In-depth architectural comparison of the Invgate Service Desk MCP and Zendesk MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Invgate Service Desk MCP
Support & Service Management · Local stdio
Quality: 49/100 (Fair) | Auth: API Key required
Zendesk MCP
Support & Service Management · Local stdio
Quality: 51/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Invgate Service Desk MCP if you need specialized Support & Service Management tools running via a local process. Choose Zendesk MCP if your workspace requires Support & Service Management integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Invgate Service Desk MCP when:
You need dedicated capabilities in the Support & Service Management domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: INVGATE_BASE_URL, INVGATE_API_TOKEN, INVGATE_WRITE_PROFILE.
Primary tools included: 96 tools spanning incidents, users, assets, workflows, and more, Read-only access enabled by default, Optional write operations for incidents, time tracking, and knowledge base.
MCP server for InvGate Service Desk: 96 tools across 11 domains (incidents, users, knowledge base, assets, custom fields, workflows, time tracking), read-only by default with opt-in writes.
MCP server for Zendesk. Read/write tools for tickets, comments, views, macros, users, groups, organizations, and time tracking; optional Help Center knowledge base and Git-Zen GitLab integration.
Category & Scope
Tools & Capabilities Breakdown
Invgate Service Desk MCP Tools (6)
96 tools spanning incidents, users, assets, workflows, and more
Read-only access enabled by default
Optional write operations for incidents, time tracking, and knowledge base
Supports searching, listing, creating, updating, and commenting
Authentication via API token with HTTP Basic
Prebuilt MCP bundle for easy installation with compatible clients
Zendesk MCP Tools (29)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Invgate Service Desk MCP is categorized under Support & Service Management and uses a local stdio subprocess. In contrast, Zendesk MCP belongs to Support & Service Management using local stdio subprocess. Select Invgate Service Desk MCP when you need capabilities focused on support & service management and Zendesk MCP when you require tools for support & service management.
Search tickets by status, priority, type, assignee, requester, tags, or keyword
zendesk_get_tickets
List tickets with pagination and sorting (page, per_page, sort_by, sort_order)
zendesk_get_ticket
Get one ticket's metadata
zendesk_create_ticket
Create a new ticket (subject, description, optional priority/type/assignee_id/requester_id/tags/custom_fields)
zendesk_update_ticket
Update one or more fields on an existing ticket (status, priority, subject, type, assignee_id, requester_id, group_id, custom_status_id, tags, custom_fields, due_at)
zendesk_get_comments
Get the conversation thread on a ticket
zendesk_list_attachments
List attachments on a ticket
zendesk_download_attachment
Download an attachment to a local cache directory
zendesk_ticket_to_gitlab_context
Format a ticket and its conversation as a Markdown issue draft
zendesk_post_comment
Post a public reply on a ticket
zendesk_post_internal_note
Post an agent-only internal note on a ticket
zendesk_set_ticket_status
Set ticket status (`new`, `open`, `pending`, `hold`, `solved`, `closed`)