A side-by-side look at the Zendesk MCP and Swifteq MCP Server for Zendesk MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Zendesk MCP for support & service management work as a local process; choose Swifteq MCP Server for Zendesk for support & service management over a hosted endpoint. You can also run both side by side in one mcpServers block.
zendesk_get_ticket, zendesk_search_tickets, zendesk_get_comments.Rows where the two servers differ are marked.
| Spec | S Swifteq MCP Server for Zendesk | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 61/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 29 | Not listed |
| Full listing | View Zendesk MCP | View Swifteq MCP Server for Zendesk |
zendesk_get_ticketGet a Zendesk ticket by ID. Returns ticket fields including status, priority, requester, assignee, tags, and description.zendesk_search_ticketsSearch Zendesk tickets by keyword and/or status. keywords: free-text search (e.g. 'login failure LDAP'). status: new, open, pending, hold, solved, closed — leave empty for all statuses. Returns id, subject, status, requester, assignee, and dates.zendesk_get_commentsGet all comments (public replies and internal notes) for a Zendesk ticket. Includes attachment metadata but does not download files.zendesk_list_attachmentsList all attachments across all comments for a Zendesk ticket. Returns filename, content type, size, and download URL for each. Use zendesk_download_attachment to fetch file contents.zendesk_download_attachmentDownload a Zendesk attachment. Obtain attachment_url and filename from zendesk_list_attachments. ticket_id is required for cache organization. Optional dest_dir overrides the default cache location (it must be inside the cache or a directory listed in 'attachment_allowed_dest_dirs' in the config); the file is written there and (for archives) extracted alongside it. Archives return a file list and unpack_dir — read individual files with your normal file tools. PDFs return up to ~500KB of extracted text. Images are base64-encoded.zendesk_ticket_to_gitlab_contextFormat a Zendesk ticket and its comments as an issue draft. Returns Markdown with ticket metadata, full conversation, and an empty Steps to Reproduce section. Use this output as the description when creating an issue in your tracker.zendesk_post_commentPost a public reply on a Zendesk ticket. The reply is visible to the requester. Use for customer-facing responses.zendesk_post_internal_notePost an internal note on a Zendesk ticket. Internal notes are only visible to agents and are not sent to the requester.zendesk_set_ticket_statusSet the status of a Zendesk ticket. Valid statuses: new, open, pending, hold, solved, closed.zendesk_assign_ticketAssign a Zendesk ticket to an agent by their email address. Pass 'me' as assignee_email to assign the ticket to yourself (the authenticated user).zendesk_update_ticketUpdate one or more fields on a Zendesk ticket. Pass only the fields you want to change. status: new/open/pending/hold/solved/closed. priority: low/normal/high/urgent. type: problem/incident/question/task. assignee_id, requester_id, group_id, custom_status_id are integer IDs. due_at is ISO8601. Returns JSON of the refreshed ticket.zendesk_get_time_trackingGet time tracking data for a Zendesk ticket. Returns total time spent and time spent on the last update, in both seconds and human-readable format (e.g. '2h 15m').No tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"michaelrice-zendesk-mcp": {
"command": "uvx",
"args": [
"zendesk-mcp"
]
}
}
}
{
"mcpServers": {
"swifteq-mcp-server-for-zendesk": {
"command": "npx",
"args": [
"-y",
"swifteq-mcp-server-for-zendesk"
]
}
}
}