Autotask MCP server
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
B70/100grade B
Adoption
Growing
53 stars
Reviews
Write oneNobody has reviewed Autotask yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Autotask tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add autotask-mcp -- docker run -i --rm ghcr.io/wyre-ai/autotask-mcp:v2.38.0
Autotask: common questions
- Is Autotask MCP server safe?
- Mostly: it is graded B (70/100). Read the Autotask safety report
- How do I install Autotask?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Autotask need an API key?
- Yes. The registry entry asks for
AUTOTASK_SECRET,AUTOTASK_INTEGRATION_CODE. - Is Autotask maintained?
- The last commit was in the last day (2026-09-19). The latest release is v2.38.0.