Support
Zendesk MCP server
Connect Zendesk to Claude, ChatGPT, Cursor, and any MCP-compatible AI agent. Live access to your end-users, organizations, and the full ticket timeline — read and write — through one unified profile per customer.
A direct Zendesk MCP shows your agent Zendesk. Pathbound shows your agent the customer — across Zendesk, HubSpot, Gmail, your tracker, Apollo, Calendly, and the rest of your stack — through one unified profile served over the Model Context Protocol.
Tickets resolved against HubSpot deal stage, Gmail threads, website page views, Apollo enrichment, Calendly meetings — all stitched onto one timeline per contact. Your agent stops asking "who is this requester?" on every ticket.
Same person as [email protected] requesting tickets in Zendesk, [email protected] in Gmail, and a contact in HubSpot — Pathbound resolves to one entity. A direct connector only knows its own user IDs.
Token-efficient response shapes (count_only, fields=summary), server-side aggregation, batch tools. Agents get the answer, not raw ticket JSON. Stays inside the context window even on long ticket threads.
Update a ticket once — Pathbound writes back to Zendesk, fans out to your other sources, and logs every change with actor, timestamp, and result. Reversible. The audit trail SOC 2 and GDPR auditors look for.
Connect Zendesk once. Your agent gets identity-resolved profiles, the full ticket timeline, and write access — through one MCP server, identity-resolved with HubSpot, Gmail, your tracker, and your other sources.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
}Ticket-specific MCP tools (list_tickets, get_ticket) ship next — today, ticket history is visible in the Pathbound dashboard's contact view and the unified contact profile carries the Zendesk user record.
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 → Zendesk → Connect. Enter your Zendesk subdomain, then OAuth via Zendesk's official OAuth flow; sync runs every 60 minutes and pulls end-users, organizations, tickets, and comments via Zendesk's incremental export API.
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: “Brief me on [email protected] — include any Zendesk context you have.” The agent calls get_contact via MCP; the Zendesk end-user record is folded into the unified profile alongside everything else.
Pathbound is an independent platform. We connect to Zendesk via Zendesk's official OAuth flow and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with Zendesk.
REST is for backends and scheduled jobs. MCP is for AI agents — it’s the protocol Claude, ChatGPT, and Cursor speak. Pathbound’s MCP also unifies Zendesk with HubSpot, Gmail, your website tracker, and other sources into one profile per contact, so the agent doesn’t glue 6 APIs together itself.
Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue — any client that supports the Model Context Protocol with OAuth.
Today: OAuth Zendesk connection, scheduled sync of end-users, organizations, and tickets, identity resolution into the unified contact profile, and the full ticket history visible on the contact page in the Pathbound dashboard. The unified MCP tools (get_contact, get_contact_timeline, list_contacts) include Zendesk-sourced fields. Roadmap: ticket-specific MCP tools (list_tickets, get_ticket) and write actions (update status, assign, add comment).
End-users only. Pathbound's sync filters on role[]=end-user at the API layer, so your support staff aren't mixed into the unified contact directory.
OAuth 2.0 end to end. You enter your Zendesk subdomain, register Pathbound as an OAuth client in Zendesk Admin Center (one-time, ~5 min), and complete the standard OAuth handshake. The MCP client opens Pathbound's login; you log in once and the agent gets scoped access tied to your user. Revoke anytime from Settings → Connected Apps.
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. Drop in the tracker snippet. Connect one CRM. Point your MCP client at
mcp.pathbound.ai/mcp.