Autotask vs Magic MCP

A side-by-side look at the Autotask and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Autotask logoAutotaskSupport & Service Management · Local subprocess (stdio)MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.59GoodAuth: otherMagic MCP logoMagic MCPArchitecture & Design · Local subprocess (stdio)Create crafted UI components inspired by the best 21st.dev design engineers.53GoodAuth: api key required

Verdict: choose Autotask for support & service management work as a local process; choose Magic MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Autotask logoChoose Autotask when

  • You need dedicated capabilities in the Support & Service Management domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: AUTOTASK_USERNAME, AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, CONDUIT_S2S_SECRET, AUTH_MODE.
  • You want tools like autotask_search_companies, autotask_create_company, autotask_update_company.
Explore Autotask

Magic MCP logoChoose Magic MCP when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: TWENTY_FIRST_API_KEY, API_KEY_21ST.
Explore Magic MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAutotask logoAutotaskMagic MCP logoMagic MCP
CategorySupport & Service ManagementArchitecture & Design
Quality signal59/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthotherAPI key required
PricingNot declaredPaid service
Required env varsAUTOTASK_USERNAMEAUTOTASK_SECRETAUTOTASK_INTEGRATION_CODECONDUIT_S2S_SECRETAUTH_MODETWENTY_FIRST_API_KEYAPI_KEY_21ST
Verified ownerCommunity listingCommunity listing
GitHub stars586,217
Directory activity 6 views 0 installs 0 upvotes 16 views 1 installs 0 upvotes
Tools30Not listed

Tools & capabilities

Autotask tools 30

  • autotask_search_companiesSearch companies with filters
  • autotask_create_companyCreate new company
  • autotask_update_companyUpdate existing company
  • autotask_search_contactsSearch contacts with filters
  • autotask_create_contactCreate new contact
  • autotask_search_ticketsSearch tickets with filters
  • autotask_get_ticket_detailsGet a ticket by ID: description, status/priority/queue, company, contact, assignee, dates, linked configuration item, resolution, custom fields (UDFs), recent notes and the full record (`fullDetails: true` for untruncated text and all UDFs)
  • autotask_create_ticketCreate new ticket
  • autotask_create_time_entryLog time entry
  • autotask_search_time_entriesSearch time entries with filters (resource, ticket, task, date range); each entry includes `summaryNotes` and `internalNotes`
  • autotask_search_billing_itemsSearch approved and posted billing items
  • autotask_get_billing_itemGet specific billing item by ID
  • +18 more on the listing page

Magic MCP 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.

Autotask

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "autotask-2": {
      "command": "npx",
      "args": [
        "-y",
        "github:WYRE-AI/autotask-mcp"
      ],
      "env": {
        "AUTOTASK_USERNAME": "YOUR_AUTOTASK_USERNAME_HERE",
        "AUTOTASK_SECRET": "YOUR_AUTOTASK_SECRET_HERE",
        "AUTOTASK_INTEGRATION_CODE": "YOUR_AUTOTASK_INTEGRATION_CODE_HERE",
        "CONDUIT_S2S_SECRET": "YOUR_CONDUIT_S2S_SECRET_HERE",
        "AUTH_MODE": "YOUR_AUTH_MODE_HERE"
      }
    }
  }
}

Magic MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "21st-dev-magic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@21st-dev/cli@latest"
      ],
      "env": {
        "TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
        "API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
      }
    }
  }
}

Frequently asked questions

Autotask is categorized under Support & Service Management and uses a local stdio subprocess. Magic MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Autotask for support & service management work and Magic MCP for architecture & design.

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.

Autotask has no declared pricing — check the project's own site. Auth: other. Magic MCP is listed as a paid service. 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 autotask-2 and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Autotask has a quality signal of 59/100 (Good) with 6 views, 0 installs and 58 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 6,217 GitHub stars.