A side-by-side look at the HellouOne 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 HellouOne for support & service management work; choose Zendesk MCP for support & service management as a local process. You can also run both side by side in one mcpServers block.
ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, ZENDESK_API_TOKEN.create_ticket, get_ticket, update_ticket.Rows where the two servers differ are marked.
| Spec | H HellouOne | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 37/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View HellouOne | View Zendesk MCP |
No tool names declared yet. Check the project README from the listing page.
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 ticketPaste 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.
No confirmed install command for HellouOne yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"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"
}
}
}
}