Use RouteKite from AI clients
Connect an approved AI client to one RouteKite workspace, inspect live operations, and complete supported workflows with explicit safeguards.
On this page
Production service
RouteKite MCP is available at https://routekite.com/mcp over Streamable HTTP. Hosted connections use RouteKite sign-in and OAuth, so you do not copy an API key into the client.
A connection is limited to one workspace and one approved access level. RouteKite applies the same workspace authorization and product safeguards used by the public API.
| Setting | Value |
|---|---|
| Server URL | https://routekite.com/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth with PKCE |
| Workspace access | One approved workspace per connection |
| Tool manifest | 46 established tools; 22 audience and campaign tools in staged release |
What RouteKite MCP can do
- Inspect workspace readiness, domains, DNS records, Sending Addresses, messages, delivery events, templates, campaigns, contacts, lists, imports, attachments, and webhooks.
- Compile an email preview, diagnose a delivery, check a recipient's current eligibility, estimate variable usage cost, and search a curated RouteKite documentation index.
- Create sending configuration, send one transactional email, manage template lifecycle, create and send campaigns, manage contacts and lists, import CSV contacts, prepare attachments, and create webhooks.
- Return a structured preview before every supported change so the exact workspace action can be reviewed before execution.
Choose the access level
Only workspace owners, admins, and developers can approve a hosted MCP connection. Page and API authorization remain authoritative even when a client displays a tool.
| Access | Best for | Includes |
|---|---|---|
| Read | Reporting, diagnosis, and planning | Workspace, domain, email, template, campaign, and audience reads |
| Manage | Approved operational work | Read access plus configuration, sending, template, campaign, audience, attachment, and webhook actions |
What the connection does not change
RouteKite MCP does not give an AI client direct database, storage, billing, delivery-infrastructure, or Super Admin access. Every tool calls a customer-facing RouteKite API boundary.
Tool results are live workspace data, not a separate MCP copy. A successful preview is not a successful mutation, and a successful submission is not proof of final inbox delivery.