Skip to main content
Glama
Autotask MCP Server

Autotask MCP Server

by haxos-anon

Autotask MCP Server

Build Status codecov License Node.js

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 39 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 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

Deploy to DO

Deploy to Cloudflare Workers

Related MCP server: Autotask MCP Server

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-technology/autotask-mcp

See Installation for Docker and from-source methods.

Features

  • ๐Ÿ”Œ MCP Protocol Compliance: Full support for MCP resources and tools

  • ๐Ÿ› ๏ธ Comprehensive API Coverage: 39 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

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-technology/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-technology/autotask-mcp:latest",
        "dist/entry.js"
      ]
    }
  }
}

Remote (HTTP Streamable โ€” for server deployments):

docker run -d \
  --name autotask-mcp \
  -p 8080:8080 \
  -e AUTOTASK_USERNAME="your-user@company.com" \
  -e AUTOTASK_SECRET="your-secret" \
  -e AUTOTASK_INTEGRATION_CODE="your-code" \
  --restart unless-stopped \
  ghcr.io/wyre-technology/autotask-mcp:latest

# Verify
curl http://localhost:8080/health

Clients connect to http://host:8080/mcp using MCP Streamable HTTP transport.

Gateway Mode (for MCP Gateway deployments):

When deploying behind an MCP Gateway that injects credentials via HTTP headers:

docker run -d \
  --name autotask-mcp \
  -p 8080:8080 \
  -e AUTH_MODE=gateway \
  --restart unless-stopped \
  ghcr.io/wyre-technology/autotask-mcp:latest

The gateway injects credentials via headers:

  • X-API-Key: Autotask username

  • X-API-Secret: Autotask secret

  • X-Integration-Code: Autotask integration code

See Gateway Mode for details.

Option 3: From Source (Development)

git clone https://github.com/wyre-technology/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)

# 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)
MCP_HTTP_HOST=0.0.0.0        # HTTP transport bind address

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

# 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

Expected Headers:

Header

Description

X-API-Key

Autotask API username (email)

X-API-Secret

Autotask API secret key

X-Integration-Code

Autotask integration code

X-API-URL

(Optional) Custom Autotask API URL

Health Check Response (Gateway Mode):

{
  "status": "ok",
  "transport": "http",
  "authMode": "gateway",
  "timestamp": "2026-02-05T10:00:00.000Z"
}

For detailed migration instructions, see the Migration Guide.

๐Ÿ’ก Pro Tip: Copy the above content to a .env file in your project root.

Autotask API Setup

  1. Create API User: In Autotask, create a dedicated API user with appropriate permissions

  2. Generate Secret: Generate an API secret for the user

  3. Integration Code: Obtain your integration code from Autotask

  4. Permissions: Ensure the API user has read/write access to required entities

For detailed setup instructions, see the Autotask API documentation.

Usage

Command Line

# Start the MCP server (stdio transport, for piping to an MCP client)
node dist/entry.js

# Start with HTTP transport
MCP_TRANSPORT=http node dist/index.js

MCP Client Configuration

See Installation for all setup methods.

API Reference

Resources

Resources provide read-only access to Autotask data:

  • autotask://companies - List all companies

  • autotask://companies/{id} - Get specific company

  • autotask://contacts - List all contacts

  • autotask://contacts/{id} - Get specific contact

  • autotask://tickets - List all tickets

  • autotask://tickets/{id} - Get specific ticket

  • autotask://time-entries - List time entries

Tools

The server provides 39 tools for interacting with Autotask:

Company Operations

  • autotask_search_companies - Search companies with filters

  • autotask_create_company - Create new company

  • autotask_update_company - Update existing company

Contact Operations

  • autotask_search_contacts - Search contacts with filters

  • autotask_create_contact - Create new contact

Ticket Operations

  • autotask_search_tickets - Search tickets with filters

  • autotask_get_ticket_details - Get full ticket details by ID

  • autotask_create_ticket - Create new ticket

Time Entry Operations

  • autotask_create_time_entry - Log time entry

  • autotask_search_time_entries - Search time entries with filters (resource, ticket, project, date range)

Billing Items (Approve and Post Workflow)

  • autotask_search_billing_items - Search approved and posted billing items

  • autotask_get_billing_item - Get specific billing item by ID

  • autotask_search_billing_item_approval_levels - Search multi-level approval records for time entries

Project Operations

  • autotask_search_projects - Search projects with filters

  • autotask_create_project - Create new project

Resource Operations

  • autotask_search_resources - Search resources (technicians/users)

Note Operations

  • autotask_get_ticket_note / autotask_search_ticket_notes / autotask_create_ticket_note

  • autotask_get_project_note / autotask_search_project_notes / autotask_create_project_note

  • autotask_get_company_note / autotask_search_company_notes / autotask_create_company_note

Attachment Operations

  • autotask_get_ticket_attachment - Get ticket attachment

  • autotask_search_ticket_attachments - Search ticket attachments

Financial Operations

  • autotask_get_expense_report / autotask_search_expense_reports / autotask_create_expense_report

  • autotask_get_quote / autotask_search_quotes / autotask_create_quote

  • autotask_search_invoices - Search invoices

  • autotask_search_contracts - Search contracts

Configuration Items

  • autotask_search_configuration_items - Search configuration items (assets)

Task Operations

  • autotask_search_tasks - Search project tasks

  • autotask_create_task - Create project task

Utility Operations

  • autotask_test_connection - Test API connectivity

Example Tool Usage

// Search for companies
{
  "name": "autotask_search_companies",
  "arguments": {
    "searchTerm": "Acme Corp",
    "isActive": true,
    "pageSize": 10
  }
}

// Create a new ticket
{
  "name": "autotask_create_ticket",
  "arguments": {
    "companyID": 12345,
    "title": "Server maintenance request",
    "description": "Need to perform monthly server maintenance",
    "priority": 2,
    "status": 1
  }
}

ID-to-Name Mapping

The Autotask MCP server includes intelligent ID-to-name mapping that automatically resolves company and resource IDs to human-readable names, making API responses much more useful for AI assistants and human users.

Automatic Enhancement

All search and detail tools automatically include an _enhanced field with resolved names:

{
  "id": 12345,
  "title": "Sample Ticket",
  "companyID": 678,
  "assignedResourceID": 90,
  "_enhanced": {
    "companyName": "Acme Corporation",
    "assignedResourceName": "John Smith"
  }
}

How It Works

ID-to-name mapping is applied automatically to all search and detail tool results. No additional tools are needed โ€” the _enhanced field is added transparently to every response that contains company or resource IDs.

Performance Features

  • Smart Caching: Names are cached for 30 minutes to reduce API calls

  • Bulk Operations: Efficient batch lookups for multiple IDs

  • Graceful Fallback: Returns "Unknown Company (123)" if lookup fails

  • Parallel Processing: Multiple mappings resolved simultaneously

Testing Mapping

Test the mapping functionality:

npm run test:mapping

For detailed mapping documentation, see docs/mapping.md.

HTTP Transport

The server supports the MCP Streamable HTTP transport for remote deployments (e.g., Docker, cloud hosting). Set MCP_TRANSPORT=http to enable it.

# Start with HTTP transport
MCP_TRANSPORT=http MCP_HTTP_PORT=8080 node dist/index.js

The HTTP transport exposes:

  • POST /mcp โ€” MCP Streamable HTTP endpoint

  • GET /health โ€” Health check (returns {"status":"ok"})

Clients must send requests to /mcp with Accept: application/json, text/event-stream headers per the MCP Streamable HTTP specification.

Docker Deployment

The Docker image uses HTTP transport by default (port 8080) with a built-in health check.

Using Pre-built Image from GitHub Container Registry

The Docker image defaults to HTTP transport on port 8080 โ€” suitable for remote/server deployments where clients connect over the network.

# Pull the latest image
docker pull ghcr.io/wyre-technology/autotask-mcp:latest

# Run container with HTTP transport (default)
docker run -d \
  --name autotask-mcp \
  -p 8080:8080 \
  -e AUTOTASK_USERNAME="your-api-user@example.com" \
  -e AUTOTASK_SECRET="your-secret-key" \
  -e AUTOTASK_INTEGRATION_CODE="your-integration-code" \
  --restart unless-stopped \
  ghcr.io/wyre-technology/autotask-mcp:latest

# Verify it's running
curl http://localhost:8080/health

For stdio usage with Claude Desktop, see Installation Option 2.

Quick Start (From Source)

# Clone repository
git clone https://github.com/wyre-technology/autotask-mcp.git
cd autotask-mcp

# Create environment file
cp .env.example .env
# Edit .env with your credentials

# Start with docker-compose
docker compose up -d

Production Deployment

# Build production image locally
docker build -t autotask-mcp:latest .

# Run container
docker run -d \
  --name autotask-mcp \
  --env-file .env \
  --restart unless-stopped \
  autotask-mcp:latest

Development Mode

# Start development environment with hot reload
docker compose --profile dev up autotask-mcp-dev

Development

Setup

git clone https://github.com/wyre-technology/autotask-mcp.git
cd autotask-mcp
npm install

Available Scripts

npm run dev          # Start development server with hot reload
npm run build        # Build for production
npm run test         # Run test suite
npm run test:watch   # Run tests in watch mode
npm run test:coverage # Run tests with coverage
npm run lint         # Run ESLint
npm run lint:fix     # Fix ESLint issues

Project Structure

autotask-mcp/
โ”œโ”€โ”€ src/
โ”‚   โ”œโ”€โ”€ handlers/           # MCP request handlers
โ”‚   โ”œโ”€โ”€ mcp/               # MCP server implementation
โ”‚   โ”œโ”€โ”€ services/          # Autotask service layer
โ”‚   โ”œโ”€โ”€ types/             # TypeScript type definitions
โ”‚   โ”œโ”€โ”€ utils/             # Utility functions (config, logger, cache)
โ”‚   โ”œโ”€โ”€ entry.ts           # Entry point (stdout guard + .env loader)
โ”‚   โ””โ”€โ”€ index.ts           # Server bootstrap (config, logger, server init)
โ”œโ”€โ”€ tests/                 # Test files
โ”œโ”€โ”€ scripts/               # Build and packaging scripts
โ”‚   โ””โ”€โ”€ pack-mcpb.js       # MCPB bundle creation
โ”œโ”€โ”€ manifest.json          # MCPB manifest for desktop distribution
โ”œโ”€โ”€ Dockerfile             # Container definition (HTTP transport)
โ”œโ”€โ”€ docker-compose.yml     # Multi-service orchestration
โ””โ”€โ”€ package.json          # Project configuration

Testing

Running Tests

# Run all tests
npm test

# Run with coverage
npm run test:coverage

# Run in watch mode
npm run test:watch

# Run specific test file
npm test -- tests/autotask-service.test.ts

Test Categories

  • Unit Tests: Service layer and utility functions

  • Integration Tests: MCP protocol compliance

  • API Tests: Autotask API integration (requires credentials)

Coverage Requirements

  • Minimum 80% coverage for all metrics

  • 100% coverage for critical paths (authentication, data handling)

Configuration Reference

Environment Variables

Variable

Required

Default

Description

AUTOTASK_USERNAME

โœ…

-

Autotask API username (email)

AUTOTASK_SECRET

โœ…

-

Autotask API secret key

AUTOTASK_INTEGRATION_CODE

โœ…

-

Autotask integration code

AUTOTASK_API_URL

โŒ

Auto-detected

Autotask API endpoint URL

MCP_SERVER_NAME

โŒ

autotask-mcp

MCP server name

MCP_TRANSPORT

โŒ

stdio

Transport type (stdio or http)

MCP_HTTP_PORT

โŒ

8080

HTTP transport port

MCP_HTTP_HOST

โŒ

0.0.0.0

HTTP transport bind address

LOG_LEVEL

โŒ

info

Logging level

LOG_FORMAT

โŒ

simple

Log output format

NODE_ENV

โŒ

development

Node.js environment

Logging Levels

  • error: Only error messages

  • warn: Warnings and errors

  • info: General information, warnings, and errors

  • debug: Detailed debugging information

Log Formats

  • simple: Human-readable console output

  • json: Structured JSON output (recommended for production)

Troubleshooting

Common Issues

Authentication Errors

Error: Missing required Autotask credentials

Solution: Ensure all required environment variables are set correctly.

Connection Timeouts

Error: Connection to Autotask API failed

Solutions:

  • Check network connectivity

  • Verify API endpoint URL

  • Confirm API user has proper permissions

Permission Denied

Error: User does not have permission to access this resource

Solution: Review Autotask API user permissions and security level settings.

Debug Mode

Enable debug logging for detailed troubleshooting:

LOG_LEVEL=debug npm start

Health Checks

Test server connectivity:

# Run test suite
npm run test

# For HTTP transport, check the health endpoint
curl http://localhost:8080/health
# Returns: {"status":"ok"}

# Test API connection with debug logging
LOG_LEVEL=debug npm start

Autotask API Rate Limits

Problem: 429 Too Many Requests or "thread limit exceeded" errors when Claude queries aggressively

Autotask enforces 3 concurrent threads per endpoint per API tracking identifier. When an LLM issues multiple tool calls simultaneously (e.g., searching tickets, companies, and contacts at once), requests can pile up and hit this limit.

Built-in mitigation: The underlying autotask-node SDK automatically queues excess requests rather than failing immediately. Requests wait for a slot to free up, so you generally won't see 429 errors โ€” but you may notice slower responses under heavy load.

Critical for team/multi-user deployments: If multiple users or the MCP Gateway share the same API credentials, they compete for the same 3-thread budget. This can cause noticeable slowdowns and, in severe cases, queued requests that time out.

Solution โ€” one API key per team: Create a dedicated Autotask API user per team or integration. Each user has an independent integrationCode with its own thread budget:

  1. Admin > Resources (Users) > Resources/Users โ†’ Add Resource

  2. Set Security Level to API User

  3. Note the username, secret, and integration code

  4. Set AUTOTASK_USERNAME, AUTOTASK_SECRET, and AUTOTASK_INTEGRATION_CODE per team

Support Team  โ†’ AUTOTASK_INTEGRATION_CODE=SUPPORT_TEAM_CODE  (3 threads)
Projects Team โ†’ AUTOTASK_INTEGRATION_CODE=PROJECTS_TEAM_CODE (3 threads, independent)

Additionally, Autotask limits 10,000 total requests per hour across all integrations hitting your tenant. If you hit this limit, all integrations will start receiving 429s โ€” another reason to use targeted queries with appropriate filters.

MCP Client Issues

Problem: MCP server not appearing in Claude Desktop Solutions:

  1. Check configuration file syntax (valid JSON)

  2. Verify file path in the configuration

  3. Ensure environment variables are set correctly

  4. Restart Claude Desktop completely

Problem: "Invalid JSON-RPC message: [dotenv@...] injecting env" / Server disconnected Cause: The autotask-node library calls dotenv.config() at module load time. dotenv v17+ writes status messages via console.log to stdout, which corrupts the MCP stdio JSON-RPC channel. Solution: Ensure you're using dist/entry.js (not dist/index.js) as the entry point. The entry wrapper redirects console.log to stderr before any libraries load.

Problem: Slow responses Solutions:

  1. Check network connectivity to Autotask API

  2. Enable debug logging (LOG_LEVEL=debug) to identify bottlenecks

  3. The server caches company/resource names for 30 minutes automatically

Security Best Practices

  • Store credentials in environment variables, not directly in config files

  • Limit Autotask API user permissions to the minimum required

  • Rotate API credentials regularly

  • For Docker deployments, use secrets management rather than plain environment variables

Contributing

  1. Fork the repository

  2. Create a feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

Development Guidelines

  • Follow TypeScript best practices

  • Maintain test coverage above 80%

  • Use conventional commit messages

  • Update documentation for API changes

  • Add tests for new features

License

This project is licensed under the Apache License 2.0. See the LICENSE file for details.

Contributor License Agreement

By submitting a pull request, you agree to the terms of our Contributor License Agreement. This ensures that contributions can be properly licensed and that you have the right to submit the code.

Contributors

Avatar

Name

Contributions

@asachs01

Maintainer

@Baphomet480

CLI bin fix

Support

Acknowledgments


Built by WYRE Technology โ€” part of the MSP Claude Plugins ecosystem

Available Tools

90 tools
autotask_create_companyB

Create a new company in Autotask

Inputs: companyName (required), companyType (required), phone, address1, +5 more.

autotask_create_company_noteB

Create a new note for a company

Inputs: companyId (required), description (required), title, actionType.

autotask_create_contactB

Create a new contact in Autotask

Inputs: companyID (required), firstName (required), lastName (required), emailAddress, +2 more.

autotask_create_expense_itemB

Create an expense item on an existing expense report

Inputs: expenseReportId (required), description (required), expenseDate (required), expenseCategory (required), +6 more.

autotask_create_expense_reportC

Create a new expense report

Inputs: name (required), submitterId (required), weekEndingDate (required), description.

autotask_create_opportunityB

Create a new sales opportunity in Autotask

Inputs: title (required), companyId (required), ownerResourceId (required), status (required), +11 more.

autotask_create_phaseC

Create a new phase in an Autotask project

Inputs: projectID (required), title (required), description, startDate, +2 more.

autotask_create_projectC

Create a new project in Autotask

Inputs: companyID (required), projectName (required), status (required), projectType (required), +5 more.

autotask_create_project_noteC

Create a new note for a project

Inputs: projectId (required), description (required), title, noteType, +2 more.

autotask_create_quoteB

Create a new quote

Inputs: companyId (required), name, description, contactId, +3 more.

autotask_create_quote_itemA

Create a line item on a quote. Set exactly ONE item reference (serviceID, productID, or serviceBundleID). Required: quoteId, quantity. Defaults: unitDiscount=0, lineDiscount=0, percentageDiscount=0, isOptional=false.

Inputs: quoteId (required), quantity (required), name, description, +11 more.

autotask_create_service_callC

Create a new service call in Autotask. Service calls are used to schedule and plan work on tickets.

Inputs: description (required), startDateTime (required), endDateTime (required), status, +3 more.

autotask_create_service_call_ticketB

Link a ticket to a service call. This associates the ticket with the service call for scheduling purposes.

Inputs: serviceCallID (required), ticketID (required).

autotask_create_service_call_ticket_resourceB

Assign a resource (technician) to a service call ticket.

Inputs: serviceCallTicketID (required), resourceID (required), roleID.

autotask_create_taskC

Create a new task in Autotask

Inputs: projectID (required), title (required), status (required), description, +5 more.

autotask_create_ticketB

Create a new ticket in Autotask

Inputs: companyID (required), title (required), description (required), status, +17 more.

autotask_create_ticket_attachmentA

Upload a file attachment to an existing ticket. The file content must be passed as a base64-encoded string in the data field (MCP is JSON-RPC, so binary bytes must be base64-encoded). Autotask enforces a 3 MB hard limit on ticket attachments; this tool validates the decoded size before calling the API and returns a clear error if the limit is exceeded. Example: { ticketId: 12345, title: "screenshot.png", data: "iVBORw0KGgoAAAANSUhEUgAA..." }

Inputs: ticketId (required), title (required), data (required), fullPath, +2 more.

autotask_create_ticket_chargeA

Create a charge (material, cost, or expense) on a ticket. Used to bill clients for parts, travel, or other non-labor costs.

Inputs: ticketID (required), name (required), chargeType (required), description, +8 more.

autotask_create_ticket_checklist_itemB

Add a new checklist item to a ticket.

Inputs: ticketId (required), itemName (required), position, isCompleted.

autotask_create_ticket_noteB

Create a new note for a ticket

Inputs: ticketId (required), description (required), title, noteType, +1 more.

autotask_create_time_entryA

Create a time entry in Autotask. Can be tied to a ticket, task, or project, OR created as "Regular Time" (no parent) for meetings, admin work, etc. For Regular Time, specify a category like "Internal Meeting", "Office Management", "Training", etc.

Inputs: dateWorked (required), hoursWorked (required), summaryNotes (required), ticketID, +8 more.

autotask_delete_quote_itemB

Delete a quote item (line item) from a quote

Inputs: quoteId (required), quoteItemId (required).

autotask_delete_service_callB

Delete a service call by ID

Inputs: serviceCallId (required).

autotask_delete_service_call_ticketB

Remove a ticket association from a service call by the service call ticket record ID

Inputs: serviceCallTicketId (required).

autotask_delete_service_call_ticket_resourceB

Remove a resource assignment from a service call ticket by the resource record ID

Inputs: serviceCallTicketResourceId (required).

autotask_delete_ticket_chargeA

Delete a ticket charge by ID. Requires both the parent ticket ID and charge ID.

Inputs: ticketId (required), chargeId (required).

autotask_delete_ticket_checklist_itemB

Delete a checklist item from a ticket.

Inputs: ticketId (required), itemId (required).

autotask_execute_toolB

Execute any Autotask tool by name. Use after discovering tools via autotask_list_category_tools.

Inputs: toolName (required), arguments.

autotask_get_billing_itemB

Get detailed information for a specific billing item by ID

Inputs: billingItemId (required).

autotask_get_company_noteB

Get a specific company note by company ID and note ID

Inputs: companyId (required), noteId (required).

autotask_get_company_site_configurationA

Get the site configuration record(s) for a company in Autotask. Site configurations contain tenant-defined fields used to track per-company configuration data. Call this first to discover which fields are available before calling autotask_update_company_site_configuration.

Inputs: companyId (required).

autotask_get_expense_reportA

Get a specific expense report by ID

Inputs: reportId (required).

autotask_get_field_infoA

Get field definitions for an Autotask entity type, including picklist values. Useful for discovering valid values for any picklist field.

Inputs: entityType (required), fieldName.

autotask_get_invoice_detailsA

Get a single Autotask invoice with its nested line items (billing items posted to the invoice). Use for finance workflows that need to see exactly what an invoice contains.

Inputs: invoiceId (required).

autotask_get_opportunityA

Get a specific opportunity by ID

Inputs: opportunityId (required).

autotask_get_productA

Get a specific product by ID

Inputs: productId (required).

autotask_get_project_noteA

Get a specific project note by project ID and note ID

Inputs: projectId (required), noteId (required).

autotask_get_quoteB

Get a specific quote by ID

Inputs: quoteId (required).

autotask_get_quote_itemA

Get a specific quote item by ID

Inputs: quoteItemId (required).

autotask_get_serviceA

Get a specific service by ID

Inputs: serviceId (required).

autotask_get_service_bundleB

Get a specific service bundle by ID

Inputs: serviceBundleId (required).

autotask_get_service_callB

Get a specific service call by ID

Inputs: serviceCallId (required).

autotask_get_ticket_attachmentA

Get a specific ticket attachment by ticket ID and attachment ID

Inputs: ticketId (required), attachmentId (required), includeData.

autotask_get_ticket_chargeB

Get a specific ticket charge by ID

Inputs: chargeId (required).

autotask_get_ticket_detailsA

Get detailed information for a specific ticket by ID. Use this for full ticket data when needed.

Inputs: ticketID (required), fullDetails.

autotask_get_ticket_noteA

Get a specific ticket note by ticket ID and note ID

Inputs: ticketId (required), noteId (required).

autotask_list_categoriesA

List available tool categories. Use this to discover what types of Autotask operations are available before loading specific tools.

Inputs: no named parameters.

autotask_list_category_toolsA

List tools in a specific category with full schemas. Use after autotask_list_categories to see available tools and their parameters.

Inputs: category (required).

autotask_list_phasesB

List phases for a project in Autotask

Inputs: projectID (required), pageSize.

autotask_list_queuesA

List all available ticket queues in Autotask. Use this to find queue IDs for filtering tickets by queue.

Inputs: no named parameters.

autotask_list_ticket_prioritiesA

List all available ticket priorities in Autotask. Use this to find priority values for filtering or creating tickets.

Inputs: no named parameters.

autotask_list_ticket_statusesA

List all available ticket statuses in Autotask. Use this to find status values for filtering or creating tickets.

Inputs: no named parameters.

autotask_routerA

Intelligent tool router - describe what you want to do and get the right tool suggestion with pre-filled parameters. Use this when unsure which tool to call.

Inputs: intent (required).

autotask_search_billing_item_approval_levelsB

Search for billing item approval levels. These describe multi-level approval records for Autotask time entries, enabling visibility into tiered approval workflows.

Inputs: timeEntryId, approvalResourceId, approvalLevel, approvedAfter, +3 more.

autotask_search_billing_itemsA

Search for billing items in Autotask. Billing items represent approved and posted billable items from the "Approve and Post" workflow. Returns 25 results per page by default.

Inputs: companyId, ticketId, projectId, contractId, +8 more.

autotask_search_companiesB

Search for companies in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Inputs: searchTerm, isActive, page, pageSize.

autotask_search_company_notesC

Search for notes on a specific company

Inputs: companyId (required), pageSize.

autotask_search_configuration_itemsC

Search for configuration items in Autotask with optional filters

Inputs: searchTerm, companyID, isActive, productID, +1 more.

autotask_search_contactsA

Search for contacts in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Inputs: searchTerm, companyID, isActive, page, +1 more.

autotask_search_contractsC

Search for contracts in Autotask with optional filters

Inputs: searchTerm, companyID, status, pageSize.

autotask_search_expense_reportsC

Search for expense reports with optional filters

Inputs: submitterId, status, pageSize.

autotask_search_invoicesC

Search for invoices in Autotask with optional filters

Inputs: companyID, invoiceNumber, isVoided, pageSize.

autotask_search_opportunitiesC

Search for opportunities with optional filters

Inputs: companyId, searchTerm, status, pageSize.

autotask_search_productsB

Search for products with optional filters

Inputs: searchTerm, isActive, pageSize.

autotask_search_project_notesC

Search for notes on a specific project

Inputs: projectId (required), pageSize.

autotask_search_projectsB

Search for projects in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Inputs: searchTerm, companyID, status, projectLeadResourceID, +2 more.

autotask_search_quote_itemsA

Search for quote items, typically filtered by quote ID

Inputs: quoteId, searchTerm, pageSize.

autotask_search_quotesC

Search for quotes with optional filters

Inputs: companyId, contactId, opportunityId, searchTerm, +1 more.

autotask_search_resourcesC

Search for resources (users) in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Inputs: searchTerm, isActive, resourceType, page, +1 more.

autotask_search_service_bundlesC

Search for service bundles with optional filters

Inputs: searchTerm, isActive, pageSize.

autotask_search_service_callsB

Search for service calls in Autotask. Filter by company, status, or date range.

Inputs: companyId, status, startAfter, startBefore, +1 more.

autotask_search_service_call_ticket_resourcesB

Search for resource (technician) assignments on service call tickets.

Inputs: serviceCallTicketId, resourceId, pageSize.

autotask_search_service_call_ticketsA

Search for ticket associations on service calls. Use this to find which tickets are linked to a service call, or which service calls contain a specific ticket.

Inputs: serviceCallId, ticketId, pageSize.

autotask_search_servicesC

Search for services with optional filters

Inputs: searchTerm, isActive, pageSize.

autotask_search_tasksB

Search for tasks in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Inputs: searchTerm, projectID, status, assignedResourceID, +2 more.

autotask_search_ticket_attachmentsB

Search for attachments on a specific ticket

Inputs: ticketId (required), pageSize.

autotask_search_ticket_chargesA

Search for charges on a specific ticket. Charges represent materials, costs, or expenses billed against a ticket. Providing ticketId is strongly recommended โ€” unfiltered queries are expensive and capped at 10 results.

Inputs: ticketId, pageSize.

autotask_search_ticket_checklist_itemsA

List all checklist items on a ticket, including their completion status. Checklist items are a sub-resource of a ticket and cannot be queried without a ticket ID.

Inputs: ticketId (required).

autotask_search_ticket_notesB

Search for notes on a specific ticket

Inputs: ticketId (required), pageSize.

autotask_search_ticketsA

Search for tickets in Autotask. Returns 25 results per page by default. Use page parameter for more results. Use get_ticket_details for full data on a specific ticket.

Inputs: searchTerm, companyID, status, assignedResourceID, +6 more.

autotask_search_time_entriesA

Search for time entries in Autotask. Returns 25 results per page by default. Time entries can be filtered by resource, ticket, project, task, date range, or approval status. Use approvalStatus="unapproved" to find entries not yet posted.

Inputs: resourceId, ticketId, projectId, taskId, +6 more.

autotask_test_connectionB

Test the connection to Autotask API

Inputs: no named parameters.

autotask_update_companyC

Update an existing company in Autotask

Inputs: id (required), companyName, phone, address1, +4 more.

autotask_update_company_site_configurationA

Update fields on a company site configuration record. The set of available fields is tenant-defined, so callers should first call autotask_get_company_site_configuration to discover the available field names and current values for the company. Pass the site configuration record id (not the company id) along with an updates object containing the fields to change.

Inputs: id (required), updates (required).

autotask_update_projectA

Update an existing project in Autotask. Only the fields you provide will be updated. Common use case: set status=5 to mark a project Complete.

Inputs: projectId (required), projectName, description, status, +8 more.

autotask_update_quote_itemA

Update an existing quote item (quantity, price, etc.)

Inputs: quoteItemId (required), quantity, unitPrice, unitDiscount, +4 more.

autotask_update_service_callA

Update an existing service call. Use this to change status, times, or description. To complete/close a service call, set complete: true or update the status.

Inputs: serviceCallId (required), description, status, startDateTime, +2 more.

autotask_update_ticketB

Update an existing ticket in Autotask. Only fields provided will be changed.

Inputs: ticketId (required), title, description, status, +5 more.

autotask_update_ticket_chargeA

Update an existing ticket charge. Only fields provided will be changed.

Inputs: chargeId (required), name, description, unitQuantity, +4 more.

autotask_update_ticket_checklist_itemB

Update a checklist item on a ticket โ€” edit text, mark complete/incomplete, or change position.

Inputs: ticketId (required), itemId (required), itemName, isCompleted, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    B3.4/5.0

    Scored across 90 tools

    Disambiguation4/5

    Most tools have distinct purposes (create vs. search vs. get vs. update), but there is some overlap between 'get' and 'search' tools (e.g., get_quote vs. search_quotes) and among delete tools for different entities. The descriptions clarify usage, though the sheer number could cause confusion.

    Naming Consistency5/5

    All tools follow a consistent 'autotask_verb_noun' pattern (e.g., autotask_create_ticket, autotask_search_companies, autotask_get_quote). Verbs are standard CRUD terms plus search/list/get/execute/router. No mixing of conventions.

    Tool Count3/5

    90 tools is very high for a single server. While Autotask is a large domain covering many entities, this count feels excessive and likely includes many variants (e.g., three service call delete tools). It would benefit from consolidation or categorization.

    Completeness4/5

    The tool surface covers most major Autotask entities (companies, contacts, tickets, projects, quotes, expenses, service calls) with create, read, update, delete and search. Minor gaps: no delete for companies, contacts, or projects; no update for contacts. Overall well-rounded for the domain.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      C
      maintenance
      Provides AI assistants with direct access to Autotask PSA for MSP operations. Enables natural language interaction for ticket management, time logging, company lookups, project tracking, and billing review through 39 comprehensive tools.
      100
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Autotask PSA through natural language, providing tools for ticket triage, time logging, company lookups, project management, and more.
      Apache 2.0