---
title: "Autotask MCP server for AI agents - actionlake"
description: "Give Claude 62 Autotask actions through one MCP server: PSA, companies, ticketing, billing. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/autotask
updated: 2026-09-24
---

Connectors · MSP & PSA

# Autotask MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Autotask and the rest of your systems. It gives your agent 62 Autotask actions (34 reads, 20 writes and 8 that wait for a confirmation) and holds the Autotask credential itself, so the agent never does. It paces Autotask's limits and records every call.

[Connect Autotask free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "autotask.tickets.query",
  intent: "check which Autotask account is connected"
}
# Search Autotask tickets · read · 1 upstream call
```

- 62 actions in one signed file
- 34 read look, never change
- 20 write create and update
- 8 wait for a yes destructive, confirmed first

Set up

## Connect Autotask in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Autotask.
   Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `integration_code` API Integration Code
   - `username` API user name
   - `secret` API user secret
   Found for you at connect: base url.
   ```
   account { op: "connections.requirements", service: "autotask" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "autotask.tickets.query" }
   # search autotask tickets · read · 1 upstream call
   check { action: "autotask.tickets.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Autotask at a glance

**Sign-in**

Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`integration_code` `username` `secret`

**Found for you**

base url

**Limits we pace to**

10,000 calls an hour, per connection

**API covered**

Autotask PSA API 1.0, at your Autotask instance's API base URL, which you enter when connecting (path /V1.0)

**Built from**

Autotask's documentation, read 1 September 2026[autotask.net](https://www.autotask.net/help/developerhelp/Content/APIs/REST/REST_API_Home.htm)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

34 of 34 reads, for up to 1 minute; a write clears what it affects

**Ready-made plans**

6 in the store

**Shared entities**

3, so ask can line Autotask up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Autotask.

62 actions in 8 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **34** read look, never change
- **20** write create and update
- **8** destructive wait for a confirmation

1. ### PSA
   53
   25 read · 20 write · 8 destructive
   Create an Autotask ticket · Create an Autotask project · Update an Autotask ticket · Get one Autotask project
2. ### Companies
   2
   2 read · 0 write · 0 destructive
   Get one Autotask company · Search Autotask companies
3. ### Ticketing
   2
   2 read · 0 write · 0 destructive
   Search Autotask tickets · Get one Autotask ticket
4. ### Billing
   1
   1 read · 0 write · 0 destructive
   Search Autotask invoices
5. ### Contacts
   1
   1 read · 0 write · 0 destructive
   Search Autotask contacts
6. ### Projects
   1
   1 read · 0 write · 0 destructive
   Search Autotask projects
7. ### Resources
   1
   1 read · 0 write · 0 destructive
   Search Autotask resources
8. ### Time
   1
   1 read · 0 write · 0 destructive
   Search Autotask time entries

Top actions

## The Autotask API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 53 of Autotask's 59 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `autotask.tickets.create` Create an Autotask ticket | Raise a service ticket against a company. | write | `service.ticket.create` 54 connectors |
| `autotask.tickets.query` Search Autotask tickets | Search Autotask PSA service tickets by status, company, queue, assigned resource, priority or date — or with a raw search_filter document. | read | `service.ticket.query` 8 connectors |
| `autotask.projects.create` Create an Autotask project | Create the project header. Set dates correctly first: startDateTime cannot change once any phase or task exists. | write | `work.project.create` 102 connectors |
| `autotask.projects.get` Get one Autotask project | Fetch a single project by its numeric id. | read | `work.project.get` 106 connectors |
| `autotask.tickets.delete` Delete an Autotask ticket | Delete one ticket by id. Irreversible. | destructive | `service.ticket.delete` 42 connectors |
| `autotask.companies.create` Create an Autotask company | Add a customer, prospect or vendor. | write | `crm.company.create` 142 connectors |
| `autotask.companies.get` Get one Autotask company | Fetch a single Autotask PSA company by its numeric id. | read | `crm.company.get` 162 connectors |
| `autotask.tasks.create` Add a task to an Autotask project | Create a task under a project, optionally inside a phase. | write | `work.task.create` 127 connectors |
| `autotask.ticket_notes.create` Add a note to an Autotask ticket | Append a note to an existing ticket. | write | `service.ticket_note.create` 24 connectors |
| `autotask.contracts.create` Create an Autotask contract | Create a fixed-price, T&M, block-hour, retainer or recurring-service contract against a company. | write | `service.contract.create` 19 connectors |
| `autotask.time_entries.create` Log time against an Autotask ticket | Record worked time on a ticket or task. | write | `work.time_entry.create` 56 connectors |
| `autotask.contacts.create` Create an Autotask contact | Add a person at a company. | write | `crm.contact.create` 161 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Autotask actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Autotask tickets have been open the longest? Show me the ten oldest with their status.
   calls `autotask.tickets.query`
2. Plan write
   Record delivered hardware against a client and open a deployment ticket in Autotask.
   calls `autotask.companies.get` `autotask.configuration_items.query` `autotask.configuration_items.update` `autotask.tickets.create` `autotask.tickets.get` +1 more
3. Plan write
   Log billable time against a ticket and note it in Autotask.
   calls `autotask.tickets.get` `autotask.billing_codes.query` `autotask.time_entries.create` `autotask.ticket_notes.create`
4. Write write
   Create an Autotask ticket in Autotask. Show me exactly what you will send before you save it.
   calls `autotask.tickets.create`
5. Across systems read
   Which Autotask companies have invoices in NetSuite, and how many each?
   calls `autotask.companies.query` `netsuite.views.invoices`

Across your systems

## Autotask, joined to the rest of your business.

One `ask` fetches from Autotask and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

- Which Autotask companies have invoices in NetSuite, and how many each?
  `autotask.companies.query` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite)
- Which Autotask companies have tickets in HubSpot CRM, and how many each?
  `autotask.companies.query` + `hubspot_crm.tickets.list`, on `crm.company` · [HubSpot CRM](https://actionlake.com/connectors/hubspot-crm)

Also mapped by other connectors `crm.company` **227** `work.project` **116** `service.ticket` **62**

ask

```
ask {
  intent: "which Autotask companies have invoices in NetSuite, and how many each",
  steps: [
    { action: "autotask.companies.query", as: "co", input: {}, limit: 100, max_pages: 5 },
    { action: "netsuite.views.invoices", as: "inv", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "co",
        right: "inv",
        on: "crm.company",
        group_by: "co.name",
        select: ["co.name", "count(inv.id) as invoices"]
    } }
  ]
}
```

Example. Run it through check first: it validates the steps and prices them, and it is free.

The plan store

## Ready-made plans for Autotask.

6 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.

1. ### Sweep contracts nearing their end date and raise renewal tickets
   Use it when Someone asks for renewal tickets to be raised for contracts that are about to expire.
   A person decides Raise one renewal ticket in queue _queue id_ for each contract expiring after _ends after_.
   **Effect**
   write
   **Steps**
   4 · loops
   **Needs**
   ends after and queue id
   **Install**
   `autotask-expiring-contract-renewal-sweep`
2. ### Log billable time against a ticket and note it
   Use it when An engineer needs hours booked to a ticket with a matching note on the ticket.
   **Effect**
   write
   **Steps**
   4
   **Needs**
   date worked, hours worked, resource id, role id, summary and ticket id
   **Install**
   `autotask-log-time-against-ticket`
3. ### Onboard a new client company with a primary contact and contract
   Use it when A new client has been won and needs its Autotask company, contact and contract set up.
   A person decides Create a _contract type_ contract '_contract name_' for _company name_ running _start date_ to _end date_.
   **Effect**
   write
   **Steps**
   5
   **Needs**
   company name, company type, contact first name, contact last name, contract name, contract type, end date, owner resource id, phone, queue id and start date
   **Install**
   `autotask-onboard-new-client`
4. ### Spin up a delivery project from an existing contract
   Use it when A signed contract needs its delivery project, phase and initial task list created.
   A person decides Create project '_project name_' for company _company id_ under contract _contractName_, running _start_ to _end_.
   **Effect**
   write
   **Steps**
   5 · loops
   **Needs**
   company id, contract id, end, lead resource id, phase title, project name, project type, start and tasks
   **Install**
   `autotask-spin-up-project-from-contract`
5. ### Record delivered hardware against a client and open a deployment ticket
   Use it when Hardware has arrived for a client and needs recording plus a deployment ticket.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   company id, configuration item id, install date, location, queue id and serial number
   **Install**
   `autotask-new-hardware-asset-intake`
6. ### Remove tasks from a cancelled project after sign-off
   Use it when A project was cancelled and its remaining task list has to be cleared out.
   A person decides Permanently delete all listed tasks on project '_projectName_'. This cannot be undone.
   **Effect**
   destructive
   **Steps**
   4 · loops
   **Needs**
   project id
   **Install**
   `autotask-purge-cancelled-project-tasks`

install a plan

```
account { op: "plans.install", slug: "autotask-expiring-contract-renewal-sweep" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance for Autotask

## Destructive actions wait for a yes.

8 Autotask actions are destructive. These are all of them:

- Delete an Autotask ticket `autotask.tickets.delete`
- Delete an Autotask project task `autotask.tasks.delete`
- Delete an Autotask time entry `autotask.time_entries.delete`
- Delete an Autotask ticket note `autotask.ticket_notes.delete`
- Delete an Autotask contact `autotask.contacts.delete`
- Remove a service from an Autotask contract `autotask.contract_services.delete`
- Delete an Autotask contract milestone `autotask.contract_milestones.delete`
- Delete an Autotask project phase `autotask.phases.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do autotask.tickets.delete confirm_policy: **human**

Delete an Autotask ticket?

**intent:** the user asked me to delete an Autotask ticket

run suspended · waiting for a named person · key _autotask-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "autotask-agent",
  allowed_actions: ["autotask.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "autotask.tickets.delete", approver: "lead@example.com" },
    { match: "autotask.tasks.delete", approver: "lead@example.com" },
    { match: "autotask.time_entries.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Autotask only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Autotask costs on actionlake.

Every Autotask action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Autotask refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 62 Autotask actions
- 22 actions page each page of a long list is one call
- 34 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Autotask action.

62 actions by area: the id your agent calls, what it does, and its effect.

**PSA 53**

- `autotask.billing_codes.query` List Autotask billing codes read
- `autotask.companies.create` Create an Autotask company write
- `autotask.companies.update` Update an Autotask company write
- `autotask.configuration_items.get` Get one Autotask configuration item read
- `autotask.configuration_items.query` Search Autotask configuration items read
- `autotask.configuration_items.update` Update an Autotask configuration item write
- `autotask.contacts.create` Create an Autotask contact write
- `autotask.contacts.delete` Delete an Autotask contact destructive
- `autotask.contacts.get` Get one Autotask contact read
- `autotask.contacts.update` Update an Autotask contact write
- `autotask.contract_milestones.create` Add a milestone to an Autotask contract write
- `autotask.contract_milestones.delete` Delete an Autotask contract milestone destructive
- `autotask.contract_rates.create` Set a role's hourly rate on an Autotask contract write
- `autotask.contract_services.create` Add a service to an Autotask contract write
- `autotask.contract_services.delete` Remove a service from an Autotask contract destructive
- `autotask.contracts.create` Create an Autotask contract write
- `autotask.contracts.get` Get one Autotask contract read
- `autotask.contracts.query` Search Autotask contracts read
- `autotask.contracts.update` Update an Autotask contract write
- `autotask.departments.query` List Autotask departments read
- `autotask.entity_information.fields` Describe an Autotask entity's fields read
- `autotask.invoices.get` Get one Autotask invoice read
- `autotask.opportunities.get` Get one Autotask opportunity read
- `autotask.opportunities.query` Search Autotask opportunities read
- `autotask.opportunities.update` Update an Autotask opportunity write
- `autotask.organizational_level_1.query` List Autotask organizational level 1 read
- `autotask.organizational_level_2.query` List Autotask organizational level 2 read
- `autotask.organizational_level_associations.query` List Autotask lines of business read
- `autotask.phases.create` Add a phase to an Autotask project write
- `autotask.phases.delete` Delete an Autotask project phase destructive
- `autotask.projects.create` Create an Autotask project write
- `autotask.projects.get` Get one Autotask project read
- `autotask.projects.update` Update an Autotask project write
- `autotask.quotes.query` List Autotask quotes read
- `autotask.roles.query` List Autotask roles read
- `autotask.service_calls.query` List Autotask service calls read
- `autotask.services.query` List Autotask services read
- `autotask.subscriptions.query` List Autotask subscriptions read
- `autotask.tasks.create` Add a task to an Autotask project write
- `autotask.tasks.delete` Delete an Autotask project task destructive
- `autotask.tasks.get` Get one Autotask task read
- `autotask.tasks.query` Search Autotask project tasks read
- `autotask.tasks.update` Update an Autotask task write
- `autotask.threshold_information.query` Read Autotask API threshold headroom read
- `autotask.ticket_categories.query` List Autotask ticket categories read
- `autotask.ticket_notes.create` Add a note to an Autotask ticket write
- `autotask.ticket_notes.delete` Delete an Autotask ticket note destructive
- `autotask.tickets.create` Create an Autotask ticket write
- `autotask.tickets.delete` Delete an Autotask ticket destructive
- `autotask.tickets.update` Update an Autotask ticket write
- `autotask.time_entries.create` Log time against an Autotask ticket write
- `autotask.time_entries.delete` Delete an Autotask time entry destructive
- `autotask.time_entries.get` Get one Autotask time entry read

**Companies 2**

- `autotask.companies.get` Get one Autotask company read
- `autotask.companies.query` Search Autotask companies read

**Ticketing 2**

- `autotask.tickets.get` Get one Autotask ticket read
- `autotask.tickets.query` Search Autotask tickets read

**Billing 1**

- `autotask.invoices.query` Search Autotask invoices read

**Contacts 1**

- `autotask.contacts.query` Search Autotask contacts read

**Projects 1**

- `autotask.projects.query` Search Autotask projects read

**Resources 1**

- `autotask.resources.query` Search Autotask resources read

**Time 1**

- `autotask.time_entries.query` Search Autotask time entries read

Questions

## The Autotask MCP server, answered.

**Is there an Autotask MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 62 Autotask actions across PSA, companies, ticketing and billing, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Autotask.

**What do I need to connect Autotask?**

API Integration Code, API user name and API user secret. actionlake finds base url for you when you connect. The free call account { op: "connections.requirements", service: "autotask" } lists exactly what to paste.

**Can an AI agent delete or change things in Autotask?**

Only if its key allows it, and only with an explicit confirmation. 8 Autotask actions are destructive, including delete an Autotask ticket, delete an Autotask project task and delete an Autotask time entry. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Autotask API limit?**

actionlake paces every call to the limits in the Autotask service file: 10,000 calls an hour per connection. Repeated reads are answered from cache (34 Autotask actions can be), which never reaches Autotask.

**What does an Autotask action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (22 Autotask actions page). Cache hits, searches, dry runs and calls Autotask refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Autotask API does it cover?**

The Autotask PSA API 1.0 at your Autotask instance's API base URL, which you enter when connecting (path /V1.0). It is built from Autotask's documentation as read on 1 September 2026. 62 actions in 8 areas, each one in the signed service file (version 1.0.0).

**Can I combine Autotask with my other systems?**

Yes. ask joins Autotask to NetSuite or HubSpot CRM on the same customer and returns the answer rather than every row. Autotask maps crm.company, which 227 other connectors also map.

**Does actionlake keep my Autotask data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 1 minute, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Autotask credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Autotask

Shares the most action names with

- [Gorelo 25](https://actionlake.com/connectors/gorelo)
- [Accelo 23](https://actionlake.com/connectors/accelo)
- [SuperOps RMM+PSA 21](https://actionlake.com/connectors/superops-rmm-psa)
- [Zomentum 16](https://actionlake.com/connectors/zomentum)
- [Rocketlane 16](https://actionlake.com/connectors/rocketlane)
- [Atera 14](https://actionlake.com/connectors/atera)

Joins with, on shared entities

- [Adobe Workfront 3](https://actionlake.com/connectors/adobe-workfront)
- [Acumatica Cloud ERP 3](https://actionlake.com/connectors/acumatica-cloud-erp)
- [Odoo 3](https://actionlake.com/connectors/odoo)
- [Unified.to 3](https://actionlake.com/connectors/unified-to)
- [ERPNext (Frappe) 3](https://actionlake.com/connectors/erpnext-frappe)
- [ServiceTitan 3](https://actionlake.com/connectors/servicetitan)

Browse

- [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Autotask; the name is the vendor's own. Counts are from the Autotask service file, version 1.0.0.

## Give your agent Autotask today.

[Connect Autotask free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/autotask
More: https://actionlake.com/llms.txt
