MCP

Claude Code

Last verified: 2026-07-21

One command adds the server — the same on macOS, Linux, and Windows — and your browser signs you in the first time you use it.

Prerequisites

  • A Manyreach account + your API key (Manyreach web app → API & Integrations)
  • Claude Code installed (claude --version to check) and signed in to your Anthropic account

Steps

  1. Run:

    claude mcp add --transport http manyreach https://mcp.manyreach.com/mcp

    This adds the server for the current project only (the default "local" scope, stored in ~/.claude.json). Add --scope user to make it available in every project on your machine — or --scope project to write a .mcp.json your whole team gets through the repo.

  2. Claude Code will show manyreach as needing authentication. Inside a claude session, run /mcp, select manyreach, then choose Authenticate — or from a plain shell, run claude mcp login manyreach.

  3. Run claude mcp list — manyreach should show ✔ Connected.

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 — there are no client IDs or OAuth fields to fill in anywhere, and afterwards the connection stays signed in on its own. Over SSH or another session with no local browser, Claude Code instead prints a URL to open yourself and asks for the resulting redirect URL back at the prompt (connect with ssh -t, and force this mode with claude mcp login manyreach --no-browser if needed).

Verify

Ask Claude Code to "describe the Manyreach catalog". It should call the describe tool and list resources like campaign, prospect, and sender.

Troubleshooting

  • ! Needs authentication in claude mcp list — run /mcp and choose Authenticate, or claude mcp login manyreach from a shell.
  • Running non-interactively (claude -p, scripts, CI) — sign in first from an interactive session; Claude Code can't open a browser to authenticate on its own in that mode.
  • Edited the project's .mcp.json file and nothing changed — two things to check: settings are only read when a session starts (restart it), and .mcp.json only holds servers added with --scope project — the default scope lives in ~/.claude.json instead.
  • On a managed/enterprise install, the server silently disappears from claude mcp list — an admin's MCP policy (allowedMcpServers / deniedMcpServers in managed settings) can remove a previously-working server with no error message (a fresh claude mcp add fails loudly instead); ask your admin if that's expected.