This is different from the two other AI integrations in these docs. The
MCP server is the connection an agent calls SenderKit through;
the AI-agent guide gives your own app’s agent a send tool. The
skills plugin is the layer that makes a coding agent good at both — it ships the
know-how, and bundles the MCP server so runtime sends work out of the box.
The two skills
The plugin contains onesenderkit plugin with two skills. They split along a single
line: does the agent change your code, or operate SenderKit at runtime?
senderkit-integration
Writes SenderKit into your app. Detects your stack, adds SenderKit behind a small
local wrapper, migrates an existing provider (Resend, SendGrid, Postmark, Mailgun,
SES, SMTP, Twilio, FCM, APNs, Expo) or routes through it, and verifies in test mode
before live traffic.
Install
- Claude Code
- Codex
- Cursor
Install from the marketplace:This loads both skills and the SenderKit MCP server from the repo’s Check it works: run
.mcp.json
(OAuth — no key stored). Run /mcp, sign in, and pick a workspace and test/live mode.Developing against a local checkout instead:/mcp — the senderkit server should be connected — or ask
“Use senderkit-integration to add a welcome email.”Installing the plugin gives you the
senderkit_* MCP tools, but auth differs by client:
Claude Code uses OAuth (no key stored); Codex and Cursor use an API key via
SENDERKIT_API_KEY. For every other client, manual config, and self-hosting, see
MCP installation. Start with an sk_test_ key so a coding agent
can’t send to real people until you trust it.What’s next
MCP Server
The connection the messaging-operations skill rides on — tools and modes.
MCP installation
Connect the MCP server in any client, including manual config.
Send from your AI agent
The other direction — give your app’s own agent a send tool.
MCP tools
Every tool the messaging-operations skill can call.