AI and Agents
Website agent tools and WebMCP
How AI agents use the OutboundSync website — WebMCP in-page tools, a public JSON API, and a read-only site MCP endpoint, kept separate from the product MCP.
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.
This is not the product MCP
Section titled “This is not the product MCP”The two surfaces side by side:
| Product MCP | Website tools (this page) | |
|---|---|---|
| Endpoint | https://mcp.outboundsync.com/mcp |
https://outboundsync.com/api/mcp/ + in-page WebMCP |
| What it does | Wraps ~35 OutboundSync API v1 tools — pipeline readiness, prior outreach, observability, blocklists, Sync Monitoring | Marketing-site lookups — integrations, agencies, pricing, comparisons, docs search, demo/get-started links |
| Data | Your account’s outbound + CRM sync data | Public information about the product and company |
| Auth | Required — Authorization: Bearer osapi_... |
None (read-only). The one write path — contact — is human-confirmed |
| Who it’s for | Coding agents operating your account (Cursor, Claude Code, Codex) | Any agent browsing or evaluating OutboundSync |
| Docs | OutboundSync MCP | This 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.
The tools
Section titled “The tools”| Tool | What it returns |
|---|---|
find_integration |
Matching integrations with page and Markdown URLs (filter by name, type, tier, availability, or crm to get tool + CRM guide pages) |
find_agency |
Matching partner agencies (filter by name, tool, tier) |
get_pricing |
Current tiers, included send volume, and rollover caps |
list_comparisons / get_comparison |
OutboundSync vs. Zapier, Make, n8n, and Clay |
search_docs |
Documentation pages matching a keyword, with their Markdown mirrors |
book_demo |
The SavvyCal link to book a live demo with a human |
get_started |
The link to create an account in the app |
submit_contact |
Sends 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.
Three ways to reach them
Section titled “Three ways to reach them”WebMCP browser support
Section titled “WebMCP browser support”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.
Remote site MCP endpoint
Section titled “Remote site MCP endpoint”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/.
curl -s https://outboundsync.com/api/mcp/ \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Public JSON API
Section titled “Public JSON API”| Endpoint | Content |
|---|---|
/data/integrations-index.json |
Integrations directory, plus combos (every tool + CRM guide page) |
/data/agencies-index.json |
Partner agencies |
/data/pricing.json |
Pricing tiers |
/data/comparisons-index.json |
Competitor comparisons |
/data/docs-index.json |
Docs catalog for keyword search |
