Claude Code CLI Setup

Connect the Claude Code CLI to Keplars using the MCP Server. No bridge process needed — native HTTP transport supported.

Claude Code (the CLI) supports HTTP MCP servers natively. Unlike other clients, no mcp-remote bridge is needed — it connects directly to the Keplars MCP endpoint.

Setup

Get your Keplars API keys

Open the Keplars dashboard and navigate to API Keys in your workspace settings. You need two keys:

Send key (prefixed live_): used for sending emails
Admin key (prefixed adm_): used for templates, contacts, campaigns, and domains

Create both and copy them. You will only see each key once.

Add the server with one command

claude mcp add --transport http \
  --header "Authorization:<YOUR_SEND_KEY>" \
  --header "X-Admin-Api-Key:<YOUR_ADMIN_KEY>" \
  keplars https://mcp.keplars.com/mcp

This writes the config to your user-level Claude settings and makes the tools available in every project.

To scope it to a single project instead, add --scope project from inside the project directory:

claude mcp add --transport http --scope project \
  --header "Authorization:<YOUR_SEND_KEY>" \
  --header "X-Admin-Api-Key:<YOUR_ADMIN_KEY>" \
  keplars https://mcp.keplars.com/mcp

This writes to .claude/settings.json in the project root.

Verify

claude mcp list

You should see keplars listed with http transport and the endpoint URL.

Try it out

Start a Claude Code session and ask naturally:

Send a transactional email

"Send a transactional email to [email protected] with subject 'Your verification code' and body 'Your code is 482910'"

List audiences and add a contact

"List my Keplars audiences, then add [email protected] to the newsletter audience with first name Sarah"

Create and send a campaign

"Create a Keplars campaign called 'Release Notes' targeting audience aud-123 using template tmpl-abc with subject 'What is new in v2.0', then send it"

Campaigns and bulk sends trigger a confirmation step

When you ask Claude Code to send a campaign or a bulk email, it will first show you the audience size and ask you to confirm before dispatching. Reply "yes" to proceed or "no" to cancel.

Manual config

You can also edit ~/.claude/settings.json directly instead of using the CLI command:

{
  "mcpServers": {
    "keplars": {
      "type": "http",
      "url": "https://mcp.keplars.com/mcp",
      "headers": {
        "Authorization": "<YOUR_SEND_KEY>",
        "X-Admin-Api-Key": "<YOUR_ADMIN_KEY>"
      }
    }
  }
}

Troubleshooting

claude mcp add says the server already exists

Remove it first, then re-add:

claude mcp remove keplars
claude mcp add --transport http \
  --header "Authorization:<YOUR_SEND_KEY>" \
  --header "X-Admin-Api-Key:<YOUR_ADMIN_KEY>" \
  keplars https://mcp.keplars.com/mcp

Tools not available in a session

Run claude mcp list to confirm the server is registered. If it shows up but tools are unavailable, check that the endpoint is reachable from your machine with:

curl -s -X POST https://mcp.keplars.com/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: <YOUR_SEND_KEY>" \
  -H "X-Admin-Api-Key: <YOUR_ADMIN_KEY>" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \
  | jq '.result.tools[].name'

"Unauthorized" error on email sends

Your send key (live_ prefix) may be invalid or deleted. Generate a new one from the Keplars dashboard under API Keys and re-add the server.

"Unauthorized" error on templates, contacts, or campaigns

These tools require the admin key (adm_ prefix) in X-Admin-Api-Key. Make sure both headers are present when adding the server.