Articles on: Integrations

Connect SuperSend MCP to Cursor

Connect SuperSend MCP to Cursor


Purpose


This article explains how to connect SuperSend's MCP (Model Context Protocol) server to Cursor. Once connected, you can ask the Cursor AI agent to manage your SuperSend campaigns, contacts, senders, and deliverability without leaving your editor.


Prerequisites


  • A SuperSend account with at least one team.
  • A SuperSend API key (see How to get your API key below).
  • Cursor installed (any recent version with MCP support).


How to Get Your SuperSend API Key


Your organization already has an API key in SuperSend. You do not create or rotate it—it stays the same for your account. Copy it whenever you connect a new tool.


  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.



Shortcut: Let Cursor Set Itself Up


If you already have Cursor open, you can skip the manual steps below. The Cursor agent can read SuperSend's setup docs and configure the connection for you.


  1. Open the Cursor chat panel.
  2. Paste the following URL and prompt:


> Read the setup docs at https://docs.supersend.io/docs/mcp-server and configure the SuperSend MCP server for me.


Cursor will fetch the page, identify the correct config for Cursor, and either make the file changes automatically or walk you through exactly what to paste and where.


You'll still need your SuperSend API key ready (see How to Get Your SuperSend API Key above). The manual steps below are here if you prefer to do it yourself or need to troubleshoot.



Steps


Step 1: Open or create the Cursor MCP config file


Cursor reads MCP server configuration from ~/.cursor/mcp.json (your home directory).


Open that file in a text editor. If it doesn't exist yet, create it.


Step 2: Add the SuperSend MCP server


Paste the following into ~/.cursor/mcp.json, replacing YOUR-API-KEY with your SuperSend API key:


{
  "mcpServers": {
    "supersend": {
      "url": "https://mcp.supersend.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR-API-KEY"
      }
    }
  }
}


If you already have other MCP servers listed, add the "supersend" block inside the existing "mcpServers" object.


Step 3: Restart Cursor


Fully quit and relaunch Cursor so it picks up the updated config.


Step 4: Enable the MCP server in Cursor settings


  1. Open Cursor Settings (⌘, on macOS or Ctrl+, on Windows/Linux).
  2. Navigate to MCP (under the Features or Tools section).
  3. Confirm supersend appears in the server list and its status shows as Connected (green indicator).


If it shows as disconnected, check that your API key is correct and that the JSON in mcp.json is valid.


Step 5: Verify the connection


In the Cursor chat panel, type:


List my SuperSend teams


The agent will call the list_teams tool and return your team names. If you see them, you're connected.



What You Can Do Once Connected


Here are some example prompts to get started directly in the Cursor chat:


  • 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 the sequence for my "Product Launch" campaign — view campaign steps


If the agent 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 setup, the Cursor AI agent has access to SuperSend tools covering contacts, campaigns, senders, conversations, deliverability intelligence, domain health, and more. The tools are called automatically when you ask about SuperSend in the chat panel.


Troubleshooting


  • Issue: The supersend server shows as Disconnected in Cursor MCP settings.

Fix: Confirm the mcp.json file is valid JSON (no trailing commas, no missing brackets). Use a JSON validator if unsure. Also confirm your API key is correct.


  • Issue: Cursor says it doesn't know about SuperSend tools.

Fix: Make sure you fully quit and relaunched Cursor after editing mcp.json. Changes to the config file require a full restart to take effect.


  • Issue: Authentication error from SuperSend.

Fix: Copy the key again from Admin → System → API Key → Copy and update mcp.json. Ensure there are no extra spaces or line breaks around the key in the JSON file.


  • Issue: mcp.json file location unclear.

Fix: On macOS/Linux, the file is at ~/.cursor/mcp.json (in your home directory, inside a .cursor folder). On Windows, it is at %USERPROFILE%\.cursor\mcp.json. The .cursor folder may be hidden — use your file manager's "Show hidden files" option or create it manually if it doesn't exist.


  • Issue: Server shows as connected but tools don't appear to work.

Fix: Run curl https://mcp.supersend.io/health in a terminal — it should return {"status":"ok"}. If it doesn't, there may be a network or firewall issue.




Updated on: 07/04/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!