Skip to content

Autotask MCP connector

The Autotask connector brings tickets, ticket notes, companies, contacts and resources into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can look up, create and update service desk work in plain language, with every action logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

How many Autotask tickets are open for Acme this week?

Working in Autotask with Elaichi

  • List all Autotask tickets
  • Get single Autotask ticket by ID
  • List all Autotask ticket notes
Ask anything…
Governance / Audit log Last 24 hours
Autotask List all Autotask ticket notes Emily Carter · ChatGPT · 9:41 AM Done
Autotask Get single Autotask ticket by ID Emily Carter · ChatGPT · 9:41 AM Done
Autotask List all Autotask tickets Emily Carter · ChatGPT · 9:41 AM Done
Autotask Autotask tickets count Megan Brooks · Claude · 9:38 AM Done
Autotask Create a Autotask ticket Ryan Hayes · Cursor · 9:35 AM Done

How to connect Autotask to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Autotask MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Autotask MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Autotask MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Autotask MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Autotask MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Autotask to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Autotask through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Autotask is logged.

  • 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.”

See all 37 Autotask tools →

What connecting Autotask gets you

6 screens from Elaichi, each doing one job for your Autotask account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about Autotask tickets in plain language.

Answers come from live Autotask tickets, notes and companies, not a stale export.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Autotask here.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all Autotask tickets List Search Autotask Tickets using a JSON filter query. Returns Ticket objects including id, ticketNumber, title, description, status, priority, queueID, companyID, contactID, assignedResourceID, ticketType, issueType, dueDateTime, createDate, completedDate, lastActivityDate, resolution and userDefinedFields. The request body accepts a filter with operators such as eq, gte, contains, in, and grouping with and/or.
Get single Autotask ticket by ID Get Retrieve a single Autotask Ticket by its id. Returns the full Ticket object including status, priority, assignment, dates, resolution and user-defined fields.
Autotask tickets count Action Count Autotask Tickets matching a JSON filter query, without returning the records. Use the same filter syntax as the ticket list. Returns queryCount.
Create a Autotask ticket Create Create a Ticket in Autotask. Fields are sent at the top level of the request body (Autotask does not use a wrapper object). Required: title, companyID, status, priority, and either queueID or assignedResourceID. Returns the created ticket id.
Update a Autotask ticket by ID Update Fully update an Autotask Ticket (HTTP PUT). Include the ticket id plus every field you want to persist — fields omitted from a PUT may be cleared. Use partial_update (PATCH) to change only selected fields.

Tool catalog

37 Autotask tools ready without custom code.

Tickets, ticket notes and companies, each with list, count, create and update methods.

ElaichiToolboxes
Name Source template Tools Created

Service desk toolbox

Autotask · tickets and ticket notes

Autotask starter 18 Mar 4, 2026

Field engineering toolbox

Autotask · onsite tickets and time notes

— 9 Mar 2, 2026

Account management toolbox

Autotask · companies and ticket history

— 24 Feb 27, 2026

Escalations toolbox

Autotask · high priority tickets

Autotask starter 6 Feb 19, 2026

Billing toolbox

Autotask · companies and billable tickets

— 31 Jan 30, 2026

Reporting toolbox

Autotask · ticket counts and trends

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Autotask toolbox.

Curate one toolbox per team so service desk and finance see different Autotask tools.

ElaichiConnections
Connection Scope Status Access
AU

Autotask (Service desk)

Connected by Emily Carter

Personal • Active 1 team · 6 members
AU

Autotask (Field engineering)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
AU

Autotask (Escalations)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
AU

Autotask (Account management)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
AU

Autotask (Billing)

Connected by Ryan Hayes

Personal • Active Not shared
AU

Autotask (NOC after hours)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Autotask without seeing a credential.

Each Autotask connection shows who connected it and which teams and members share it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Autotask Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Autotask Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Autotask Tickets List Toolbox

Audit log

Answer who changed which Autotask ticket.

Append-only log of when, who, what happened, type and Autotask resource touched.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Autotask digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch tickets

    Autotask

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Autotask

    Queued

Automations

A schedule fires and Autotask work finishes.

Fetch tickets, group them, draft a digest, get approval, post a note back.

Autotask health

Refreshed 4 minutes ago · every 15 minutes · from the tickets collection

Live

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%

Collections and dashboards

Autotask ticket numbers land before anyone asks.

Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Autotask

All three can connect Autotask to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Autotask, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Autotask tools Allow or restrict single Autotask tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Autotask call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

Questions, answered

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, Microsoft Copilot, 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 my team share one Autotask connection?

Yes. One person connects Autotask in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every ticket created or note added through the shared Autotask connection is recorded under their own name in the audit log.

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 restricting updates, or allow adding notes while restricting changes to ticket status. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says. 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, Cursor and Microsoft Copilot. 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.

Does the Autotask MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Autotask is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Autotask?

Yes. Both let Claude, ChatGPT or Cursor use Autotask. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Autotask call.

How is Elaichi different from Composio for Autotask?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Autotask: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Autotask in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot