A Autotask MCP server, so Claude can work with your Autotask data

Status: no official server yet

Authentication

Autotask uses the REST API v1.0. The server first discovers your zone with GET https://webservices.autotask.net/atservicesrest/v1.0/zoneInformation?user=<api user>, which returns the zone URL to use for every other request.

Each request carries three headers: ApiIntegrationCode, UserName and Secret, belonging to an API-only user.

Honest limits

• You need an API-only user and an integration code in Autotask. The tools can only reach what that user’s security level allows.
• Searches are POST requests to /query endpoints with a filter body, so the server has to translate Claude’s request into Autotask filters. We agree the supported filters in writing.
• Write tools change live PSA data. A read-only first build is an option.

How you’d connect it

The server runs two ways: locally over stdio, started with npx, or remotely over Streamable HTTP at a URL on your own host. The commands below use placeholders; your README has the real package name, URL and variables. NOLU does not run a shared hosted Autotask server.

Claude Code

# remote (Streamable HTTP)
claude mcp add --transport http autotask https://<your-host>/mcp

# local (stdio)
claude mcp add autotask -e AUTOTASK_USERNAME=<value> -e AUTOTASK_SECRET=<value> -e AUTOTASK_INTEGRATION_CODE=<value> -- npx -y <your-server-package>

Claude Desktop

For a remote server, add the URL https://<your-host>/mcp as a custom connector. For a local server, add it to claude_desktop_config.json:

{
  "mcpServers": {
    "autotask": {
      "command": "npx",
      "args": ["-y", "<your-server-package>"],
      "env": {
        "AUTOTASK_USERNAME": "<value>",
        "AUTOTASK_SECRET": "<value>",
        "AUTOTASK_INTEGRATION_CODE": "<value>"
      }
    }
  }
}

Cursor

In .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "autotask": { "url": "https://<your-host>/mcp" }
  }
}

Variable names above are examples. Keep credentials in local config or your host’s secret store, never in the repository.

Who it is for

• Autotask customers (MSPs) who want Claude to work with their own Autotask account, using their own credentials.
• Kaseya itself, if it wants an MCP server built around its API for its customers. That usually means the Standard tier, with OAuth so each user signs in with their own account.

Questions