Connect Calendly once. Your agent reads scheduled meetings on the unified profile—identity-resolved with your CRM, email, and website events—through one MCP server.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
} …plus 20 more—26 MCP tools total, across contacts, companies, events, and conversations.
OAuth one connector. Drop a snippet into your MCP client. Ask a question.
Create an account at pathbound.ai. Free during public alpha.
In the dashboard, go to Integrations → Calendly → Connect. Authorize over Calendly’s official OAuth in one click—read-only scopes. Pathbound syncs scheduled events and invitees and matches each meeting to the right contact.
Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Settings → Connected Apps → Add custom MCP → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
} Ask the agent: “Who has a meeting booked with us this week?” The agent calls list_events via MCP and returns the list.
A direct Calendly connector shows your agent calendar events. Pathbound shows your agent the customer—Calendly meetings stitched together with your CRM, email, support, and website events—through one unified profile served over the Model Context Protocol.
Every booking, reschedule, and cancellation lands on the same timeline as deal stage, emails, and pricing-page visits. The agent sees the meeting next to the reason it matters.
The invitee resolves to the same unified contact you already have in your CRM, Gmail, and website events—by email—so the meeting joins their profile, not a separate calendar feed.
Pathbound only reads from Calendly—scheduled events and invitees. It never books or cancels, so connecting it can’t touch your scheduling.
Token-efficient shapes: the agent gets “demo booked, Tue 2pm, with the VP of Eng,” not raw event JSON.
Pathbound is an independent platform. We connect to Calendly via its official OAuth API and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with Calendly.
No. The Calendly integration is read-only—it pulls scheduled events and invitees into the unified profile and never books, reschedules, or cancels.
Scheduled events (including reschedules and cancellations) and invitee details, matched onto the unified contact by email. The meeting then sits on the same timeline as the contact’s CRM record, emails, and web activity.
Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue—any client that supports the Model Context Protocol with OAuth.
Tenant-isolated and OAuth-scoped per user, with encryption at rest via our infrastructure provider’s default configuration. GDPR-aligned; SOC 2 readiness in progress. Pathbound does not sell customer data, and we don’t call AI providers on your behalf—your MCP client does, under your account and the AI provider’s terms.
Same MCP server, same tools—just connect a different source. See the integrations directory.
Sign up, connect one CRM or drop the events snippet, and point your MCP client at
mcp.pathbound.ai/mcp.