Autotask

Autotask MCP Server

Give your AI assistant direct access to Autotask. Search tickets, create time entries, look up companies, manage projects — all through natural language. No more copy-pasting between browser tabs and chat windows.

This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Autotask PSA environment. Your AI assistant gets 101 tools covering the operations MSP teams use daily: ticket triage, time logging, company lookups, project management, billing review, and more.

If you run an MSP on Autotask and you're tired of the context-switching tax, this is for you.

Part of the [MSP Claude Plugins](https://github.com/WYRE-AI/msp-claude-plugins) ecosystem — a growing suite of AI integrations for the MSP stack including Datto RMM, IT Glue, HaloPSA, ConnectWise Automate, NinjaOne, Huntress, and more. Built by MSPs, for MSPs.

One-Click Deployment

Note — no GitHub Packages token required. Unlike most WYRE MCP servers,

autotask-mcp does not depend on a private @wyre-ai/* package on

GitHub Packages. Its only WYRE dependency is the autotask-node SDK, declared

as a git dependency on the public WYRE-AI/autotask-node repo, which

npm install resolves anonymously. The DigitalOcean one-click deploy therefore

works without any NODE_AUTH_TOKEN/GITHUB_TOKEN build variable.

Quick Start

Claude Desktop — download, open, done:

1. Download autotask-mcp.mcpb from the latest release
2. Open the file (double-click or drag into Claude Desktop)
3. Enter your Autotask credentials when prompted (Username, Secret, Integration Code)

No terminal, no JSON editing, no Node.js install required.

Claude Code (CLI):

claude mcp add autotask-mcp \

-e AUTOTASK_USERNAME=your-user@company.com \ -e AUTOTASK_SECRET=your-secret \ -e AUTOTASK_INTEGRATION_CODE=your-code \ -- npx -y github:WYRE-AI/autotask-mcp

See Installation for Docker and from-source methods.

Features

• 🔌 MCP Protocol Compliance: Full support for MCP resources and tools
• 🎴 Interactive Ticket Card (MCP Apps): autotask_get_ticket_details renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Add note" round-trip; neutral theme by default, brandable via MCP_BRAND_* env vars. In every host, the text the assistant reads carries the full ticket: description, contact, linked configuration item, custom fields (UDFs), recent notes and the complete record as JSON
• 🛠️ Comprehensive API Coverage: 101 tools spanning companies, contacts, tickets, projects, billing items, time entries, notes, attachments, and more
• 🔍 Advanced Search: Powerful search capabilities with filters across all entities
• 📝 CRUD Operations: Create, read, update operations for core Autotask entities
• 🔄 ID-to-Name Mapping: Automatic resolution of company and resource IDs to human-readable names
• ⚡ Intelligent Caching: Smart caching system for improved performance and reduced API calls
• 🔒 Secure Authentication: Enterprise-grade API security with Autotask credentials
• 🌐 Dual Transport: Supports both stdio (local) and HTTP Streamable (remote/Docker) transports
• 📦 MCPB Packaging: One-click installation via MCP Bundle for desktop clients
• 🐳 Docker Ready: Containerized deployment with HTTP transport and health checks
• 📊 Structured Logging: Comprehensive logging with configurable levels and formats
• 🧪 Test Coverage: Comprehensive test suite with 80%+ coverage

Table of Contents

• Installation
• Configuration
• Gateway Mode
• Usage
• API Reference
• ID-to-Name Mapping
• HTTP Transport
• Docker Deployment
• Migration Guide
• Development
• Testing
• Troubleshooting
• Contributing
• Contributors
• License

Installation

Option 1: MCPB Bundle (Claude Desktop)

The simplest method — no terminal, no JSON editing, no Node.js install required.

1. Download autotask-mcp.mcpb from the latest release
2. Open the file (double-click or drag into Claude Desktop)
3. Enter your Autotask credentials when prompted (Username, Secret, Integration Code)

For Claude Code (CLI), one command:

claude mcp add autotask-mcp \

-e AUTOTASK_USERNAME=your-user@company.com \ -e AUTOTASK_SECRET=your-secret \ -e AUTOTASK_INTEGRATION_CODE=your-code \ -- npx -y github:WYRE-AI/autotask-mcp

Option 2: Docker

Local (stdio — for Claude Desktop or Claude Code):

{

"mcpServers": { "autotask": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "MCP_TRANSPORT=stdio", "-e", "AUTOTASK_USERNAME=your-user@company.com", "-e", "AUTOTASK_SECRET=your-secret", "-e", "AUTOTASK_INTEGRATION_CODE=your-code", "--entrypoint", "node", "ghcr.io/wyre-ai/autotask-mcp:latest", "dist/entry.js" ] } } }

Remote (HTTP Streamable — for server deployments):

docker run -d \

--name autotask-mcp \ -p 127.0.0.1:8080:8080 \ -e CONDUIT_S2S_SECRET="your-real-s2s-secret" \ -e AUTOTASK_USERNAME="your-user@company.com" \ -e AUTOTASK_SECRET="your-secret" \ -e AUTOTASK_INTEGRATION_CODE="your-code" \ --restart unless-stopped \ ghcr.io/wyre-ai/autotask-mcp:latest

Verify (health does not require X-Gateway-S2S)

curl http://127.0.0.1:8080/health

The HTTP server refuses to start when CONDUIT_S2S_SECRET is empty or a known placeholder. Clients connect to http://127.0.0.1:8080/mcp using MCP Streamable HTTP transport and must send X-Gateway-S2S. See X-Gateway-S2S signing.

Gateway Mode (for MCP Gateway deployments):

When deploying behind an MCP Gateway that injects credentials via HTTP headers. This container has no static Autotask credentials:

docker run -d \

--name autotask-mcp \ -p 127.0.0.1:8080:8080 \ -e CONDUIT_S2S_SECRET="your-real-s2s-secret" \ -e AUTH_MODE=gateway \ --restart unless-stopped \ ghcr.io/wyre-ai/autotask-mcp:latest

The gateway injects credentials via headers:

• X-Gateway-S2S: service-to-service proof (required on /mcp)
• X-API-Key: Autotask username
• X-API-Secret: Autotask secret
• X-Integration-Code: Autotask integration code
• X-Impersonation-Resource-Id: (optional) Autotask resource ID to act on behalf of

A /mcp request missing any of the three Autotask headers returns 401 and does not fall back to AUTOTASK_* in the environment. See Gateway Mode for details.

Option 3: From Source (Development)

git clone https://github.com/WYRE-AI/autotask-mcp.git

cd autotask-mcp npm ci && npm run build

Then point your MCP client at dist/entry.js:

{

"mcpServers": { "autotask": { "command": "node", "args": ["/path/to/autotask-mcp/dist/entry.js"], "env": { "AUTOTASK_USERNAME": "your-user@company.com", "AUTOTASK_SECRET": "your-secret", "AUTOTASK_INTEGRATION_CODE": "your-code" } } } }

Prerequisites

• Valid Autotask API credentials (API user email, secret, integration code)
• MCP-compatible client (Claude Desktop, Claude Code, etc.)
• Docker (for Option 2) or Node.js 18+ (for Option 3)

Configuration

Environment Variables

Create a .env file with your configuration:

# Required Autotask API credentials (Local Mode)

AUTOTASK_USERNAME=your-api-user@example.com AUTOTASK_SECRET=your-secret-key AUTOTASK_INTEGRATION_CODE=your-integration-code

Optional configuration

AUTOTASK_API_URL is auto-detected from AUTOTASK_USERNAME via Autotask's

unauthenticated zoneInformation endpoint on first connect. Only set this

explicitly to override auto-detection (e.g. for an on-prem proxy).

AUTOTASK_API_URL=https://webservices2.autotask.net/atservicesrest/

MCP_SERVER_NAME=autotask-mcp

Authentication mode

AUTH_MODE=env # env (local), gateway (hosted)

Required to start HTTP. Empty and known placeholders are rejected.

Never commit a real value. stdio does not use this.

CONDUIT_S2S_SECRET=

Local HTTP only. Exactly "1" skips X-Gateway-S2S and forces 127.0.0.1.

MCP_ALLOW_INSECURE_DEV=1

Transport (stdio for local/desktop, http for remote/Docker)

MCP_TRANSPORT=stdio # stdio, http MCP_HTTP_PORT=8080 # HTTP transport port (only used when MCP_TRANSPORT=http)

Honored when CONDUIT_S2S_SECRET is set. Without a usable secret the bind is 127.0.0.1.

MCP_HTTP_HOST=0.0.0.0 # HTTP transport bind address

Logging

LOG_LEVEL=info # error, warn, info, debug LOG_FORMAT=simple # simple, json

Search-result name enrichment

Max concurrent Autotask API calls used to resolve company/resource names on

search results. Kept low to stay under Autotask's per-integration

concurrent-thread limit (raising it risks HTTP 429 "thread threshold").

AUTOTASK_ENHANCE_CONCURRENCY=3

Max Autotask REST calls in flight per tenant. Further calls queue instead of

tripping the concurrent-thread limit (HTTP 429 "thread threshold").

AUTOTASK_MAX_INFLIGHT=3

Environment

NODE_ENV=production

Gateway Mode

When deployed behind an MCP Gateway (e.g., mcp.wyre.ai), the server operates in gateway mode where credentials are injected via HTTP headers on each request.

Enable Gateway Mode:

AUTH_MODE=gateway

MCP_TRANSPORT=http CONDUIT_S2S_SECRET=

Every /mcp request must include a valid X-Gateway-S2S header and the three Autotask credential headers. A request missing any credential header returns 401. The server does not fall back to AUTOTASK_USERNAME, AUTOTASK_SECRET, or AUTOTASK_INTEGRATION_CODE in the process environment.

Expected Headers:

| X-Impersonation-Resource-Id | (Optional) Autotask resource ID