MCP Server — Overview
The Pathbound MCP server exposes the REST API as a set of tools for Model Context Protocol clients. The most common use is connecting Pathbound to Claude.ai so you can ask questions like “what did this contact do this week?” or “show me the visitors who hit /pricing yesterday” — and have the model read your unified customer profiles, events, and activity history.
Server URL
Section titled “Server URL”https://mcp.pathbound.ai/mcpWhen to use MCP vs REST
Section titled “When to use MCP vs REST”| Use… | When |
|---|---|
| REST API | You’re writing your own backend, integration, or scheduled job. |
| MCP server | You want Claude.ai (or another MCP client) to read Pathbound data on your behalf. |
The two surfaces hit the same backend and respect the same tenant boundaries. MCP authenticates via Pathbound’s native OAuth login (no API key); the REST API authenticates via API keys.
What MCP exposes
Section titled “What MCP exposes”26 tools across these domains:
- Contacts — list, get, create, update, timeline, conversations, email threads, notes CRUD.
- Companies — list, get, create, update, notes CRUD.
- Events — list, get, types, stats.
- Batch & Aggregate — multi-entity lookups and server-side group-by.
See the full Tools Reference.
Connecting Claude.ai
Section titled “Connecting Claude.ai”- In Claude.ai, open Settings → Connected Apps → Add custom MCP.
- Enter the URL
https://mcp.pathbound.ai/mcp. - Claude opens the OAuth flow — log in with your Pathbound account.
- Approve the connection. You’re now ready to ask Claude questions about your Pathbound data.
The OAuth grant is per-user and respects your Pathbound permissions: anything you can read or write in the Pathbound dashboard is what the MCP tools will let Claude do.
Limits
Section titled “Limits”- The MCP server is stateless and rate-limited per user. Heavy bursts (more than ~30 tool calls per minute) may be throttled.
- Tool responses are bounded —
get_contactcaps at 20 events. Useaggregate_dataandbatch_get_*instead of paginating.