OutboundSync MCP Server out now

TL;DR. OutboundSync’s hosted MCP server is live for Cursor, Claude Code, Codex, and other Streamable HTTP clients. It uses the same Bearer API key as our REST API. There is no local MCP process to babysit. Connect https://mcp.outboundsync.com/mcp, then read the MCP setup guide.

After we shipped the public API, Sync Monitoring webhooks, and Agent Skills, the missing piece was calling those same account tools from inside the agent harness without hand-rolling REST. Hosted MCP is that piece.

Where it sits

OutboundSync MCP sits on top of the rest of the agent toolkit:

• ~35 API v1 tools — every live resource route wrapped as an MCP tool
• Sync Monitoring webhooks — sync.failed / sync.recovered to your HTTPS endpoint
• 15 public Agent Skills — preflight, sync monitoring, CRM analysis, copy, deliverability, and more

The AI and Agents hub maps how MCP, API, Skills, and Webhooks fit one loop: connect MCP (or Skills / REST) before launch, then Webhooks notify your stack when sync health changes after you send. Prefer MCP tools when connected; Skills still work over REST with OUTBOUNDSYNC_API_KEY.

Plugin marketplace listings for Cursor, Claude Code, and Codex are still in progress. Manual setup works today.

What you can do

Have your coding agent:

• Confirm the key and which CRM connections it can see (get_me)
• Check account readiness before a big run (get_account_status)
• Look up prior outreach on a contact by email or social profile URL (get_contact_outreach)
• Inspect syncs and retry when something fails (list_syncs / retry_sync — write scope, confirm first)
• List Sources paste URLs when wiring sequencers (list_sources)
• Inspect Sync Monitoring webhook deliveries when the key is account-scoped

The full tool list lives in the MCP docs and the mcp repo.

In plain English

A lot of what you do in the OutboundSync app is available outside the app through our API. MCP lets you run those same moves inside tools like Cursor and Claude Code — one-offs or recurring — without writing the HTTP yourself.

Getting started

1. Create a key under Platform access → API keys (Creating API keys). Prefer read unless the agent needs to mutate after you confirm.
2. Export it: export OUTBOUNDSYNC_API_KEY=osapi_... (never commit the key).
3. Connect https://mcp.outboundsync.com/mcp with Authorization: Bearer ${OUTBOUNDSYNC_API_KEY}.

Cursor — add to ~/.cursor/mcp.json (or project .cursor/mcp.json):

{
  "mcpServers": {
    "outboundsync": {
      "url": "https://mcp.outboundsync.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:OUTBOUNDSYNC_API_KEY}"
      }
    }
  }
}

Claude Code:

claude mcp add --transport http outboundsync https://mcp.outboundsync.com/mcp \
  --header "Authorization: Bearer ${OUTBOUNDSYNC_API_KEY}"

Smoke-test with get_me, then get_account_status. Codex and other Streamable HTTP clients follow the same URL and Bearer header — see MCP setup.

If Platform API access is already on your account, this is live today. If you need it enabled, contact us and we will turn it on.

A few caveats

Write tools (retry_sync, destination/webhook replay, blocklist pause/resync, webhook CRUD) need a key with the write scope — confirm with the user before calling them. Platform webhook tools need an account-scoped key; connection-scoped keys return 403 on /webhooks*, same as REST.

Claude Desktop and claude.ai remote Connectors expect OAuth and are not supported yet. Use Claude Code or Cursor with a Bearer key instead.

Frequently asked questions

What is the OutboundSync MCP server?

OutboundSync MCP is a hosted Model Context Protocol server at https://mcp.outboundsync.com/mcp. It exposes live OutboundSync API v1 tools to coding agents such as Cursor, Claude Code, and Codex over Streamable HTTP. Auth is the same Bearer API key you use for REST — there is no local MCP process to run.

How do I connect OutboundSync MCP?

Create a key under Platform access → API keys, set OUTBOUNDSYNC_API_KEY in your environment, then point your MCP client at https://mcp.outboundsync.com/mcp with Authorization: Bearer osapi_.... Cursor uses ~/.cursor/mcp.json; Claude Code uses claude mcp add --transport http. Full steps are in the MCP setup docs.

Do I need a separate key for MCP?

No. The same osapi_ Bearer key authenticates REST and hosted MCP. Use at least read scope for introspection; add write only if your agent may retry syncs, replay deliveries, pause or resync blocklists, or mutate Sync Monitoring webhooks after you confirm.

What can my coding agent do with OutboundSync MCP?

Confirm the key and which CRM connections it can see (get_me), check account readiness before a big run (get_account_status), look up prior outreach on a contact (get_contact_outreach), inspect syncs and retry when something fails (list_syncs / retry_sync), and work Sync Monitoring webhooks when the key is account-scoped.

Does Claude Desktop support OutboundSync MCP?

Not yet. Claude Desktop and claude.ai remote Connectors expect OAuth. Use Claude Code or Cursor with a Bearer API key today. Marketplace plugin listings are still in progress — manual setup works now.

Next steps

• MCP overview · MCP setup
• API v1 reference · Creating API keys
• Agent Skills catalog · AI and Agents