RouteKite MCP integration
Work with RouteKite from your AI assistant.
Connect compatible Claude and Codex clients to RouteKite through MCP to work with contacts, templates, campaigns, and delivery records using workspace-scoped access and explicit approval.
Reviewed October 4, 2026
Start with one authorized connection
Model Context Protocol, or MCP, lets a compatible AI client use RouteKite tools after you authorize a connection. The hosted server is available at https://routekite.com/mcp.
- Add RouteKite to your client
Follow the setup guide for Codex, Claude Code, or the Claude app. Your client must support remote MCP and the documented authorization flow.
- Choose the workspace and access
Sign in to RouteKite and select one workspace with Read or Manage access. Workspace owners, admins, and developers can authorize a hosted connection.
- Inspect before changing
Ask for readiness, a draft, an audience count, or a delivery record. Review the returned facts and the proposed change before confirming it.
- Approve a real send deliberately
Review sender, recipients, content, and consequences. Confirmed campaign and transactional sends deliver real email and consume the normal sending allowance.
Bring the email workflow into the conversation
Use the assistant to prepare and inspect supported email operations while RouteKite remains the authority for roles, sender readiness, recipient eligibility, billing, and delivery.
- Contacts and audiences
- Read, import, create, and update contacts; organize lists; work with supported fields, topics, and segments; and review matching and eligible recipient counts.
- Templates
- Create a supported template, inspect its variables and preview, publish an immutable version, or update existing template metadata. Editing an existing template body stays in the dashboard or starts as a new template.
- Campaigns
- Prepare a draft, inspect its audience and readiness, and explicitly confirm a supported send or schedule. The preparation and final send checks still apply.
- Messages and delivery
- Prepare a transactional email, check current recipient eligibility and template variables, and retrieve recorded message states and delivery events.
Examples to try after connection
A useful prompt names the workspace task, requests a review, and makes the approval boundary explicit. After connecting, try one of these instructions.
- “Check my workspace sending readiness and explain what I need to finish before sending.”
- “Find my draft campaign, show the sender, audience, and eligible recipient count, and prepare a send preview. Wait for my approval.”
- “Create a welcome email template with a name variable. Show me the preview before publishing it.”
- “Show the latest delivery events for this message and explain what its current state means.”
These are prompts for a connected assistant. Pasting them into a conversation does not install a connector, grant access, or send an email by itself.
Permissions and limits stay visible
Each connection belongs to one member and workspace. Read access inspects available records; Manage adds supported changes. Every request still passes RouteKite's server-side authorization.
Supported changes return a preview before explicit confirmation. Sending is a real action, and deleting a contact or list is destructive. Inspect current state after an uncertain response before retrying; not every operation has the same deduplication behavior.
MCP does not manage purchases, API keys, administrator access, or infrastructure. A delivery check reports stored evidence and cannot guarantee inbox placement. Client availability, subscription requirements, connection setup, and support for individual workflows vary; the setup guide describes the current paths without promising universal client acceptance.
Review or revoke your connections in Dashboard, Developers, MCP Connections. Refresh the client's tool list after a RouteKite tool release.
Connect the workspace you already use.
Prepare campaigns and product emails with a compatible AI assistant, then keep the final decision with your team.