Skip to main content
This walkthrough connects Claude Code to SenderKit and makes your first tool call. The hosted MCP server runs at https://mcp.senderkit.com, so there’s nothing to install — you just point the client at it with your API key. Other clients and the local stdio server are covered in Installation.
1

Get a test API key

Create one in the dashboard. For this walkthrough, use a key with the sk_test_ prefix — sends go through the full pipeline but never reach a real provider. See Authentication.
export SENDERKIT_API_KEY=sk_test_…
2

Register the server with Claude Code

From your terminal, run:
claude mcp add --transport http --scope user senderkit \
  https://mcp.senderkit.com \
  --header "Authorization: Bearer $SENDERKIT_API_KEY"
--scope user makes the server available across every Claude Code project, not just the current one. The command writes the configuration into ~/.claude.json.
3

Confirm the server is connected

Start Claude Code and run /mcp. You should see senderkit with a tool count of 10. If it shows pending for a moment, that’s expected — Claude Code waits for the server to advertise its tools.
4

Send your first tool call

Ask Claude:
Use SenderKit to list my templates.
Claude calls the senderkit_templates_list tool and prints what your workspace has. Then try:
Send the welcome template to me@example.com.
With an sk_test_ key, the message moves through the full lifecycle (queued → rendered → sent → delivered) without ever touching a provider.
Swap the key prefix to sk_live_… when you’re ready to send real notifications. The MCP server doesn’t change — only the key does.

Installation

Config for Claude Desktop, Cursor, Windsurf, and other clients.

Tools

The full tool surface and every parameter.