Autotask vs MCP FreeScout
A side-by-side look at the Autotask and MCP FreeScout 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 MCP FreeScout 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 Autotask when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- 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 MCP FreeScout when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FREESCOUT_URL, FREESCOUT_API_KEY. - You want tools like
freescout_get_ticket, freescout_analyze_ticket, freescout_add_note.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 56/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AUTOTASK_USERNAMEAUTOTASK_SECRETAUTOTASK_INTEGRATION_CODE | FREESCOUT_URLFREESCOUT_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 58 | 29 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 30 | 8 |
| Full listing | View Autotask | View MCP FreeScout |
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
MCP FreeScout tools 8
freescout_get_ticketFetch a FreeScout ticket with all its details and conversation threads.freescout_analyze_ticketAnalyze a ticket to determine issue type, root cause, and suggested solutions.freescout_add_noteAdd an internal note to a ticket for team communication.freescout_update_ticketUpdate ticket status and/or assignment.freescout_create_draft_replyCreate a draft reply in FreeScout that can be edited before sending. This tool lets the LLM generate the reply content and saves it directly to FreeScout as a draft. **Automatically converts Markdown formatting to HTML** for proper display in FreeScout.freescout_get_ticket_contextGet ticket context and customer information to help craft personalized replies.freescout_search_ticketsSearch for tickets across your FreeScout instance.freescout_get_mailboxesGet a list of all available mailboxes in your FreeScout instance.
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": {
"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"
}
}
}
}
MCP FreeScout
{
"mcpServers": {
"mcp-freescout": {
"command": "npx",
"args": [
"@verygoodplugins/mcp-freescout@latest"
],
"env": {
"FREESCOUT_URL": "YOUR_FREESCOUT_URL_HERE",
"FREESCOUT_API_KEY": "YOUR_FREESCOUT_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Autotask is categorized under Support & Service Management and uses a local stdio subprocess. MCP FreeScout belongs to Support & Service Management and uses a local stdio subprocess. Pick Autotask for support & service management work and MCP FreeScout 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. MCP FreeScout 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 and mcp-freescout 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 56/100 (Good) with 1 views, 0 installs and 58 GitHub stars. MCP FreeScout has 60/100 (Good) with 0 views, 0 installs and 29 GitHub stars.