RCS-Templates for AI agents
RCS-Templates is agent-native. The /api/agent gateway lets autonomous AI
agents discover, author, clone, render, and send RCS templates
programmatically — reusing the exact same services as the human app.
It’s exposed three ways over one typed contract, so the surfaces can’t drift:
| Surface | Package ref | Use it for |
|---|---|---|
| MCP server | rcs-mcp | In-model tool use — Claude or any MCP host calls templates as native tools |
| CLI | rcs | Shells, CI, and shell-driven agent loops — JSON in, JSON out |
| Typed client | GatewayClient | Embedding the gateway directly in your own service code |
The MCP server and the CLI ship together as the @rcs-templates/agent-toolkit
package and are available on the Pro plan. The raw gateway and typed client
are available to any account.
Everything an agent can do is gated by scoped API keys. An agent can only do what its key was minted for, and an agent send clears the same provider-approval gate as a human send — there’s no back door to ship an unapproved template.
What you can do
Each capability is exactly one gateway call (one MCP tool / one CLI verb):
- Discover — search the 500+ template marketplace by query, channel, and category.
- Inspect — fetch a template’s content, ratings, and grounding knowledge doc.
- Render — try-before-you-buy with sample variables; inspect the validated RCS payload + SMS fallback.
- Author — create new templates from a content object, validated against channel rules.
- Clone — deep-copy a marketplace listing into your org as a clean private draft.
- Submit — send a draft to the provider (Twilio) for brand approval.
- Send — broadcast an org-owned template to an E.164 list, RCS-first with SMS/MMS fallback.
- Meter — read month-to-date usage from the same ledger billing counts.
Get started
- Mint an API key — a scoped
rcsk_live_…token. - Set up the MCP server or the CLI.
- Follow the agent quickstart to wire it into your agent.
- Reference every tool and scope in the API reference.