MCP

Cursor

Last verified: 2026-07-21

Cursor's pricing currently lists MCP under its paid tiers (plans are now Hobby, Pro, Pro+, Ultra, Teams, Enterprise). Sign-in opens in your browser the first time you connect.

Prerequisites

  • A Manyreach account + your API key (Manyreach web app → API & Integrations)
  • Cursor installed and up to date, on a paid plan (Pro or higher)

Steps

The fastest path is the official one-click link:

Add to Cursor →

Cursor shows an approval dialog and writes the entry into mcp.json for you — continue at step 4. Prefer to see exactly what you're adding? Do it by hand:

  1. Open (or create) Cursor's global MCP config file:

    • macOS / Linux: ~/.cursor/mcp.json
    • Windows: C:\Users\<you>\.cursor\mcp.json

    To enable it in a single project instead, use .cursor/mcp.json inside that project's folder — the two files are merged, so just don't define manyreach in both. The in-app equivalent is the gear icon → Cursor Settings → Tools & Integrations → New MCP Server.

  2. Add:

    {
  "mcpServers": {
    "manyreach": {
      "url": "https://mcp.manyreach.com/mcp"
    }
  }
}

    No type or headers keys are needed — the sign-in is negotiated automatically.

  3. Save, then reload Cursor (Command Palette → Reload Window) — Cursor doesn't hot-reload the file. Toggling the server off and on under Tools & Integrations → MCP Tools works too.

  4. Under Cursor Settings → Tools & Integrations → MCP Tools, find manyreach. If it shows Needs login (or Needs authentication), click it.

What the authorization looks like

Your browser opens a Manyreach authorization page. Paste your API key there and click Authorize. The key is checked once and never shown to the AI — afterwards the connection stays signed in on its own.

Verify

Ask Cursor's agent to "describe the Manyreach catalog". It should call the describe tool and list resources like campaign, prospect, and sender.

Troubleshooting

  • Edited mcp.json and nothing changed — Cursor doesn't hot-reload it; reload the window, or toggle the server in Tools & Integrations → MCP Tools.
  • The browser sign-in fails or loops — a known 2026 regression around Cursor's sign-in callback (it now listens on http://localhost:8787/callback): make sure nothing else is using port 8787, update Cursor, and retry.
  • Connection errors with no obvious cause — select the server and hit Show Logs in Tools & Integrations → MCP Tools, or open the MCP channel in the Output panel (Cmd/Ctrl+Shift+U).
  • The server never appears at all — check the JSON is valid (a stray comma fails silently), that the entry sits under the mcpServers root key, and that your plan includes MCP.