What is the key difference between Zendesk MCP and Autotask?

Zendesk MCP belongs to the Support & Service Management category with local stdio execution, while Autotask belongs to the Support & Service Management category with local stdio execution.

How do I install Zendesk MCP or Autotask in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Zendesk MCP and Autotask free or paid?

Zendesk MCP operates under a BYOK (Pay Provider Direct) model (OAuth 2.0). Autotask operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Zendesk MCP lists 29 tools with 2 views and 7 GitHub stars. Autotask lists 29 tools with 0 views and 53 GitHub stars.

Can I use both Zendesk MCP and Autotask together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Zendesk MCP vs Autotask

In-depth architectural comparison of the Zendesk MCP and Autotask 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

Zendesk MCP

Support & Service Management · Local stdio

Quality: 51/100 (Good) | Auth: OAuth 2.0

Autotask

Support & Service Management · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Verdict Summary: Choose Zendesk MCP if you need specialized Support & Service Management tools running via a local process. Choose Autotask 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 Zendesk 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 (BYOK (Pay Provider Direct)).
You have access to required keys: ZENDESK_SUBDOMAIN, ZENDESK_OAUTH_CLIENT_ID, ZENDESK_OAUTH_CLIENT_SECRET, ZENDESK_OAUTH_TOKEN_PATH.
Primary tools included: zendesk_search_tickets, zendesk_get_tickets, zendesk_get_ticket.

Explore Zendesk MCP Details

Choose Autotask when:

You need dedicated capabilities in the Support & Service Management domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: autotask_search_companies, autotask_create_company, autotask_update_company.

Feature & Specification Comparison

Specification	Zendesk MCP michaelrice Support & Service Management	Autotask Support & Service Management
Summary	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.	MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
Category & Scope	Support & Service Management

Tools & Capabilities Breakdown

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

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).

Zendesk MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "michaelrice-zendesk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "michaelrice-zendesk-mcp"
      ],
      "env": {
        "ZENDESK_SUBDOMAIN": "YOUR_ZENDESK_SUBDOMAIN_HERE",
        "ZENDESK_OAUTH_CLIENT_ID": "YOUR_ZENDESK_OAUTH_CLIENT_ID_HERE",
        "ZENDESK_OAUTH_CLIENT_SECRET": "YOUR_ZENDESK_OAUTH_CLIENT_SECRET_HERE",
        "ZENDESK_OAUTH_TOKEN_PATH": "YOUR_ZENDESK_OAUTH_TOKEN_PATH_HERE"
      }
    }
  }
}

Autotask Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "autotask": {
      "command": "npx",
      "args": [
        "-y",
        "github:WYRE-AI/autotask-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Zendesk MCP is categorized under Support & Service Management and uses a local stdio subprocess. In contrast, Autotask belongs to Support & Service Management using local stdio subprocess. Select Zendesk MCP when you need capabilities focused on support & service management and Autotask when you require tools for support & service management.

More alternatives to Zendesk MCP More alternatives to Autotask Support & Service Management category hub Canonical compare URL