Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Autotask PSA in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Autotask PSA by Datto (Kaseya): query companies, contacts, tickets and notes, time entries, projects and tasks, resources, contracts and configuration items; create and update tickets, add notes and log time. Autotask REST API.
Try asking
Example prompts for Autotask PSA
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Autotask PSA, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Autotask PSA
Autotask PSA by Datto (Kaseya): query companies, contacts, tickets and notes, time entries, projects and tasks, resources, contracts and configuration items; create and update tickets, add notes and log time. Autotask REST API.
Setup
The connector uses the Autotask PSA REST API. It needs an API-only resource, which only an Autotask administrator can create.
- In Autotask open Admin → Resources/Users → New API User and give the resource the API User (API-only) security level.
- On its Security tab, under API Tracking Identifier, pick your integration vendor or let Autotask generate a custom (internal integration) identifier. Copy it into
AUTOTASK_INTEGRATION_CODE. - Copy the API user's username (an email-like value) into
AUTOTASK_USERNAMEand the generated secret intoAUTOTASK_SECRET. The secret is shown in full only when it is generated. - Open
https://webservices.autotask.net/atservicesrest/v1.0/zoneInformation?user=<API username>in a browser and copy the host from theurlfield intoAUTOTASK_ZONE_HOST, for examplewebservices5.autotask.net: host only, withouthttps://and without a path. A wrong zone answers 500 or 401 even with correct credentials. - Start with
autotask_query_companies, thenautotask_query_ticketswithcompanyID. Status, priority and queue are numeric ids that differ per database: read them withautotask_get_entity_fields(for example entityTickets) before filtering or writing them.
A query returns at most 500 records; Autotask allows 10,000 requests per hour per database, so use autotask_count_tickets for counts. Creating and updating tickets, adding notes and logging time change data and can trigger customer notifications through workflow rules. Nothing is deleted by this connector.
Prerequisites: AUTOTASK_ZONE_HOST, AUTOTASK_USERNAME, AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE
Install the connector locally
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://localhost:3000/connectors/store, pick Autotask PSA and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
autotask_query_companies | Query companies (customers, prospects, vendors) with an Autotask filter: name, type, phone, address, owner resource and active flag |
autotask_get_company | Get one company by id with all standard fields and user-defined fields |
autotask_query_contacts | Query contacts (people at customer companies) with an Autotask filter: name, email, phone, company and active flag |
autotask_get_contact | Get one contact by id: name, company, email addresses, phones, title and active flag |
autotask_query_tickets | Query service desk tickets with an Autotask filter: number, title, status, priority, queue, company, contact, assigned resource, due date… |
autotask_count_tickets | Count the tickets matching an Autotask filter without returning them, for example open tickets per queue |
autotask_get_ticket | Get one ticket by id with all fields: title, description, status, priority, queue, issue and sub-issue type, company, contact, assigned… |
autotask_query_ticket_notes | Query ticket notes with an Autotask filter, usually by ticketID: title, description, note type, publish (who can see it), creator and date |
autotask_query_time_entries | Query time entries with an Autotask filter: resource, ticket or task, date worked, start and end time, hours worked and to bill, role… |
autotask_get_time_entry | Get one time entry by id: resource, ticket or task, dates, hours worked, hours to bill, role, billing code, summary and internal notes |
autotask_query_projects | Query projects with an Autotask filter: name, number, company, status, type, project lead, start and end dates, estimated and actual hours |
autotask_get_project | Get one project by id with status, type, company, lead resource, dates, hours, revenue fields and user-defined fields |
autotask_query_tasks | Query project tasks with an Autotask filter, usually by projectID: title, status, assigned resource, phase, start and end dates, estimated… |
autotask_query_resources | Query resources (Autotask users: technicians, employees) with an Autotask filter: name, email, title, active flag and default service desk… |
autotask_get_resource | Get one resource (Autotask user) by id: name, email, title, active flag, location, license type and default role |
autotask_query_contracts | Query customer contracts with an Autotask filter: name, number, company, type (time and materials, fixed price, block hours, retainer… |
autotask_query_configuration_items | Query configuration items (managed devices and assets) with an Autotask filter: reference title, serial number, company, product, install… |
autotask_get_entity_fields | Describe the fields of an entity: name, data type, whether it is required or read-only, and for picklists the allowed values with their… |
autotask_query | Query any Autotask entity that has no dedicated tool (for example Roles, BillingCodes, ServiceCalls, Opportunities, Invoices, Quotes) with… |
autotask_create_ticket | Create a service desk ticket for a company |
autotask_update_ticket | Change fields of an existing ticket: status, priority, queue, assigned resource, due date, title or description |
autotask_create_ticket_note | Add a note to a ticket. publish 1 makes it visible to all Autotask users and the customer portal, 2 to internal users only |
autotask_create_time_entry | Log time worked on a ticket or task for a resource: date, start and end time or hours, role, summary and internal notes |
Next steps
Was this guide helpful?
