OutboundSync MCP
When to use this guide: You want coding agents (Cursor, Claude Code, Codex, and similar) to call OutboundSync API v1 tools without hand-rolling REST — launch preflight, prior outreach, observability, blocklists, and Sync Monitoring.
The hosted OutboundSync MCP wraps every live OutboundSync API v1 resource route (~35 tools). Auth is the same as REST: Authorization: Bearer osapi_... from a dashboard API key.
The MCP surface is in Beta. The hosted server is production-ready; Cursor, Claude Code, and Codex plugin marketplace listings are still in progress — use the manual setup in Setup today.
Endpoint
Section titled “Endpoint”| Field | Value |
|---|---|
| Endpoint | https://mcp.outboundsync.com/mcp |
| Transport | Streamable HTTP |
| Health | https://mcp.outboundsync.com/health |
| Discovery manifest | /.well-known/agent-discovery.json on outboundsync.com |
Write tools (retry, replay, blocklist pause/resync, webhook CRUD) need a key with the write scope. Platform webhook tools need an account-scoped key — connection-scoped keys return 403 on /webhooks*, same as REST.
Claude Connectors and Claude Desktop remote connectors expect OAuth and are not supported yet. Use Claude Code or Cursor with a Bearer API key instead.
MCP vs API vs Skills
Section titled “MCP vs API vs Skills”| Surface | Best for |
|---|---|
| MCP (this section) | Your coding agent calling OutboundSync tools directly from Cursor, Claude Code, or Codex |
| API | Scripts, Try the API, OpenAPI reference, and REST when no MCP client is connected |
| Agent Skills | Structured workflows (preflight gauge, CRM analysis, sync monitoring) — prefer MCP tools when connected, fall back to REST |
For how all three fit with Webhooks in one loop, see AI and Agents.
Start here
Section titled “Start here”Full tool list and server repo: github.com/outboundsync/mcp.
