Zendesk
Customer support and ticketing.
Verdict
Common use cases
- Triage new tickets during morning standup
- Draft responses to escalated customer issues
- Audit organization records before renewal calls
- Create follow-up tickets from Slack threads
- Pull ticket history into client strategy sessions
Integration
- Vendor
- Zendesk
- Category
- crm
- Auth
- OAUTH2
- Tools
- 12
- Composio slug
zendesk
Tools
- Count Zendesk Organizations
Count the number of organizations in zendesk.
- Create Zendesk Organization
Create an organization in zendesk.
- Create Zendesk Ticket
Create a ticket in zendesk.
- Delete Zendesk Organizationdestructive
Delete an organization in zendesk.
- Delete Zendesk Ticketdestructive
Delete a ticket in zendesk.
- Get Zendesk About Me
Get information about the owner account in zendesk.
- Get Zendesk Organization
Get information about a specific organization in zendesk.
- Get Zendesk Organizations
Get all organizations in zendesk.
- Get Zendesk Ticket
Get ticket details from zendesk.
- List Tickets
List zendesk tickets with pagination and filtering.
- Reply to Zendesk Ticket
Action to reply to a zendesk ticket by adding a comment.
- Update Zendesk Organization
Update an organization in zendesk.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Find Zendesk in the MCP directory and click Connect. 3. You'll be redirected to Zendesk's OAuth consent screen — sign in with an account that has admin permissions. 4. Review the requested scopes: read and write access to tickets, organizations, and user profiles. 5. Click Authorize to grant access and return to Switchy. 6. Back in Switchy, open any Space and type '@Zendesk get information about the owner account' to confirm the connection works. 7. If the MCP responds with your account details, setup is complete. 8. To invoke tools in a conversation, @mention Zendesk followed by your request — for example, '@Zendesk create a ticket for billing issue reported by Acme Corp'. 9. The MCP will execute the action and return results inline, so your team can continue the discussion without switching tabs.
What teammates see: by default, memories from Zendesk are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Triage Open Tickets
@Zendesk show me all open tickets created in the last 24 hours, grouped by priority level.Open in a Space →
Create Escalation Ticket
@Zendesk create a high-priority ticket titled 'API timeout affecting Enterprise customers' and assign it to the engineering team.Open in a Space →
Check Organization Details
@Zendesk get all details for the organization named 'Acme Corporation', including recent ticket activity.Open in a Space →
Bulk Update Organizations
@Zendesk update the 'account tier' field to 'Enterprise' for organizations with more than 500 users.Open in a Space →
Close Resolved Tickets
@Zendesk close all tickets tagged 'bug-fix-deployed' that were updated more than 48 hours ago.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@zendesk show me all open tickets from Acme Corp that mention billing issues in the last 7 days
Found 4 open tickets from Acme Corp mentioning billing in the past week: • Ticket #8821 (Priority: High) - "Invoice discrepancy for March billing cycle" - Created 2 days ago by sarah@acmecorp.com • Ticket #8798 (Priority: Normal) - "Question about payment method update" - Created 4 days ago by finance@acmecorp.com • Ticket #8776 (Priority: Normal) - "Duplicate charge on credit card" - Created 6 days ago by john@acmecorp.com • Ticket #8765 (Priority: Low) - "Request for billing history export" - Created 7 days ago by admin@acmecorp.com All tickets are currently assigned to the Billing team queue.
This example demonstrates cross-referencing organization data with ticket search. The MCP requires read access to both tickets and organizations. Response time depends on your Zendesk instance size — accounts with 100k+ tickets may see slower queries. The actual ticket fields returned vary by your custom configuration.
@zendesk create a high-priority ticket for TechStart Inc about their API integration failing, assign it to the engineering team
Created ticket #8847 successfully: • Organization: TechStart Inc (ID: 360012847) • Subject: "API integration failing" • Priority: High • Status: Open • Assignee: Engineering team group • Requester: Set to your account (you can update this manually) • Ticket URL: https://yourcompany.zendesk.com/agent/tickets/8847 The ticket is now visible in the Engineering team's queue. Note that no email notification was sent to TechStart Inc since no specific requester email was provided.
This write action creates a real ticket in your Zendesk instance immediately. The MCP needs ticket creation permissions and organization read access to link the org correctly. Be aware that ticket creation triggers any active automations or triggers you've configured in Zendesk — this could send emails, update fields, or notify Slack channels.
@zendesk pull all organizations created in the last 30 days and summarize which industries they're from based on their names and notes
Retrieved 23 organizations created in the past month. Based on organization names and available notes fields: **SaaS/Technology (12 orgs)**: CloudSync Solutions, DataFlow Analytics, APIFirst Inc, and 9 others — mostly mid-market software companies requesting API documentation and integration support. **Healthcare (6 orgs)**: MedTech Partners, HealthBridge Clinic, CareConnect Systems — focused on HIPAA compliance questions and secure data handling. **Financial Services (3 orgs)**: FinSecure LLC, Capital Advisors Group, PayStream — primarily inquiring about SOC 2 certification and audit trails. **Other (2 orgs)**: One manufacturing company, one educational institution. The SaaS segment shows the highest ticket volume per organization (avg 4.2 tickets each).
This synthesis example combines the MCP's organization listing with the AI's pattern recognition. The categorization is interpretive — Zendesk doesn't enforce industry taxonomy, so accuracy depends on how consistently your team populates org metadata. The MCP returns raw organization data; the AI infers industry from text fields, which may misclassify ambiguous names.
Use-case deep-dives
When Zendesk MCP speeds up morning ticket review
A 5-person support team starts each day reviewing overnight tickets and assigning them by customer tier. The Zendesk MCP lets them pull ticket lists, check organization details, and create follow-up tickets without leaving their shared AI workspace. The OAuth2 flow means each agent authenticates once and the team can query ticket counts or org info in natural language during standup. This works well if your ticket volume stays under 200 new tickets per day—beyond that, you'll want dedicated Zendesk views instead of ad-hoc MCP queries. If your team spends 15+ minutes each morning context-switching between Slack, Zendesk, and your CRM, this MCP collapses that into one conversation and cuts triage time in half.
Why this MCP matters for account setup workflows
A 3-person customer success team onboards 4-6 enterprise clients per quarter, each requiring a new Zendesk organization, custom ticket tags, and initial support tickets. The Zendesk MCP's create and get organization tools let them script the entire setup inside Switchy without opening the Zendesk admin panel. They authenticate once via OAuth2, then run a shared prompt that creates the org, verifies the setup, and logs the new account ID for handoff to sales ops. This scenario breaks down if you need advanced org fields or SLA policies—the MCP covers basic CRUD but won't configure Zendesk's deeper settings. If your onboarding checklist includes 'create Zendesk org' as a manual step more than twice a month, this MCP automates it and keeps the team in one workspace.
When Zendesk MCP helps product teams mine support data
A 4-person product team runs a quarterly feedback sprint where they pull common support themes from Zendesk to inform the roadmap. The Zendesk MCP lets them query ticket counts by keyword, retrieve org details for high-value customers, and export ticket summaries without waiting on support to run reports. The 12 available tools cover the read-heavy workflow—get tickets, count orgs, check account info—so the product manager can ask 'how many tickets mention billing errors from enterprise orgs this quarter' and get an answer in seconds. This falls apart if your Zendesk instance has complex custom fields or macros the MCP can't access. If your product team currently emails support for ticket exports or waits days for a Zendesk report, this MCP gives them self-service access and shortens the feedback loop to minutes.
Frequently asked
What does the Zendesk MCP do in Switchy?
It lets your team create, read, update, and delete Zendesk tickets and organizations directly from Switchy's AI workspace. You can count orgs, pull customer details, or spin up support tickets without switching tabs. It's built for teams who triage support issues or manage customer accounts in Zendesk and want AI to handle the repetitive lookups and data entry.
Do I need admin access to connect Zendesk via OAuth?
You need a Zendesk account with API access enabled. Most Zendesk plans grant this to agents by default, but your workspace admin controls OAuth app approvals. If your Zendesk instance restricts third-party OAuth apps, you'll need an admin to whitelist Switchy before you can authenticate. Check your Zendesk security settings or ask your IT lead.
Can the Zendesk MCP read ticket comments or attachments?
No. The current tool set focuses on ticket and organization CRUD operations—creating tickets, fetching org details, counting records. It doesn't expose comment threads, file attachments, or ticket history. If you need to pull conversation context into Switchy, you'll still need to open Zendesk or use a custom API call outside this MCP.
How is this different from just using Zendesk's web UI?
The MCP turns Zendesk actions into AI-callable functions. Instead of clicking through five screens to create a ticket or look up an org, you describe what you want in plain English and Switchy executes it. It's faster for bulk operations and lets you chain Zendesk tasks with other tools in a single workflow—like pulling a Slack thread, creating a ticket, then logging it in Notion.
Who on the team should connect the Zendesk integration?
Whoever owns support triage or customer success ops. That person's Zendesk credentials determine which tickets and orgs the MCP can access, so pick someone with the right permissions. If multiple people need it, each can connect their own Zendesk account in Switchy—connections are per-user, not shared across the workspace.