Connect a client - ManyPI Docs

Every client points at the same endpoint:

https://mcp.manypi.com/mcp

Two ways to authenticate:

Sign in with your browser (OAuth) — nothing to paste. Supported by Claude Code, Claude.ai & Desktop, Cursor and VS Code.
API key — works everywhere. Create one in Settings → API keys and send it as Authorization: Bearer mpi_….

Prefer OAuth where it is available: there is no key to leak, and you can revoke the connection from Settings → Connected apps at any time.

Replace mpi_your_api_key in every snippet below with your real key. A key needs read, plus agents for lead generation, leads:validate for verification, and outreach:send to send.

AI agent CLIs

Claude Code

With browser sign-in — no key needed:

claude mcp add --transport http manypi https://mcp.manypi.com/mcp -s user

Then start Claude Code, run /mcp, choose manypi → Authenticate, and approve in the browser.With an API key:

claude mcp add --transport http manypi https://mcp.manypi.com/mcp \
  --header "Authorization: Bearer mpi_your_api_key" -s user

Drop -s user to scope it to the current project only. Verify with /mcp.

Codex

Codex speaks stdio, so bridge to the hosted server with mcp-remote. Add to ~/.codex/config.toml:

[mcp_servers.manypi]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.manypi.com/mcp", "--header", "Authorization: Bearer mpi_your_api_key"]

Gemini CLI

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "manypi": {
      "httpUrl": "https://mcp.manypi.com/mcp",
      "headers": { "Authorization": "Bearer mpi_your_api_key" }
    }
  }
}

Run gemini, then /mcp to confirm.

GitHub Copilot CLI

Run /mcp add and provide an HTTP server, or add to your Copilot MCP config:

{
  "mcpServers": {
    "manypi": {
      "type": "http",
      "url": "https://mcp.manypi.com/mcp",
      "headers": { "Authorization": "Bearer mpi_your_api_key" }
    }
  }
}

OpenCode

Add to opencode.json (project) or ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "manypi": {
      "type": "remote",
      "url": "https://mcp.manypi.com/mcp",
      "enabled": true,
      "headers": { "Authorization": "Bearer mpi_your_api_key" }
    }
  }
}

Factory (Droid)

Add to ~/.factory/mcp.json:

{
  "mcpServers": {
    "manypi": {
      "type": "http",
      "url": "https://mcp.manypi.com/mcp",
      "headers": { "Authorization": "Bearer mpi_your_api_key" }
    }
  }
}

Web clients

Claude.ai and Claude Desktop

With browser sign-in:

Settings → Connectors → Add custom connector
Name it ManyPI and paste the server URL:
https://mcp.manypi.com/mcp
Click Connect. Claude opens ManyPI in a new window; approve and the connector goes live.

Leave the advanced OAuth fields empty — Claude fills them in from ManyPI itself.With an API key: add the connector the same way, and when Claude prompts for an Authorization header, paste:

Authorization: Bearer mpi_your_api_key

ChatGPT

Requires a paid ChatGPT plan.

Settings → Connectors → Advanced → Developer mode
Under Connectors, click Create, name it ManyPI, and paste:
https://mcp.manypi.com/mcp
Add a custom header so every call is authenticated:
Authorization: Bearer mpi_your_api_key

Goose

Desktop: Settings → Extensions → Add. CLI: goose configure → Add Extension.Choose Remote Extension (Streamable HTTP), paste https://mcp.manypi.com/mcp, and add the header:

Authorization: Bearer mpi_your_api_key

IDEs

Cursor

With browser sign-in — create ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

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

Open Settings → MCP; manypi shows a Login button. Click it and approve.With an API key:

{
  "mcpServers": {
    "manypi": {
      "url": "https://mcp.manypi.com/mcp",
      "headers": { "Authorization": "Bearer mpi_your_api_key" }
    }
  }
}

VS Code

With browser sign-in — create .vscode/mcp.json:

{ "servers": { "manypi": { "type": "http", "url": "https://mcp.manypi.com/mcp" } } }

Run MCP: List Servers → manypi → Start. VS Code opens ManyPI for approval.Or from the CLI:

code --add-mcp '{"name":"manypi","type":"http","url":"https://mcp.manypi.com/mcp"}'

With an API key:

{
  "servers": {
    "manypi": {
      "type": "http",
      "url": "https://mcp.manypi.com/mcp",
      "headers": { "Authorization": "Bearer mpi_your_api_key" }
    }
  }
}

Antigravity

Agent panel → MCP servers → Add server, or edit the MCP config:

{
  "mcpServers": {
    "manypi": {
      "serverUrl": "https://mcp.manypi.com/mcp",
      "headers": { "Authorization": "Bearer mpi_your_api_key" }
    }
  }
}

Kiro

Edit .kiro/settings/mcp.json (workspace) or ~/.kiro/settings/mcp.json (user):

{
  "mcpServers": {
    "manypi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.manypi.com/mcp", "--header", "Authorization: Bearer mpi_your_api_key"]
    }
  }
}

Windsurf

Settings → Cascade → MCP servers → Add, or edit ~/.codeium/windsurf/mcp_config.json. Windsurf proxies HTTP servers via mcp-remote:

{
  "mcpServers": {
    "manypi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.manypi.com/mcp", "--header", "Authorization: Bearer mpi_your_api_key"]
    }
  }
}

Click Refresh in the MCP panel.

Any other client

If your client supports MCP over Streamable HTTP, point it at https://mcp.manypi.com/mcp with an Authorization: Bearer header. If it only speaks stdio, bridge with:

npx -y mcp-remote https://mcp.manypi.com/mcp \
  --header "Authorization: Bearer mpi_your_api_key"

Troubleshooting

The tool list is empty

Almost always authentication. Check the header is exactly Authorization: Bearer mpi_…, and confirm the key works:

curl https://app.manypi.com/api/user -H "Authorization: Bearer mpi_your_api_key"

401 Unauthorized

The key is missing, revoked, or expired — or an OAuth token has expired and the client needs to re-authorise. Reconnect from the client’s MCP panel.

A tool returns a permission error

The key exists but lacks that permission. Lead generation needs agents, verification needs leads:validate, sending needs outreach:send. See API keys and permissions.

Sending tools fail with outreach_locked

enroll_leads and send_email require a paid plan. Everything else works on free.

​AI agent CLIs

​Web clients

​IDEs

​Any other client

​Troubleshooting

AI agent CLIs

Web clients

IDEs

Any other client

Troubleshooting