Weav vs Zendesk MCP
A side-by-side look at the Weav 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 Weav for support & service management work over a hosted endpoint; 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 Weav when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
status, priority, type.
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 | 47/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ZENDESK_SUBDOMAINZENDESK_EMAILZENDESK_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 14 |
| Full listing | View Weav | View Zendesk MCP |
Tools & capabilities
Weav tools 3
status`open` or `closed`priority`low`, `normal`, `high`, or `urgent`type`text`, `qa`, or `url`
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.
Weav
{
"mcpServers": {
"weav": {
"url": "https://mcp.weav.com/mcp"
}
}
}
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
Weav is categorized under Support & Service Management and uses a remote HTTP/SSE transport. Zendesk MCP belongs to Support & Service Management and uses a local stdio subprocess. Pick Weav 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.
Weav has no declared pricing — check the project's own site. 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 weav and zendesk-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Weav has a quality signal of 47/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.