Ticketing
Autotask MCP connector
The Autotask connector brings tickets, ticket notes, companies, contacts and resources into Claude, ChatGPT, Cursor and any MCP client, so your team can look up, create and update service desk work in plain language, with every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Autotask to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Autotask once
-
Open Connections, choose Add connection, and pick Autotask.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Autotask API key. One person generates a token in Autotask and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Autotask to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Autotask to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Autotask to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Autotask to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Autotask through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Service desk
Log a ticket while the client is talking
Describe the problem as the caller explains it and a new Autotask ticket is created against the right company and contact, with the details filled in before the call ends.
-
Service desk
Catch the ticket up after the fix
Say what you did and the ticket gets a note, a new status and an updated description, without opening Autotask and clicking through each field.
-
Dispatch
See what is open and who owns it
Ask for every open ticket in a queue, grouped by the resource assigned, and spot the ones nobody has picked up yet.
-
Account management
Prepare for a client review in minutes
Pull every ticket a company has raised this quarter, read the notes, and walk into the meeting knowing what went wrong and how quickly it was fixed.
-
Operations
Set up a new client without the forms
Create the company record in Autotask and add its main contacts in one go, then check the details read back correctly.
-
Management
Get ticket counts without building a report
Ask how many tickets are open, how many came in this week, or how many sit with one technician, and get a number from live Autotask records.
Try asking
- “How many Autotask tickets are open for Acme this week?”
- “Add a note to Autotask ticket 48210 about the callback.”
- “List Autotask companies with tickets unresolved over five days.”
AI tools
Autotask tools for your AI agents
37 tools are ready to call through Elaichi's MCP endpoint the moment you connect Autotask, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Autotask gets you
6 screens from the product, each doing one job for your Autotask account.
The agent
Ask about Autotask tickets in plain language.
Answers come from live Autotask tickets, notes and companies, not a stale export.
- tickets
- ticket notes
- companies
- resources
Ask Elaichi to work across your apps.
How many Autotask tickets are open for Acme this week?
Add a note to Autotask ticket 48210 about the callback.
List Autotask companies with tickets unresolved over five days.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Autotask here.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
37 Autotask tools ready without custom code.
Tickets, ticket notes and companies, each with list, count, create and update methods.
- List all Autotask tickets
- Get single Autotask ticket by ID
- Autotask tickets count
- Create a Autotask ticket
Toolboxes
Every team gets its own Autotask toolbox.
Curate one toolbox per team so service desk and finance see different Autotask tools.
- Service desk
- Field engineering
- Account management
- Escalations
Shared connections
Teammates use Autotask without seeing a credential.
Each Autotask connection shows who connected it and which teams and members share it.
- Service desk
- Field engineering
- Escalations
- Account management
Audit log
Answer who changed which Autotask ticket.
Append-only log of when, who, what happened, type and Autotask resource touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and Autotask work finishes.
Fetch tickets, group them, draft a digest, get approval, post a note back.
Autotask digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
Autotask
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Autotask
Queued
Collections and dashboards
Autotask ticket numbers land before anyone asks.
Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.
Autotask health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Ticket notes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Service desk 34%
Field engineering 27%
Escalations 21%
Account management 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Autotask to Claude?
In Elaichi, choose Autotask and paste in the API key from your Autotask account, then it is connected. There is no OAuth application to register and no client ID or secret to generate. In Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Autotask tickets, companies and contacts are available in the conversation.
Does Autotask work with ChatGPT and Cursor as well as Claude?
Yes. Autotask is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. Each client signs in over OAuth, so nobody pastes an Autotask API key into a chat window.
What can an AI agent actually do with my Autotask data?
An agent can list and read Autotask tickets, ticket notes, companies, contacts and resources, count them, and create or update tickets, notes, companies and contacts. In practice that means logging a ticket from a call, adding a note after a fix, checking what is open for a client, or setting up a new company with its contacts. Autotask has a lot of actions available, so short, concrete asks like "open tickets for Acme this week" work better than long paragraphs.
Does connecting Autotask give the AI access to every ticket and company?
No. Every request runs inside the Autotask access of the person who signed in, so an agent sees the tickets, companies and contacts that person can already see in Autotask, and nothing more. Elaichi can narrow that further, for example to reading only, but it can never widen it beyond what Autotask already allows.
Can I stop an agent from deleting or changing things in Autotask?
Yes. Restrictions in Elaichi work per action, so you can allow reading Autotask tickets and companies while blocking updates, or allow adding notes while blocking changes to ticket status. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it. This connector does not delete Autotask records at all.
What happens to an Autotask connection when someone leaves?
Offboarding that person in Elaichi ends their access to Autotask through every client at once, including Claude, ChatGPT and Cursor. A shared Autotask connection keeps working for everyone else on the team. If you ever want to remove Autotask entirely, disconnecting it once in Elaichi removes it from every client at the same time.
Put Autotask in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.