Autotask vs Freshdesk MCP
A side-by-side look at the Autotask and Freshdesk MCP 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 Freshdesk MCP for support & service management over a hosted endpoint. 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. - You want tools like
autotask_search_companies, autotask_create_company, autotask_update_company.
Choose Freshdesk MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_ticket, get_ticket_summary, batch_get_ticket_summaries.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 57/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | other | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AUTOTASK_USERNAMEAUTOTASK_SECRETAUTOTASK_INTEGRATION_CODE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 58 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 30 | 15 |
| Full listing | View Autotask | View Freshdesk MCP |
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 full ticket details by IDautotask_create_ticketCreate new ticketautotask_create_time_entryLog time entryautotask_search_time_entriesSearch time entries with filters (resource, ticket, task, date range)autotask_search_billing_itemsSearch approved and posted billing itemsautotask_get_billing_itemGet specific billing item by ID- +18 more on the listing page
Freshdesk MCP tools 15
get_ticketFetch a single ticket by ID. Returns status name, group name, company ID.get_ticket_summaryTicket + all conversations + attachments in one call.batch_get_ticket_summariesMultiple ticket summaries in parallel.search_ticketsFilter by query, status, priority, type, overdue, escalated, dates, company, requester, agent, group. Full ticket history.list_ticketsAll tickets with optional filters.get_conversationsAll replies and notes for a ticket (fully paginated).list_attachmentsAll attachments across ticket and conversations. Filters scanning placeholders.get_attachment_textExtract text from docx, xlsx, json, txt, csv, png, jpg (Vision OCR).query_attachmentSearch within a JSON attachment.find_image_attachmentsScan multiple tickets for image attachments.get_description_imagesOCR inline images in ticket description HTML and conversation replies.find_requesterSearch contacts by name/email → requester_id.- +3 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.
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"
}
}
}
}
Freshdesk MCP
{
"mcpServers": {
"omnom62-freshdesk-mcp": {
"url": "https://your-deployment-url/mcp"
}
}
}
Frequently asked questions
Autotask is categorized under Support & Service Management and uses a local stdio subprocess. Freshdesk MCP belongs to Support & Service Management and uses a remote HTTP/SSE transport. Pick Autotask for support & service management work and Freshdesk MCP 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.
Autotask has no declared pricing — check the project's own site. Auth: other. Freshdesk MCP has no declared pricing — check the project's own site. 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 omnom62-freshdesk-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 57/100 (Good) with 2 views, 0 installs and 58 GitHub stars. Freshdesk MCP has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.