Autotask PSA MCP Server

A Model Context Protocol server that lets AI agents on the MSPbots Agent Platform work with Autotask PSA: companies, contacts, tickets and their notes, checklists, charges, history and attachments, time entries, projects, sales, contracts, billing, expenses and service calls.

It runs as a stateless HTTP service behind the MSPbots MCP gateway. The gateway sends each tenant's Autotask credentials as request headers on every call; the server keeps nothing between requests.

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: IT Glue MCP Server

Credentials (request headers)

Header names are case-insensitive. A request to /mcp without X-Api-Key or X-Api-Secret gets 401 with the list of expected headers. The middleware only checks that the required headers are present: header formats are validated by the tools, so initialize and tools/list succeed with any non-empty values (the platform probes with placeholders).

Tools

All 111 tool names and parameters match the previous Autotask connector on the MSPbots Agent Platform, so existing agents keep working. That compatibility is why this is one server with far more than 20 tools rather than several smaller ones. Every tool is always listed; the discovery tools only describe categories, dispatch to another tool by name, or suggest a tool from a plain text intent, and keep no state.

Behaviour notes:

• Every tool returns a JSON string. Errors use one envelope: {"error": {"code": "...", "message": "...", "retryable": false}} with code one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error.

• List tools return {"items", "count", "page_number", "page_size", "has_more"}. pageSize defaults to 25 and is capped at 200 (larger values are accepted and capped). Autotask has no offset, so page > 1 is read by skipping record IDs. Results larger than 20,000 characters are cut and flagged with truncated / has_more. Null fields are left out of results.

• Some zones do not register collection-level write routes (POST/PATCH /Contacts answers with an HTML 404). Writes to child entities fall back to the parent URL (e.g. /Companies/{companyID}/Contacts, /Tickets/{id}/Notes) when the zone answers 404 or 405.

• A ticket's Work Type is billingCodeID, a reference to BillingCodes, not a picklist: autotask_get_field_info cannot list it; use autotask_search_billing_codes (useType 1 = Work Type, 3 = internal time).

• Ticket assignments and ticket/task time entries need a role; it is resolved from the resource's roles when unambiguous, otherwise the error names the candidate roles.

• autotask_search_tickets without status returns open tickets only (status is not Complete).

• Transient failures (429, 5xx, timeouts) are retried with backoff, honouring Retry-After. Creates are retried only on 429, so a late 5xx cannot create a duplicate. Autotask reports business-rule violations as HTTP 500 with an errors list; those map to invalid_argument and are not retried.

• autotask_get_ticket_attachment and autotask_get_ticket_note_attachment may return file data above the 20,000 character limit, up to maxInlineBase64Bytes.

Run locally

uv sync
uv run autotask-mcp            # listens on 0.0.0.0:8080
curl -s http://127.0.0.1:8080/health
curl -s http://127.0.0.1:8080/mcp \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -H "X-Api-Key: $AUTOTASK_API_USER" -H "X-Api-Secret: $AUTOTASK_API_SECRET" \
  -H "X-Integration-Code: $AUTOTASK_INTEGRATION_CODE" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Environment variables (all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), MCP_TRANSPORT (http or stdio). Unknown variables are ignored. Credentials are never read from the environment.

Docker

docker build -t autotask-mcp .
docker run --rm -p 8080:8080 autotask-mcp

Development

uv sync
uv run pytest -q
uv run ruff check . && uv run ruff format --check .

Code is in src/autotask_mcp/ (one module per area under tools/), tests in tests/. The implementation follows the public Autotask REST API documentation (Autotask online help, "REST API": authentication, zone lookup, entities, query syntax and entity information).

License

Copyright 2026 MSPbots.ai. Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.

Autotask is a trademark of its owner. This project is not affiliated with or endorsed by the owner of Autotask.