MCP server (rcs-mcp)
rcs-mcp is a hand-rolled Model Context Protocol server — newline-delimited
JSON-RPC over stdio, zero runtime dependencies. Register it once and Claude (or
any MCP host) can search, render, clone, author, and send templates as native
tools.
The MCP server ships in the @rcs-templates/agent-toolkit package and is a
Pro-plan feature.
Prerequisites
- A scoped agent API key (
rcsk_live_…). - Your gateway URL (the
/api/agentbase — your self-hosted server or the hosted gateway). - Node.js (the server runs via
npx, no global install required).
Register with Claude
A single claude mcp add command points the host at the packaged server with
your gateway URL and key:
claude mcp add rcs-templates \
--env RCS_GATEWAY_URL=https://your-server \
--env RCS_AGENT_KEY=rcsk_live_… \
-- npx -y -p @rcs-templates/agent-toolkit rcs-mcpThat’s it — the tools then appear natively in the agent.
Register with any MCP host
Any MCP host that supports stdio servers can launch rcs-mcp the same way. Use
this JSON server entry (the shape most hosts accept):
{
"mcpServers": {
"rcs-templates": {
"command": "npx",
"args": ["-y", "-p", "@rcs-templates/agent-toolkit", "rcs-mcp"],
"env": {
"RCS_GATEWAY_URL": "https://your-server",
"RCS_AGENT_KEY": "rcsk_live_…"
}
}
}
}The nine tools
Registering the server gives your agent nine native tools — each one is exactly one gateway call:
| Tool | Scope required |
|---|---|
capabilities | any key |
search_templates | templates:read |
get_template | templates:read |
render_template | templates:read |
create_template | templates:write |
clone_template | marketplace:clone |
submit_template | templates:submit |
send_message | messages:send |
get_usage | usage:read |
See the API reference for each tool’s inputs and outputs.
A tool only works if your key holds its scope. Call capabilities first — it
returns the scopes your key actually holds, so the agent can plan around what
it’s allowed to do.