Autotask MCP — Claude Code MCP server: what it does, how to install
Connects your AI agent to Autotask PSA via a local SQLite replica. Surfaces aging tickets, engineer workloads, and unbilled time.
Open on GitHubWhat Autotask MCP does
This server pulls Autotask PSA records directly into a local SQLite database. Local caching enables the agent to inspect client history, flag forgotten service tickets, and audit billable hours without making repeated network calls to the cloud API.
The package provides two components: autotask-cli and autotask-mcp. Interactions with your agent rely on standard input and output (stdio). Avoid running --transport http in this release: the HTTP transport has no authentication guard, leaving your Autotask credentials exposed to any malicious browser script.
What it helps with
- audit aging tickets inside service queues
- track unbilled technician hours across client contracts
- retrieve full account profiles with linked records
- evaluate current team workload distribution
Example prompts for the agent
- Check Autotask for service tickets waiting on action for over 48 hours
- List all unbilled time entries logged this week across client accounts
- Look up client details in Autotask and summarize their open issues
How to install Autotask MCP
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Autotask MCP
How to install Autotask MCP in Claude Code?
Run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/autotask/install.sh) in your terminal. Next, add the plugin using /plugin marketplace add Servosity/msp-skills and /plugin install autotask@msp-skills.
What does Autotask MCP do?
It links your assistant to Autotask PSA records through a local SQLite database mirror. This architecture speeds up queries regarding technician time allocation, tickets, and customer accounts.
Can I run Autotask MCP over HTTP transport?
Do not enable --transport http. That mode lacks password validation and binds to all network interfaces, exposing your credentials to browser-based rebinding attacks.
