Skip to content

Website agent tools and WebMCP

When to use this guide: You want an AI agent to explore or evaluate OutboundSync on the marketing site — find integrations, get pricing, compare tools, search the docs — instead of screenshotting and clicking around. This is different from connecting a coding agent to your OutboundSync account.

The website exposes a small set of read-mostly “site actions” so an agent can do the things a visitor does, described in plain language with typed inputs. They are published three ways from one source, and none of them touch your account data.

The two surfaces side by side:

Product MCPWebsite tools (this page)
Endpointhttps://mcp.outboundsync.com/mcphttps://outboundsync.com/api/mcp/ + in-page WebMCP
What it doesWraps ~35 OutboundSync API v1 tools — pipeline readiness, prior outreach, observability, blocklists, Sync MonitoringMarketing-site lookups — integrations, agencies, pricing, comparisons, docs search, demo/get-started links
DataYour account’s outbound + CRM sync dataPublic information about the product and company
AuthRequired — Authorization: Bearer osapi_...None (read-only). The one write path — contact — is human-confirmed
Who it’s forCoding agents operating your account (Cursor, Claude Code, Codex)Any agent browsing or evaluating OutboundSync
DocsOutboundSync MCPThis page

If you want an agent to use OutboundSync on your data, that’s the product MCP. If you want an agent to learn about OutboundSync from the site, that’s what’s below.

ToolWhat it returns
find_integrationMatching CRM and sequencer integrations (filter by name, type, tier)
find_agencyMatching partner agencies (filter by name, tool, tier)
get_pricingCurrent tiers, included send volume, and rollover caps
list_comparisons / get_comparisonOutboundSync vs. Zapier, Make, n8n, and Clay
search_docsDocumentation pages matching a keyword, with their Markdown mirrors
book_demoThe SavvyCal link to book a live demo with a human
get_startedThe link to create an account in the app
submit_contactSends a message to the team — fills the contact form for a person to review and submit

Every tool mirrors something a visitor can already do. The machine-readable definitions, including the equivalent REST call for each tool, live at /.well-known/webmcp/tools.json.

WebMCP is an early W3C Community Group proposal. Chrome shipped the first native implementation; other browsers are expected to follow. OutboundSync registers its tools through a feature-detected adapter, so pages behave exactly as before in browsers without WebMCP — there is nothing to turn on.

The remote endpoint at https://outboundsync.com/api/mcp/ speaks JSON-RPC 2.0 (MCP streamable HTTP) and exposes the read-only tools — the contact write is intentionally excluded there. To contact the team, an agent points a person at /contact/.

Terminal window
curl -s https://outboundsync.com/api/mcp/ \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
EndpointContent
/data/integrations-index.jsonIntegrations directory
/data/agencies-index.jsonPartner agencies
/data/pricing.jsonPricing tiers
/data/comparisons-index.jsonCompetitor comparisons
/data/docs-index.jsonDocs catalog for keyword search