Autotask vs Exa MCP Server
A side-by-side look at the Autotask and Exa MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Autotask for support & service management work as a local process; choose Exa MCP Server for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Exa MCP Server when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
web_search_exa, web_fetch_exa.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Search & Data Extraction |
| Quality signal | 59/100 · Good | 73/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | No auth required |
| Pricing | Not declared | Free |
| Required env vars | AUTOTASK_USERNAMEAUTOTASK_SECRETAUTOTASK_INTEGRATION_CODECONDUIT_S2S_SECRETAUTH_MODE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 58 | 5,161 |
| Directory activity | 6 views 0 installs 0 upvotes | 11 views 0 installs 0 upvotes |
| Tools | 30 | 2 |
| Full listing | View Autotask | View Exa MCP Server |
Tools & capabilities
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
Exa MCP Server tools 2
web_search_exaSearch the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.web_fetch_exaRead a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL. Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s).
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": {
"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"
}
}
}
}
Exa MCP Server
{
"mcpServers": {
"exa-labs-exa-mcp-server": {
"command": "npx",
"args": [
"-y",
"exa-mcp-server"
]
}
}
}
Frequently asked questions
Autotask is categorized under Support & Service Management and uses a local stdio subprocess. Exa MCP Server belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Autotask for support & service management work and Exa MCP Server for search & data extraction.
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. Exa MCP Server is listed as free. Auth: no auth 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 exa-labs-exa-mcp-server 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. Exa MCP Server has 73/100 (Great) with 11 views, 0 installs and 5,161 GitHub stars.