Magic MCP vs Autotask
A side-by-side look at the Magic MCP and Autotask MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Magic MCP for architecture & design work as a local process; choose Autotask 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 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.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Support & Service Management |
| Quality signal | 53/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | other |
| Pricing | Paid service | Not declared |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST | AUTOTASK_USERNAMEAUTOTASK_SECRETAUTOTASK_INTEGRATION_CODECONDUIT_S2S_SECRETAUTH_MODE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6,217 | 58 |
| Directory activity | 16 views 1 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 30 |
| Full listing | View Magic MCP | View Autotask |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
Autotask tools 30
autotask_search_companiesSearch companies with filtersautotask_create_companyCreate new companyautotask_update_companyUpdate existing companyautotask_search_contactsSearch contacts with filtersautotask_create_contactCreate new contactautotask_search_ticketsSearch tickets with filtersautotask_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 ticketautotask_create_time_entryLog time entryautotask_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 itemsautotask_get_billing_itemGet specific billing item by ID- +18 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.
Magic MCP
{
"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"
}
}
}
}
Autotask
{
"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"
}
}
}
}
Frequently asked questions
Magic MCP is categorized under Architecture & Design and uses a local stdio subprocess. Autotask belongs to Support & Service Management and uses a local stdio subprocess. Pick Magic MCP for architecture & design work and Autotask 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.
Magic MCP is listed as a paid service. Auth: api key required. Autotask has no declared pricing — check the project's own site. Auth: other. 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 21st-dev-magic-mcp and autotask-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic MCP has a quality signal of 53/100 (Good) with 16 views, 1 installs and 6,217 GitHub stars. Autotask has 59/100 (Good) with 6 views, 0 installs and 58 GitHub stars.