Zendesk MCP vs MCP Atlassian
A side-by-side look at the Zendesk MCP and MCP Atlassian MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Zendesk MCP for support & service management work as a local process; choose MCP Atlassian 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 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.
Choose MCP Atlassian 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:
JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN, JIRA_PERSONAL_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 56/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | ZENDESK_SUBDOMAINZENDESK_EMAILZENDESK_API_TOKEN | JIRA_URLJIRA_USERNAMEJIRA_API_TOKENJIRA_PERSONAL_TOKENCONFLUENCE_URLCONFLUENCE_USERNAMECONFLUENCE_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6,035 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 14 | Not listed |
| Full listing | View Zendesk MCP | View MCP Atlassian |
Tools & capabilities
Zendesk MCP tools 14
create_ticketCreate a Zendesk support ticket with correct requester attribution.get_ticketRetrieve details of an existing Zendesk ticket.update_ticketUpdate an existing Zendesk ticket (status, priority, add comment, or tags).search_ticketsSearch Zendesk tickets using the Zendesk Search API query syntax.list_recent_ticketsList the most recently updated Zendesk tickets.list_all_ticketsList tickets across the Zendesk instance, optionally filtered by status.list_tickets_for_requesterList tickets created for a specific requester email.get_ticket_commentsRetrieve comments and responses for a Zendesk ticket.add_ticket_commentAdd a comment to an existing Zendesk ticket.get_user_by_emailLook up a Zendesk user record by email address.close_ticketMark a Zendesk ticket as solved.reopen_ticketReopen a solved or closed Zendesk ticket.- +2 more on the listing page
MCP Atlassian tools
No tool names declared yet. Check the project README from 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.
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"
}
}
}
}
MCP Atlassian
{
"mcpServers": {
"sooperset-mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "YOUR_JIRA_URL_HERE",
"JIRA_USERNAME": "YOUR_JIRA_USERNAME_HERE",
"JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE",
"JIRA_PERSONAL_TOKEN": "YOUR_JIRA_PERSONAL_TOKEN_HERE",
"CONFLUENCE_URL": "YOUR_CONFLUENCE_URL_HERE",
"CONFLUENCE_USERNAME": "YOUR_CONFLUENCE_USERNAME_HERE",
"CONFLUENCE_API_TOKEN": "YOUR_CONFLUENCE_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Zendesk MCP is categorized under Support & Service Management and uses a local stdio subprocess. MCP Atlassian belongs to Support & Service Management and uses a local stdio subprocess. Pick Zendesk MCP for support & service management work and MCP Atlassian 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.
Zendesk MCP has no declared pricing — check the project's own site. MCP Atlassian is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 zendesk-mcp and sooperset-mcp-atlassian as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Zendesk MCP has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. MCP Atlassian has 49/100 (Fair) with 4 views, 0 installs and 6,035 GitHub stars.