Connect SuperSend MCP to Claude

Purpose

This article walks through connecting SuperSend's MCP (Model Context Protocol) server to Claude — on claude.ai (Connectors), Claude Desktop, and Claude Code. Once connected, you can manage contacts, campaigns, senders, deliverability, and more by talking to Claude directly.

Prerequisites

• A SuperSend account with at least one team.
• For claude.ai Connectors (recommended): a Claude account (Free, Pro, Max, Team, or Enterprise). Team/Enterprise may require an Owner to add the custom connector first.
• For Claude Desktop or Claude Code with an API key: your SuperSend API key (see How to get your API key below), plus Node.js for Desktop's mcp-remote bridge.

How to Get Your SuperSend API Key

You only need an API key for Desktop, Claude Code, or other clients that use header auth. claude.ai Connectors use OAuth — you log in and authorize in the browser, so no API key paste is required.

Your organization already has an API key in SuperSend. You do not create or rotate it—it stays the same for your account.

1. Log in to SuperSend and go to Admin → System tab.
2. In the IDs section, find the API Key field (next to Org ID).
3. Click Copy to copy the key to your clipboard. Use it wherever the steps below say YOUR-API-KEY.

If you do not see Admin or the API Key field, you may need org admin access—ask a workspace admin.

Option A: Claude.ai Connectors (recommended)

Use Claude's Connectors UI so Claude talks to SuperSend over the public remote MCP URL with OAuth. No config file and no API key.

Step 1: Open Connectors

1. Open claude.ai and sign in.
2. Go to Settings → Connectors (on Team/Enterprise, Owners may need Admin settings → Connectors first).

Step 2: Add the SuperSend custom connector

1. Click Add custom connector.
2. Enter the remote MCP server URL:

   
   

   
   https://mcp.supersend.io/mcp

3. Leave advanced OAuth client fields empty unless SuperSend support tells you otherwise (Claude discovers OAuth via the server's well-known metadata).
4. Click Add.

Step 3: Connect and authorize

1. Find SuperSend (or your custom connector name) in the list and click Connect.
2. Complete the SuperSend login / consent screen in the browser.
3. Return to Claude — the connector should show as connected.

Step 4: Enable in chat and verify

1. In a new chat, open the + menu → Connectors and enable SuperSend for that conversation if needed.
2. Ask:

List my SuperSend teams

Claude should call list_teams and return your teams.

Option B: Claude Desktop (API key)

Claude Desktop can also use the remote MCP server via the mcp-remote bridge and your SuperSend API key.

Step 1: Open the Claude Desktop config file

Open the config file for your operating system in any text editor:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

If the file doesn't exist yet, create it.

Step 2: Add the SuperSend MCP server

Paste the following into the config file, replacing YOUR-API-KEY with your SuperSend API key:

{
  "mcpServers": {
    "supersend": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.supersend.io/mcp",
        "--header",
        "Authorization: Bearer YOUR-API-KEY"
      ]
    }
  }
}

If you already have other MCP servers configured, add the "supersend" block inside the existing "mcpServers" object — don't replace the whole file.

Step 3: Restart Claude Desktop

Fully quit and relaunch Claude Desktop. On macOS, right-click the Dock icon and choose Quit before reopening.

Step 4: Verify the connection

In a new Claude conversation, type:

List my SuperSend teams

Claude will use the list_teams tool and return your teams. If you see your team names, the connection is working.

Option C: Claude Code (CLI)

Step 1: Run the setup command

In your terminal, run:

claude mcp add --transport http supersend https://mcp.supersend.io/mcp --header "Authorization: Bearer YOUR-API-KEY"

Replace YOUR-API-KEY with your SuperSend API key.

Step 2: Verify the connection

Start a Claude Code session and type:

List my SuperSend teams

Claude will call the list_teams tool and return your team list. If you see your teams, you're connected.

What You Can Do Once Connected

Here are some example prompts to get started:

• List my SuperSend campaigns — see all active and inactive campaigns
• Add john@example.com to my "Q4 Outreach" campaign — enroll a contact
• Why is my reply rate so low? — runs a deliverability diagnosis
• When will my campaigns finish? Do I have enough capacity? — capacity forecast
• Which senders are at risk? — per-sender health and bounce analysis
• Show me bounce insights for sender@example.com — AI bounce breakdown

If Claude asks for a Team ID or Campaign ID, just say "List my SuperSend teams first" and it will fetch the IDs automatically.

Expected Result

After completing setup, Claude has access to SuperSend tools covering contacts, campaigns, senders, conversations, deliverability intelligence, domain health, and more. The SuperSend tools appear in Claude's tool list and are called automatically when relevant.

Troubleshooting

• Issue: Claude.ai connector fails to connect or OAuth never completes.

Fix: Confirm https://mcp.supersend.io/health returns {"status":"ok"}. Retry Connect, complete SuperSend login in the browser popup, and allow the app. On Team/Enterprise, confirm an Owner added the custom connector before you connect.

• Issue: Claude says it doesn't have access to SuperSend tools.

Fix (Connectors): Enable the connector for the chat via + → Connectors.
Fix (Desktop): Confirm the config file is valid JSON and that you fully quit and relaunched Claude Desktop.

• Issue: npx mcp-remote error or "command not found."

Fix: Confirm Node.js is installed (node --version in terminal). If Node is missing, install it from nodejs.org.

• Issue: Authentication error or "Unauthorized" response (API key path).

Fix: Copy the key again from Admin → System → API Key → Copy. Ensure you pasted the full key with no extra spaces or line breaks in the config file or terminal command.

• Issue: Config file changes aren't taking effect.

Fix: Make sure you fully quit Claude Desktop (not just closed the window) before relaunching. On macOS, use right-click → Quit from the Dock.

• Issue: Claude Code says the MCP server is unreachable.

Fix: Confirm you have internet access and that https://mcp.supersend.io/mcp is reachable. Run curl https://mcp.supersend.io/health — it should return {"status":"ok"}.

Related Articles

• Connect SuperSend MCP to Cursor
• Connect SuperSend MCP to Codex
• Integrations Overview

Updated on: 20/10/2026