Zendesk MCP server for Claude & ChatGPT

What it looks like

What does Zendesk data look like in Claude?

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 website events, and your other sources.

MCP

Zendesk, exposed as MCP tools.

Claude · pathbound MCP connected

you

What do we know about [email protected]? Include Zendesk context.

↳ get_contact { email: "[email protected]" } 200 · 318 tokens · 510ms

contact Jane Reyes · Senior PM

company acme.com · fintech · 240

zendesk org = Acme Corp · verified end-user

↳ get_contact_timeline { contact_id: "ctc_01H..." } 12 events · 380ms

tracker visited /status · 4× last 24h

gmail CSM follow-up sent · yesterday

hubspot deal_stage = renewal · $48k ARR

claude

Jane is Senior PM at Acme (renewal, $48k ARR) and a verified Zendesk end-user under the Acme Corp organization. She hit /status four times in the last 24 hours and your CSM followed up yesterday. Same identity stitched across HubSpot, Gmail, your website events, and Zendesk.

signal Active renewal + repeat status-page visits. Worth a proactive check-in before next billing touch.

claude_desktop_config.json

{
  "mcpServers": {
    "pathbound": {
      "url": "https://mcp.pathbound.ai/mcp"
    }
  }
}

Zendesk tools out of the box · read

get_contact — unified profile—Zendesk end-user fields land alongside HubSpot, Gmail, website events

get_contact_timeline — page views, email replies, deal stage changes—identity-resolved with Zendesk users

list_contacts — filter the unified directory; Zendesk-only contacts show up alongside CRM contacts

get_company — company rollup that includes Zendesk organization domain + tags

aggregate_data — breakdowns by lifecycle stage, source, recency—Zendesk presence as a dimension

create_contact_note — log internal context that travels with the contact across every connected source

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.

Setup

How do I connect Zendesk to Claude?

OAuth one connector. Drop a snippet into your MCP client. Ask a question.

01

Sign up for Pathbound

Create an account at pathbound.ai. Free during public alpha.
02

Connect Zendesk

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.
03
Add Pathbound to your MCP client

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.
claude_desktop_config.json
```
{
  "mcpServers": {
    "pathbound": {
      "url": "https://mcp.pathbound.ai/mcp"
    }
  }
}
```
04

Run a test prompt

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.

Why Pathbound

Your customer doesn’t live only in Zendesk.

A direct Zendesk MCP shows your agent Zendesk. Pathbound shows your agent the customer—across Zendesk, HubSpot, Gmail, your website events, Apollo, Calendly, and the rest of your stack—through one unified profile served over the Model Context Protocol.

Beyond Zendesk

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.

Identity-resolved

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.

Built for LLMs

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.

Governed writes

Your agent can write, too—notes and profile updates land on the unified customer record, never on your Zendesk tickets. Source write-back, versioning, and rollback are rolling out—the controls SOC 2 and GDPR reviewers expect.

FAQ

Common questions.

Is this an official Zendesk MCP server?

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.

How is this different from the Zendesk REST API?

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 events, and other sources into one profile per contact, so the agent doesn’t glue six APIs together itself.

Which MCP clients does this work with?

Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue—any client that supports the Model Context Protocol with OAuth.

What exactly ships today vs. what’s on the roadmap?

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).

Does it sync agents or just end-users?

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.

How does authentication work?

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.

Is my customer data secure?

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.

What about HubSpot, Pipedrive, Intercom?

Same MCP server, same tools—just connect a different source. See the integrations directory.

Zendesk with Claude & ChatGPT—Zendesk MCP server