Install in your agent
Add SendCrew to Claude, ChatGPT, Cursor, n8n and any other MCP client, with OAuth sign-in or an API key.
Every client connects to the same remote MCP server:
https://sendcrew.io/api/mcpThere are two ways to authenticate, and both end up as a key for one workspace (one client), so the agent only sees that workspace's senders, contacts and inbox:
- Sign in with OAuth. Clients that support MCP OAuth (Claude, ChatGPT, Cursor, Claude Code, VS Code) only need the URL. They open a SendCrew page in your browser where you pick the workspace and click Allow access. SendCrew creates an API key for that client, which you can revoke any time under API keys.
- Paste an API key. Create one under API keys in the dashboard and send it as
Authorization: Bearer sc_live_.... Use this for servers, n8n and scripts.
The safety layer still applies
However the agent connects, every write goes through SendCrew's limits: daily and weekly caps, warmup, quiet hours, jitter and pool-wide dedupe. No tool parameter can override them. Add "dry_run": true to any write to check it without queueing.
Claude (claude.ai and Claude Desktop)
- Open Settings → Connectors and click Add custom connector.
- Name it
SendCrewand pastehttps://sendcrew.io/api/mcpas the URL. Leave the OAuth fields empty. - Click Connect, sign in to SendCrew, pick the workspace and click Allow access.
On Team and Enterprise plans an owner adds the connector once under Organization settings → Connectors, then each member connects their own account.
Claude Code
claude mcp add --transport http --scope user sendcrew https://sendcrew.io/api/mcpThen run /mcp, pick sendcrew and choose Authenticate. To use an API key instead, add --header "Authorization: Bearer sc_live_..." to the command.
Cursor
Add to Cursor installs it in one click. Or add SendCrew to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"sendcrew": { "url": "https://sendcrew.io/api/mcp" }
}
}Cursor shows Needs login next to the server; click it to sign in. With an API key, add "headers": { "Authorization": "Bearer sc_live_..." } instead.
ChatGPT
Custom MCP connectors need developer mode (Plus, Pro, Business, Enterprise and Edu).
- Settings → Apps & Connectors → Advanced settings: turn on Developer mode.
- Back in Apps & Connectors, click Create. Name it
SendCrew, set the MCP server URL tohttps://sendcrew.io/api/mcpand authentication to OAuth. - Sign in to SendCrew when ChatGPT asks, pick the workspace and allow access. In a chat, enable SendCrew from the + menu under Developer mode.
ChatGPT asks you to confirm before it runs a tool that writes; SendCrew marks which tools read and which send (readOnlyHint).
VS Code, Windsurf, Codex, Gemini CLI
Point the client at https://sendcrew.io/api/mcp. VS Code signs in with OAuth; the others take the API key as a header. The copy-paste configs for each are in the quickstart.
n8n
As tools for an AI Agent node: add an MCP Client Tool to the agent, set Endpoint to https://sendcrew.io/api/mcp and Server Transport to HTTP Streamable, and choose Bearer Auth with your API key as the token. Pick the tools to expose (for example send_connection, check_inbox, reply_to_thread).
As plain HTTP steps: every tool is also a REST endpoint. Use an HTTP Request node with a Header Auth credential (Authorization: Bearer sc_live_...):
POST https://sendcrew.io/api/v1/actions/send_connection
{ "url": "https://www.linkedin.com/in/someone/", "note": "Hi!", "dry_run": true }The full list is in the OpenAPI spec. For replies and accepts, point a webhook at an n8n Webhook trigger instead of polling.
Clients that only speak stdio
The CLI includes a stdio MCP server that forwards to the hosted one:
{
"mcpServers": {
"sendcrew": {
"command": "npx",
"args": ["-y", "sendcrew", "mcp"],
"env": { "SENDCREW_API_KEY": "sc_live_..." }
}
}
}Leave out env after running npx sendcrew login once; the bridge reads the saved key.
Discovery details
For client developers: the server follows the MCP authorization spec.
| What | URL |
|---|---|
| Protected resource metadata (RFC 9728) | https://sendcrew.io/.well-known/oauth-protected-resource/api/mcp |
| Authorization server metadata (RFC 8414) | https://sendcrew.io/.well-known/oauth-authorization-server |
| Dynamic client registration (RFC 7591) | https://sendcrew.io/api/oauth/register |
| Authorization (code + PKCE S256) | https://sendcrew.io/oauth/authorize |
| Token | https://sendcrew.io/api/oauth/token |
An unauthenticated request to /api/mcp gets 401 with a WWW-Authenticate header pointing at the resource metadata. The access token is a workspace API key and doesn't expire; revoke it in the dashboard.