Jobber MCP vs Zendesk MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Jobber MCP vs Zendesk MCP
In-depth architectural comparison of the Jobber 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
Jobber MCP
Support & Service Management · Local stdio
Quality: 52/100 (Good) | Auth: OAuth 2.0
Zendesk MCP
Support & Service Management · Local stdio
Quality: 51/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Jobber 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 Jobber MCP when:
You need dedicated capabilities in the Support & Service Management domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Paid Service).
You have access to required keys: JOBBER_CLIENT_ID, JOBBER_CLIENT_SECRET.
Customer-hosted, read-only MCP server for Jobber operations queries: owner action lists, overdue invoices, stale requests, estimates, jobs, and safe read-only GraphQL validation.
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
Jobber MCP Tools (6)
jobber_auth_url
create the one-time Jobber OAuth authorization link for a customer-hosted install.
jobber_exchange_code
exchange the redirected OAuth code and store tokens locally without exposing them in chat.
jobber_refresh_token
refresh the stored access token for continued read-only reporting.
jobber_account
validate the connected account before running operational queries.
jobber_clients_sample
validate read access with a capped client sample.
jobber_graphql_read
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).
Jobber 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 Jobber MCP when you need capabilities focused on support & service management and Zendesk MCP when you require tools for support & service management.
run read-only Jobber GraphQL for owner reports; mutations are blocked before sending.
Zendesk MCP Tools (29)
zendesk_search_tickets
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`)