[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Autotask MCP server: Let your AI agent work your Autotask tickets. > Autotask has an official REST API and, since this year, an official MCP server from Kaseya in alpha (checked 6 Nov 2026). Both run as an API user with an integration code that an admin sets up. Cotlet adds 11 Autotask tools hosted, over MCP for agents and REST for scripts, with none of that setup. Your agent searches tickets, adds notes and logs time in Autotask PSA. You sign in once, with no API user, no integration code and no server to host. It works inside the ChatGPT and Claude apps. - Free 7-day trial, no card - Unofficial, not affiliated with Autotask or Kaseya - Page: https://cotlet.dev/integrations/autotask-api-mcp-server ## What can your AI agent do in Autotask? - Triage new tickets by your rules - Add a status note to a ticket - Log time from a daily summary - Chase tickets with no recent update - Create tickets from email requests - Find a company and its open tickets ## Does Autotask have an MCP server or an API? - The REST API is free with your Autotask license. Autotask's help says the developer tools are for people with software development experience, and support is not part of a standard contract. - Kaseya's MCP server is published in github.com/kaseya/mcp-servers as an early-access release for Claude Desktop and Claude Code. Kaseya has no guidance for ChatGPT yet and plans OAuth 2.1 sign-in for FY27. - Zapier has an official Autotask app and a Zapier MCP page with actions to create tickets, notes and time entries. n8n has no Autotask node page. | What you need | Official REST API | Kaseya MCP (alpha) | Cotlet | |---|---|---|---| | Search tickets by company, status or queue | Yes, you code it | Yes | Yes | | Add a note to a ticket | Yes, you code it | Yes | Yes, after your OK | | Create and update tickets, log time | Yes, you code it | Yes, with a preview | Yes, after your OK | | No API user or integration code | No | No | Yes, your own sign-in | | Changes logged under your name | Under the API user | Under the API user | Yes, your own login | | Runs in the ChatGPT and Claude apps, 24/7 | No | Claude Desktop and Code | Yes, hosted | Checked 6 Nov 2026. Sources: [Autotask developer help: General information about Autotask APIs](https://www.autotask.net/help/Developerhelp/Content/APIs/General/APIs.htm), [Autotask developer help: Defining an API User](https://www.autotask.net/help/developerhelp/Content/APIs/General/Define_API_User.htm), [Autotask developer help: REST API supportability, thresholds and limits](https://www.autotask.net/help/developerhelp/Content/APIs/REST/General_Topics/REST_Thresholds_Limits.htm), [GitHub: kaseya/mcp-servers (Autotask, alpha)](https://github.com/kaseya/mcp-servers), [Zapier: Autotask MCP](https://zapier.com/mcp/autotask) ## How does the Autotask MCP server work? 1. **Sign in to Autotask.** Use your own login. 2. **Connect your AI agent.** Paste one Cotlet address. 3. **Ask in plain words.** Your agent works the tickets. We never keep your Autotask password, and no note or ticket change happens until you approve it. ## How to connect Autotask to your AI agent Use MCP with your AI agent, or the same tools over REST in n8n, Make and scripts. 1. **Enable Autotask for agents.** Sign up, log in to Autotask in its Cloud Browser, then press Enable for agents. 2. **Add the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent. 3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console. One shared address, `https://cotlet.dev/mcp/v1`, also carries Autotask next to your other apps. If you enable Autotask after connecting, refresh the connector so the new tools show up. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-autotask \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-autotask": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-autotask] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: autotask_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: autotask_write ``` ## All 11 Autotask MCP tools ### Tickets Read the options first, so status, priority and queue are your own labels. A label Autotask does not have fails at once and the error lists the valid ones. - **Search tickets** (`search_tickets`, read): Find tickets by company, status, queue, priority, assignee or age. - **Get ticket** (`get_ticket`, read): Read one ticket with its description, contact and fields. - **List ticket options** (`list_ticket_options`, read): List the statuses, priorities and queues your Autotask account uses. - **Create ticket** (`create_ticket`, write, asks first): Open a new ticket for a company. - **Update ticket** (`update_ticket`, write, asks first): Change status, priority, queue or assignee of a ticket. ### Notes Notes can reach a customer or technician through Autotask notifications. Notes cannot be removed by these tools. - **List ticket notes** (`list_ticket_notes`, read): Read the notes on a ticket, newest first. - **Add ticket note** (`add_ticket_note`, write, asks first): Add a note to a ticket. ### Time entries Autotask can refuse time on a Complete ticket when its Service Desk setting prohibits it. The error says so. - **List time entries** (`list_time_entries`, read): Read the time entries logged on a ticket or by a person on a day. - **Log time entry** (`log_time_entry`, write, asks first): Log hours on a ticket. ### Companies and contacts Look up the company and contact IDs before you create or filter tickets. - **Search companies** (`search_companies`, read): Find companies (accounts) by name. - **Search contacts** (`search_contacts`, read): Find the people at a company by name or email. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/autotask-api-mcp-server#tools ## Who can see my Autotask session, and how do I revoke it? - **What we store.** Your logged-in Autotask profile, encrypted with AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 11 Autotask tools. Never the cookie or your login. - **What the session sees.** What your security level sees: tickets, notes, time, companies. - **What no tool touches.** Contracts, billing, resources, security levels and deleting. - **If Autotask asks to sign in.** You sign in again in your own browser, with your MFA. We never type it. - **How to cut access.** Disable for agents, reset the browser, or end the session in Autotask. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). ## What can the agent do in my Autotask? You sign in with your own Autotask login, so the agent sees and changes only what that login can. A technician level stays a technician level. Tickets and companies you cannot open do not show up in a result. Autotask notes set to All Autotask Users show in the outsourced copy of the ticket (Autotask developer help, 6 Nov 2026). Notes are the writes most likely to reach a customer, so they wait for your OK. How your Autotask stays in your hands: - Your own login and MFA, signed in by you - The agent works inside your security level - Notes, ticket changes and time wait for your OK by default - No tool deletes a ticket, note or time entry - You can switch the wait off per tool for a scheduled run ## What happens when Autotask changes? - **12 h** between tests of the Autotask tools - **$0** for a call to an Autotask tool paused for repair When an Autotask screen moves or a field is renamed, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the ticket.** Status, owner and the latest notes, before it writes. 2. **Drafts the change.** A note or field update from the thread, with your own labels. 3. **Waits for your OK.** The change shows up in your Cotlet console first. 4. **Reports the result.** Ticket number, note ID, time of saving. | Action | Undo | |---|---| | Create a ticket | Edit it in Autotask; its rules and notifications may already have run | | Update status, priority, queue or assignee | Set the old value again in Autotask | | Add a note | No automatic undo; a note for All Autotask Users shows in the outsourced copy | | Log a time entry | Edit or delete it in Autotask while it is not posted and the timesheet is unsubmitted | All 4 write tools ask first: create_ticket, update_ticket, add_ticket_note, log_time_entry. Reads reach nobody and run at once. Switch the wait off per tool for a scheduled run. > A new assignee or status can fire Autotask rules and notifications, so check your workflow rules before you switch the wait off. MCP call: ``` { "name": "add_ticket_note", "arguments": { "ticket_id": 48213, "title": "Triage", "body": "Looks like a driver issue after the update. Moving to Service Desk, priority High." } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/autotask/tickets/48213/note \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"title":"Triage","body":"Looks like a driver issue after the update. Moving to Service Desk, priority High."}' ``` Tool output: ``` { "note_id": 90431, "ticket_id": 48213, "title": "Triage", "publish": "Internal", "created": "2026-11-06" } ``` Scripts and cron jobs reach the same tools over REST at `/api/v1/autotask`, with the same key and price. A write over REST waits for your OK too and answers 202 until you approve it. A failed call costs nothing. The tools table lists the REST path of each tool. ## How much does the Autotask MCP server cost? **About $70 a month** for one service coordinator at a small MSP, 12,100 credits. Your Autotask plan is billed by Kaseya as before. | Job | Calls | Credits | |---|---|---| | Triage new tickets, daily | 22 × 22 | 4,840 | | Chase tickets with no recent note, daily | 13 × 22 | 2,860 | | Log time from a daily summary | 8 × 22 | 1,760 | | Tickets from email requests | 3 × 30 | 900 | | Open tickets per company, weekly | 6 × 4 | 240 | | Cloud Browser, 30 days | | 1,500 | | Total | | 12,100 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No Autotask API user or integration code to set up The month is our example: about 10 new tickets a day, 22 working days. Public ticket volumes come from vendor blogs, 800 a month for 5 technicians at Rev.io, so the numbers are our assumption. Dollars at the $29 pack rate. Kaseya publishes no Autotask PSA list price. Its one printed figure is $129 per user per month for the Kaseya 365 Ops bundle with Autotask Ultimate (reported by assigner.ai, 6 Nov 2026). ## Autotask MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [kaseya/mcp-servers](https://github.com/kaseya/mcp-servers) | Kaseya's official early-access servers for Autotask, Datto RMM and IT Glue, with skills. 16 stars, last commit 4 Nov 2026. | Alpha. Claude Desktop and Claude Code only, runs on an API user and integration code. | | [WYRE-AI/autotask-mcp](https://github.com/WYRE-AI/autotask-mcp) | Apache-2.0, TypeScript. 101 tools for companies, contacts, tickets, projects, time entries and notes, per its README. 62 stars, last commit 29 Oct 2026. | You host it and give it an API user and integration code. | | [tegwin/AutotaskMCP](https://github.com/tegwin/AutotaskMCP) | GPL-3.0, Python MCP server. 10 stars, last commit 17 Sep 2026. | You host it, with API credentials. | | [tphakala/autotask-mcp](https://github.com/tphakala/autotask-mcp) | Apache-2.0, Go implementation. 5 stars, last commit 8 Sep 2026. | You host it, with API credentials. | | [Zapier](https://zapier.com/mcp/autotask) | Official Autotask app and a hosted MCP page: create tickets, ticket notes and time entries, find companies and contacts. | Needs a Zapier account and an Autotask API connection. | The official and community servers are good if you are happy to create an API user and run or install one. Cotlet is for the coordinator or technician who wants the same jobs inside ChatGPT or Claude, under their own login, with no API user, no integration code and no server. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Autotask tools. ## Autotask MCP server: questions ### How do I connect Autotask to ChatGPT or Claude? Sign up at cotlet.dev, log in to Autotask once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Autotask account through Cotlet, in their phone apps too. ### What can ChatGPT do in Autotask? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Autotask: triage new unassigned tickets; chase tickets with no recent update; log time from a daily summary. You ask in plain words, and anything that reaches other people waits for your OK first. ### Does Autotask have an official MCP server? Yes, in alpha (checked 6 Nov 2026). Kaseya publishes it in github.com/kaseya/mcp-servers for Claude Desktop and Claude Code. It uses an API user and an integration code. Kaseya calls it early access until OAuth 2.1 support arrives, planned for FY27. ### How do I get access? Create a free account at https://cotlet.dev, open Autotask under Integrations in the console and log in to Autotask in its Cloud Browser. The trial starts with your first app, no card asked. ### Do I need an API user or an integration code? No. Cotlet works in your own Autotask login, so no API-only user and no integration code are needed. Your security level still decides what your agent can see and change. ### Does it work with Claude and ChatGPT in the browser or on my phone? Yes. Cotlet is hosted, so the chat apps reach it by the shared address. Nothing runs on your computer. ### Can I use it without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n or Make with your Cotlet key. The same tools, inputs and price as MCP. ### Is Cotlet affiliated with Autotask? No. Cotlet is independent and not affiliated with Autotask, Datto or Kaseya. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.