Matrix42 vs Zendesk MCP
A side-by-side look at the Matrix42 and Zendesk MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Matrix42 for support & service management work as a local process; choose Zendesk MCP for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Matrix42 when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
M42_HOST, M42_API_TOKEN, M42_USERNAME, M42_PASSWORD.
Choose Zendesk MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, ZENDESK_API_TOKEN. - You want tools like
create_ticket, get_ticket, update_ticket.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 37/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | M42_HOSTM42_API_TOKENM42_USERNAMEM42_PASSWORD |
Tools & capabilities
Matrix42 tools
No tool names declared yet. Check the project README from the listing page.
Zendesk MCP tools 14
create_ticketCreate ticket with correct requester attributionget_ticketGet ticket by IDupdate_ticketUpdate status, priority, tags, or commentsearch_ticketsZendesk search query syntaxlist_recent_ticketsRecently updated ticketslist_all_ticketsAdmin-wide ticket listinglist_tickets_for_requesterTickets for a requester emailget_ticket_commentsRead ticket conversationadd_ticket_commentAdd public reply or internal noteget_user_by_emailLook up Zendesk userclose_ticketMark ticket solvedreopen_ticketReopen solved/closed ticket- +2 more on the listing page
Ready-to-paste client configs
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.
Matrix42
{
"mcpServers": {
"matrix42": {
"command": "npx",
"args": [
"-y",
"matrix42-mcp"
],
"env": {
"M42_HOST": "YOUR_M42_HOST_HERE",
"M42_API_TOKEN": "YOUR_M42_API_TOKEN_HERE",
"M42_USERNAME": "YOUR_M42_USERNAME_HERE",
"M42_PASSWORD": "YOUR_M42_PASSWORD_HERE"
}
}
}
}
Zendesk MCP
{
"mcpServers": {
"zendesk-mcp": {
"command": "npx",
"args": [
"-y",
"@markusvankempen/zendesk-mcp-server"
],
"env": {
"ZENDESK_SUBDOMAIN": "YOUR_ZENDESK_SUBDOMAIN_HERE",
"ZENDESK_EMAIL": "YOUR_ZENDESK_EMAIL_HERE",
"ZENDESK_API_TOKEN": "YOUR_ZENDESK_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Matrix42 is categorized under Support & Service Management and uses a local stdio subprocess. Zendesk MCP belongs to Support & Service Management and uses a local stdio subprocess. Pick Matrix42 for support & service management work and Zendesk MCP for support & service management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Matrix42 is listed as free. Auth: api key required. Zendesk MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add matrix42 and zendesk-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Matrix42 has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Zendesk MCP has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.