Introduction
The Autotask MCP Server connects AI assistants (like Claude) to your Kaseya Autotask PSA instance through the Model Context Protocol.
How it works
Section titled “How it works”The MCP server acts as a bridge between your AI assistant and the Autotask REST API. When you ask your AI assistant about tickets, companies, or projects, the assistant uses the MCP server’s tools to query Autotask and return structured results.
┌──────────────┐ ┌──────────────┐ ┌──────────────┐│ AI Assistant │────▶│ MCP Server │────▶│ Autotask API ││ (Claude) │◀────│ │◀────│ │└──────────────┘ └──────────────┘ └──────────────┘Key Features
Section titled “Key Features”- 39 tools covering companies, contacts, tickets, projects, time entries, notes, attachments, and financial data
- Automatic ID-to-name mapping — results include human-readable company and resource names
- Compact response format — search results are optimized for AI context windows
- Pagination support — handle large result sets efficiently
- Picklist discovery — look up valid queue IDs, ticket statuses, and priorities
Supported Entities
Section titled “Supported Entities”| Entity | Search | Get | Create | Update |
|---|---|---|---|---|
| Companies | ✓ | ✓ | ✓ | ✓ |
| Contacts | ✓ | ✓ | ✓ | — |
| Tickets | ✓ | ✓ | ✓ | — |
| Projects | ✓ | ✓ | ✓ | — |
| Tasks | ✓ | — | ✓ | — |
| Time Entries | — | — | ✓ | — |
| Notes (Ticket/Project/Company) | ✓ | ✓ | ✓ | — |
| Attachments | ✓ | ✓ | — | — |
| Configuration Items | ✓ | — | — | — |
| Contracts | ✓ | — | — | — |
| Invoices | ✓ | — | — | — |
| Expense Reports | ✓ | ✓ | ✓ | — |
| Quotes | ✓ | ✓ | ✓ | — |