Autotask vs HellouOne
A side-by-side look at the Autotask and HellouOne MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
HellouOneSupport & Service ManagementCustomer conversations, contacts, inboxes, agents, automations and reports of a HellouOne account.37FairAuth: not declaredVerdict: choose Autotask for support & service management work as a local process; choose HellouOne for support & service management. 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.
HChoose HellouOne when
- You need dedicated capabilities in the Support & Service Management domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H HellouOne | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 56/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | 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 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 30 | Not listed |
| Full listing | View Autotask | View HellouOne |
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
HellouOne 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": {
"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"
}
}
}
}
HellouOne
No confirmed install command for HellouOne yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Autotask is categorized under Support & Service Management and uses a local stdio subprocess. HellouOne belongs to Support & Service Management and uses an install path we have not confirmed yet. Pick Autotask for support & service management work and HellouOne 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. HellouOne has no confirmed install command yet — follow its own setup instructions.
Autotask has no declared pricing — check the project's own site. HellouOne 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 hellouone 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. HellouOne has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.