Autotask MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Autotask MCP Server Show me open high-priority tickets for Acme Corp."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 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
Note โ no GitHub Packages token required. Unlike most WYRE MCP servers,
autotask-mcpdoes not depend on a private@wyre-technology/*package on GitHub Packages. Its only WYRE dependency is theautotask-nodeSDK, declared as a git dependency on the publicwyre-technology/autotask-noderepo, whichnpm installresolves anonymously. The DigitalOcean one-click deploy therefore works without anyNODE_AUTH_TOKEN/GITHUB_TOKENbuild variable.
Related MCP server: Autotask MCP Server
Quick Start
Claude Desktop โ download, open, done:
Download
autotask-mcp.mcpbfrom the latest releaseOpen the file (double-click or drag into Claude Desktop)
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-mcpSee 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.
Download
autotask-mcp.mcpbfrom the latest releaseOpen the file (double-click or drag into Claude Desktop)
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-mcpOption 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/healthClients 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:latestThe gateway injects credentials via headers:
X-API-Key: Autotask usernameX-API-Secret: Autotask secretX-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 buildThen 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
# 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
# Environment
NODE_ENV=productionGateway 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=httpExpected Headers:
Header | Description |
| Autotask API username (email) |
| Autotask API secret key |
| Autotask integration code |
| (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
Create API User: In Autotask, create a dedicated API user with appropriate permissions
Generate Secret: Generate an API secret for the user
Integration Code: Obtain your integration code from Autotask
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.jsMCP Client Configuration
See Installation for all setup methods.
API Reference
Resources
Resources provide read-only access to Autotask data:
autotask://companies- List all companiesautotask://companies/{id}- Get specific companyautotask://contacts- List all contactsautotask://contacts/{id}- Get specific contactautotask://tickets- List all ticketsautotask://tickets/{id}- Get specific ticketautotask://time-entries- List time entries
Tools
The server provides 39 tools for interacting with Autotask:
Company Operations
autotask_search_companies- Search companies with filtersautotask_create_company- Create new companyautotask_update_company- Update existing company
Contact Operations
autotask_search_contacts- Search contacts with filtersautotask_create_contact- Create new contact
Ticket Operations
autotask_search_tickets- Search tickets with filtersautotask_get_ticket_details- Get full ticket details by IDautotask_create_ticket- Create new ticket
Time Entry Operations
autotask_create_time_entry- Log time entryautotask_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 itemsautotask_get_billing_item- Get specific billing item by IDautotask_search_billing_item_approval_levels- Search multi-level approval records for time entries
Project Operations
autotask_search_projects- Search projects with filtersautotask_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_noteautotask_get_project_note/autotask_search_project_notes/autotask_create_project_noteautotask_get_company_note/autotask_search_company_notes/autotask_create_company_note
Attachment Operations
autotask_get_ticket_attachment- Get ticket attachmentautotask_search_ticket_attachments- Search ticket attachments
Financial Operations
autotask_get_expense_report/autotask_search_expense_reports/autotask_create_expense_reportautotask_get_quote/autotask_search_quotes/autotask_create_quoteautotask_search_invoices- Search invoicesautotask_search_contracts- Search contracts
Configuration Items
autotask_search_configuration_items- Search configuration items (assets)
Task Operations
autotask_search_tasks- Search project tasksautotask_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:mappingFor 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.jsThe HTTP transport exposes:
POST /mcpโ MCP Streamable HTTP endpointGET /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/healthFor 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 -dProduction 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:latestDevelopment Mode
# Start development environment with hot reload
docker compose --profile dev up autotask-mcp-devDevelopment
Setup
git clone https://github.com/wyre-technology/autotask-mcp.git
cd autotask-mcp
npm installAvailable 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 issuesProject 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 configurationTesting
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.tsTest 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 API username (email) |
| โ | - | Autotask API secret key |
| โ | - | Autotask integration code |
| โ | Auto-detected | Autotask API endpoint URL |
| โ |
| MCP server name |
| โ |
| Transport type ( |
| โ |
| HTTP transport port |
| โ |
| HTTP transport bind address |
| โ |
| Logging level |
| โ |
| Log output format |
| โ |
| Max concurrent Autotask API calls used to resolve company/resource names on search results. Kept low to stay under Autotask's concurrent-thread limit. |
| โ |
| Node.js environment |
Logging Levels
error: Only error messageswarn: Warnings and errorsinfo: General information, warnings, and errorsdebug: Detailed debugging information
Log Formats
simple: Human-readable console outputjson: Structured JSON output (recommended for production)
Rate Limits
Autotask enforces per-integration-code API thresholds on a rolling 1-hour window:
~10,000 req/hr (soft) โ warning email, sporadic
HTTP 429responses~20,000 req/hr (hard) โ sustained
HTTP 429until the window rolls
LLM-driven workflows fan out easily โ "status report on all open projects with notes" can issue hundreds of requests across a few minutes. The server tries to make this safer:
429 responses are surfaced as structured errors. Tool results carry
error_type: "rate_limited"and aretry_after_secondsfield parsed from Autotask'sRetry-Afterheader. The error message explicitly tells the LLM not to retry and to ask the user to scope the query โ this prevents repeated retries from extending the cooldown.Fan-out tool descriptions include rate-limit tips. Tools that are commonly looped over (
autotask_search_ticket_notes,autotask_search_project_notes,autotask_search_company_notes,autotask_search_time_entries,autotask_search_ticket_attachments) include a hint reminding the LLM to scope the parent record list before iterating.
Raising the limit
Per-integration thresholds can be increased in Autotask:
Autotask Admin โ Resources/Users (HR) โ Resources
Edit the dedicated API user โ Workflow Rules โ API Tracking Identifier
Adjust the threshold for the integration code your MCP server uses
This is the right answer when a single integration code is shared between Claude/Copilot/etc. and other tooling. For LLM-heavy workloads, dedicate a separate API user (and integration code) so a fan-out from one client doesn't starve others.
Patterns that help
Always scope by date range when searching notes, time entries, attachments. Even a 30-day window can drop call count by an order of magnitude.
Cache parent lookups. If you're iterating over 100 tickets, fetch the ticket list once and reuse it across follow-up queries; don't re-search per child.
Use
autotask_get_field_infoto discover picklist values once per session rather than refetching them per call.
If you're seeing threshold warnings from Autotask but the server seems fine, the LLM driver is probably issuing fan-out patterns. Tighten the prompt to scope before iterating.
Troubleshooting
Common Issues
Authentication Errors
Error: Missing required Autotask credentialsSolution: Ensure all required environment variables are set correctly.
Connection Timeouts
Error: Connection to Autotask API failedSolutions:
Check network connectivity
Verify API endpoint URL
Confirm API user has proper permissions
Permission Denied
Error: User does not have permission to access this resourceSolution: Review Autotask API user permissions and security level settings.
Debug Mode
Enable debug logging for detailed troubleshooting:
LOG_LEVEL=debug npm startHealth 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 startAutotask 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:
Admin > Resources (Users) > Resources/Users โ Add Resource
Set Security Level to API User
Note the username, secret, and integration code
Set
AUTOTASK_USERNAME,AUTOTASK_SECRET, andAUTOTASK_INTEGRATION_CODEper 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:
Check configuration file syntax (valid JSON)
Verify file path in the configuration
Ensure environment variables are set correctly
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:
Check network connectivity to Autotask API
Enable debug logging (
LOG_LEVEL=debug) to identify bottlenecksThe 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
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)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 |
Maintainer | ||
CLI bin fix |
Support
๐ Documentation
๐ Issue Tracker
๐ฌ Discussions
Acknowledgments
Model Context Protocol by Anthropic
Autotask REST API by Kaseya
autotask-node library
Built by WYRE Technology โ part of the MSP Claude Plugins ecosystem
Available Tools
98 toolsautotask_create_companyC
Create new company record
Inputs: companyName (required), companyType (required), city, phone, +5 more.
autotask_create_company_noteB
Create a new note for a company
Inputs: companyId (required), description (required), title, actionType.
autotask_create_contactC
Create new contact record
Inputs: lastName (required), companyID (required), firstName (required), phone, +2 more.
autotask_create_contractA
Create a new Contract in Autotask. Field names match the Autotask REST API exactly. status: 1=In Effect, 0=Inactive. Dates are ISO format (YYYY-MM-DD).
Inputs: endDate (required), companyID (required), startDate (required), contractName (required), +27 more.
autotask_create_contract_serviceA
Add a ContractService (service line item) to an existing Contract.
Inputs: serviceID (required), unitPrice (required), contractID (required), unitCost, +4 more.
autotask_create_expense_itemB
Create an expense item on an existing expense report
Inputs: amount (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: stage (required), title (required), status (required), companyId (required), +11 more.
autotask_create_phaseC
Create a new phase in an Autotask project
Inputs: title (required), projectID (required), dueDate, startDate, +2 more.
autotask_create_projectC
Create a new project in Autotask
Inputs: status (required), companyID (required), projectName (required), projectType (required), +5 more.
autotask_create_project_noteC
Create a new note for a project
Inputs: projectId (required), description (required), title, publish, +2 more.
autotask_create_quoteB
Create a new quote
Inputs: companyId (required), name, contactId, description, +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, unitCost, +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), endDateTime (required), startDateTime (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: ticketID (required), serviceCallID (required).
autotask_create_service_call_ticket_resourceB
Assign a resource (technician) to a service call ticket.
Inputs: resourceID (required), serviceCallTicketID (required), roleID.
autotask_create_taskC
Create a new task in Autotask
Inputs: title (required), status (required), projectID (required), taskType, +5 more.
autotask_create_ticketC
Create new ticket record
Inputs: title (required), companyID (required), description (required), source, +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: data (required), title (required), ticketId (required), publish, +2 more.
autotask_create_ticket_chargeA
Create charge on ticket for materials, costs, or expenses.
Inputs: name (required), ticketID (required), chargeType (required), status, +8 more.
autotask_create_ticket_checklist_itemB
Add a new checklist item to a ticket.
Inputs: itemName (required), ticketId (required), position, isCompleted.
autotask_create_ticket_noteA
Create a new note for a ticket
Inputs: publish (required), noteType (required), ticketId (required), description (required), +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), taskID, +8 more.
autotask_delete_quote_itemADestructive
โ DESTRUCTIVE โ IRREVERSIBLE. Permanently deletes a quote item (line item) from a quote. This action cannot be undone. Confirm with the user before invoking.
Inputs: quoteId (required), quoteItemId (required).
autotask_delete_service_callADestructive
โ DESTRUCTIVE โ IRREVERSIBLE. Permanently deletes a service call and all associated data. This action cannot be undone. Confirm with the user before invoking.
Inputs: serviceCallId (required).
autotask_delete_service_call_ticketADestructive
โ DESTRUCTIVE โ IRREVERSIBLE. Permanently removes a ticket association from a service call. This action cannot be undone. Confirm with the user before invoking.
Inputs: serviceCallTicketId (required).
autotask_delete_service_call_ticket_resourceADestructive
โ DESTRUCTIVE โ IRREVERSIBLE. Permanently removes a resource assignment from a service call ticket. This action cannot be undone. Confirm with the user before invoking.
Inputs: serviceCallTicketResourceId (required).
autotask_delete_ticket_chargeADestructive
โ DESTRUCTIVE โ IRREVERSIBLE. Permanently deletes a ticket charge record and all associated billing data. This action cannot be undone. Confirm with the user before invoking.
Inputs: chargeId (required), ticketId (required).
autotask_delete_ticket_checklist_itemADestructive
โ DESTRUCTIVE โ IRREVERSIBLE. Permanently deletes a checklist item from a ticket. This action cannot be undone. Confirm with the user before invoking.
Inputs: itemId (required), ticketId (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: noteId (required), companyId (required).
autotask_get_company_site_configurationA
Get company site configuration records. Call first to discover available fields.
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: noteId (required), projectId (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 ticket attachment. With includeData=false (default) returns metadata only โ fast, suitable for browsing. With includeData=true returns the base64 binary content via the top-level /TicketAttachments/{id} endpoint (the child endpoint never populates data). The attachment is verified to belong to the given ticketId. Oversized binaries are stripped from the response with a dataOmittedReason field โ Autotask attachments can be up to 3 MB, which is ~4 MB as base64 and may exceed the MCP client tool-result limit (~1 MB).
Inputs: ticketId (required), attachmentId (required), includeData, maxInlineBase64Bytes.
autotask_get_ticket_chargeB
Get a specific ticket charge by ID
Inputs: chargeId (required).
autotask_get_ticket_detailsB
Get full ticket details including notes, time entries, and custom fields.
Inputs: ticketID (required), fullDetails.
autotask_get_ticket_historyA
Get a single ticket history entry by ID. Each entry records one audited change to a ticket field (who, when, before/after).
Inputs: historyId (required).
autotask_get_ticket_noteA
Get a specific ticket note by ticket ID and note ID
Inputs: noteId (required), ticketId (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_raw_requestA
Escape hatch for Autotask REST endpoints not yet wrapped by a typed tool. Use sparingly โ typed tools are preferred for safety. The existing Content-Type, Accept, ApiIntegrationcode, UserName, Secret headers are added automatically. The path is resolved against the zone-resolved base URL (https://webservices.autotask.net/ATServicesRest/v1.0). Pass queryParams as a flat object of string/number/boolean values; they will be URL-encoded and appended to the path.
Inputs: path (required), method (required), body, queryParams.
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: page, pageSize, timeEntryId, approvalLevel, +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: page, dateTo, dateFrom, pageSize, +8 more.
autotask_search_companiesB
Search companies by name or status. Max 200/page.
Inputs: page, isActive, pageSize, searchTerm.
autotask_search_company_notesA
Search for notes on a specific company. Iterating across many companies trips Autotask's API threshold โ scope the parent list first.
Inputs: companyId (required), pageSize.
autotask_search_configuration_itemsB
Search for configuration items in Autotask with optional filters
Inputs: isActive, pageSize, companyID, productID, +1 more.
autotask_search_contactsA
Search contacts by name, email, or company. Max 200/page.
Inputs: page, isActive, pageSize, companyID, +1 more.
autotask_search_contractsC
Search for contracts in Autotask with optional filters
Inputs: status, pageSize, companyID, searchTerm.
autotask_search_expense_reportsC
Search for expense reports with optional filters
Inputs: status, pageSize, submitterId.
autotask_search_invoicesC
Search for invoices in Autotask with optional filters
Inputs: isVoided, pageSize, companyID, invoiceNumber.
autotask_search_opportunitiesC
Search for opportunities with optional filters
Inputs: status, pageSize, companyId, searchTerm.
autotask_search_productsC
Search for products with optional filters
Inputs: isActive, pageSize, searchTerm.
autotask_search_project_notesA
Search for notes on a specific project. Fan-out across many projects trips Autotask's API threshold (see issue #69) โ scope the parent list (status, company, date range) first.
Inputs: projectId (required), pageSize.
autotask_search_projectsC
Search for projects in Autotask. Returns 25 results per page by default. Use page parameter for more results.
Inputs: page, status, pageSize, companyID, +2 more.
autotask_search_quote_itemsA
Search for quote items, typically filtered by quote ID
Inputs: quoteId, pageSize, searchTerm.
autotask_search_quotesC
Search for quotes with optional filters
Inputs: pageSize, companyId, contactId, searchTerm, +1 more.
autotask_search_resourcesA
Search for resources (users) in Autotask. Returns 25 results per page by default. Use page parameter for more results.
Inputs: page, isActive, pageSize, searchTerm, +1 more.
autotask_search_service_bundlesC
Search for service bundles with optional filters
Inputs: isActive, pageSize, searchTerm.
autotask_search_service_callsB
Search for service calls in Autotask. Filter by company, status, or date range.
Inputs: status, pageSize, companyId, startAfter, +1 more.
autotask_search_service_call_ticket_resourcesB
Search for resource (technician) assignments on service call tickets.
Inputs: pageSize, resourceId, serviceCallTicketId.
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: pageSize, ticketId, serviceCallId.
autotask_search_servicesC
Search for services with optional filters
Inputs: isActive, pageSize, searchTerm.
autotask_search_tasksA
Search for tasks in Autotask. Returns 25 results per page by default. Use page parameter for more results.
Inputs: page, status, pageSize, projectID, +2 more.
autotask_search_ticket_attachmentsA
Search for attachments on a specific ticket. Each parent triggers a separate query โ scope the parent ticket list before iterating.
Inputs: ticketId (required), pageSize.
autotask_search_ticket_chargesA
Search ticket charges (materials, costs, expenses). Provide ticketId for best performance. Max 10 if unfiltered.
Inputs: pageSize, ticketId.
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_historyA
Get the audit trail of field changes for a ticket (status transitions, assignment changes, priority edits, etc.). Use this to answer questions like "when did this ticket move from In Progress to Waiting Customer" or "who changed the priority". Returns entries ordered by Autotask; sort/filter client-side if needed.
Inputs: ticketId (required), pageSize.
autotask_search_ticket_notesA
Search for notes on a specific ticket. Iterating across many tickets trips Autotask's per-integration API threshold โ scope the parent list first.
Inputs: ticketId (required), pageSize.
autotask_search_ticketsB
Search tickets by company, queue, status, priority. Use autotask_get_ticket_details for full data. Max 500/page.
Inputs: page, status, pageSize, companyID, +7 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. Common fan-out target โ scope by date range first to avoid Autotask's API threshold.
Inputs: page, taskId, billable, pageSize, +6 more.
autotask_test_connectionB
Test Autotask API connection
Inputs: no named parameters.
autotask_update_companyA
Update company record. invoiceTemplateID sets payment terms (103=Due on Receipt, 104=NET 30). Billing address fields separate from regular address.
Inputs: id (required), city, phone, state, +28 more.
autotask_update_company_site_configurationA
Update company site configuration. Fields are tenant-defined; call get first.
Inputs: id (required), updates (required).
autotask_update_contactB
Update contact record. Only provided fields are changed.
Inputs: id (required), city, phone, state, +12 more.
autotask_update_contractA
Update an existing Contract in Autotask (PATCH). Pass only fields you want to change; everything except id is optional. status: 1=In Effect, 0=Inactive.
Inputs: id (required), status, endDate, setupFee, +28 more.
autotask_update_contract_serviceA
Update an existing ContractService line on a Contract. Pass only fields you want to change.
Inputs: id (required), contractID (required), unitCost, serviceID, +5 more.
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), status, description, endDateTime, +8 more.
autotask_update_quote_itemA
Update an existing quote item (quantity, price, etc.)
Inputs: quoteItemId (required), quantity, unitPrice, isOptional, +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), status, complete, description, +2 more.
autotask_update_ticketA
Update ticket record. Only provided fields are changed.
Inputs: ticketId (required), title, status, priority, +7 more.
autotask_update_ticket_chargeA
Update an existing ticket charge. Only fields provided will be changed.
Inputs: chargeId (required), name, status, unitCost, +4 more.
autotask_update_ticket_checklist_itemB
Update a checklist item on a ticket โ edit text, mark complete/incomplete, or change position.
Inputs: itemId (required), ticketId (required), itemName, position, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 98 tools
Each tool targets a distinct entity and action (e.g., autotask_create_ticket vs. autotask_search_tickets). Multiple 'search' tools exist but are clearly scoped to different resources. No two tools share an overlapping purpose.
All tools follow the consistent pattern 'autotask_<verb>_<noun>', using standard verbs (create, update, delete, get, search, list) and clear entity names. Even meta-tools like autotask_list_categories fit the pattern.
98 tools is high but aligned with the broad scope of the Autotask PSA platform, covering many entities and sub-resources. The count is justified for comprehensive API coverage, though it borders on heavy.
Major entities (tickets, projects, companies, contacts) have create, read, update, and search operations, but notable deletions are missing for main resources (e.g., no autotask_delete_ticket or autotask_delete_project). Sub-items have deletes, but core CRUD is incomplete.
Related MCP Connectors
Connect any AI assistant to Syncro: manage tickets, invoices, customers, assets, and more.
Connect Claude, ChatGPT or any AI assistant to Zendesk tickets, CSAT, macros and Help Center.
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Build and run agents and automations across hundreds of apps using natural language.
Related MCP Servers
- AlicenseCqualityCmaintenanceProvides 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.100Apache 2.0
- AlicenseBqualityNot gradedmaintenanceGives AI assistants direct access to Autotask PSA for searching tickets, creating time entries, managing companies, projects, and more via natural language.100Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to work directly with ConnectWise Manage, allowing natural-language operations on tickets, time entries, companies, contacts, projects, invoices, opportunities, and more.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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