Log inSubmit server
Autotask logo

Autotask

Connects AI assistants to Kaseya Autotask PSA for ticketing, companies, projects, billing, contracts, and time tracking.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Autotask

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "autotask-2": {
      "command": "npx",
      "args": [
        "-y",
        "github:WYRE-AI/autotask-mcp"
      ],
      "env": {
        "AUTOTASK_USERNAME": "YOUR_VALUE_HERE",
        "AUTOTASK_SECRET": "YOUR_VALUE_HERE",
        "AUTOTASK_INTEGRATION_CODE": "YOUR_VALUE_HERE",
        "CONDUIT_S2S_SECRET": "YOUR_VALUE_HERE",
        "AUTH_MODE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Autotask MCP server connects MCP-compatible clients to a Kaseya Autotask PSA environment through search, retrieval, creation, and update tools. It covers tickets, companies, contacts, projects, tasks, resources, time entries, billing items, contracts, invoices, opportunities, assets, notes, and attachments. Use it when an assistant needs to look up service data or perform operational updates without switching to the Autotask interface. Local stdio and remote Streamable HTTP transports are supported, with gateway authentication available for hosted deployments.

Use cases

  • Triage tickets using status, priority, queue, company, or assignee filters
  • Create companies, contacts, tickets, projects, and project tasks
  • Log and review technician time entries
  • Review billing items, invoices, contracts, and expiring agreements
  • Inspect ticket notes, custom fields, assets, and attachments

Key features

  • Filtered searches across Autotask PSA entities
  • Ticket details with notes, UDFs, assets, and attachments
  • Create and update operations for core records
  • Local stdio and remote Streamable HTTP transports
  • Gateway authentication with request-injected credentials
  • Automatic company and resource ID-to-name mapping

Tools30

What Autotask lets your agent do. Expand a tool for its parameters.

Self-reported~518 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · github:WYRE-AI/autotask-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars58Stargazers on the source repository.
Last commit2d agoMost recent push to the default branch.
Tools exposed30Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Autotask works

What Autotask MCP server does

Autotask MCP server exposes Autotask PSA operations as MCP tools for support and service-management workflows. It can search records with filters, retrieve detailed records, and create or update selected entities. The available coverage includes companies, contacts, tickets, projects, project tasks, resources, time entries, billing items, invoices, contracts, opportunities, configuration items, and ticket-related attachments.

Ticket work includes filtered searches, ticket creation, detailed retrieval, and access to notes, custom fields, linked configuration items, assignment data, status, priority, queue, resolution, and dates. Time-entry searches can filter by resource, ticket, task, or date range, while returned entries include summary and internal notes. Contract tools support searches, individual retrieval, expiration reporting, and end-date updates.

How it works

The server communicates with Autotask using an API username, secret, and integration code. It can run locally over stdio or as an HTTP service using MCP Streamable HTTP. In gateway mode, a deployment receives the Autotask credentials through request headers instead of static environment variables; an optional impersonation resource ID can identify the resource on whose behalf requests run.

Search tools accept entity-specific filters and return Autotask records. The server also resolves company and resource IDs to readable names and uses caching to reduce repeated API calls. autotask_test_connection provides a way to check API connectivity. In MCP Apps hosts such as Claude Desktop or Claude web, ticket details can render as an interactive card with an in-card add-note action; other hosts receive the ticket data as assistant-readable text and JSON.

Setup and configuration

Claude Desktop users can install the released .mcpb bundle, open it, and enter the Autotask username, secret, and integration code. Claude Code can register the server with claude mcp add and pass those values as environment variables. Source installation requires Node.js 18 or newer, followed by npm ci and npm run build.

Docker supports both local stdio and remote HTTP deployments. An HTTP deployment requires CONDUIT_S2S_SECRET; clients connect to /mcp and send the corresponding X-Gateway-S2S header. The health endpoint is available at /health. Gateway mode uses AUTH_MODE=gateway and expects X-API-Key, X-API-Secret, and X-Integration-Code headers on MCP requests.

Tools and capabilities

  • Search companies, contacts, tickets, projects, tasks, resources, invoices, contracts, configuration items, time entries, billing items, approval records, and attachments.
  • Create companies, contacts, tickets, time entries, projects, and project tasks.
  • Update companies, opportunities, and contracts.
  • Retrieve ticket details, billing items, contracts, ticket attachments, and ticket-note attachments.
  • Review expiring or expired contracts across a company or the wider organization.
  • Inspect ticket custom fields, notes, linked assets, assignment data, and complete untruncated records.

Limitations and notes

Autotask API credentials are required for normal operation. The HTTP transport requires service-to-service authentication in addition to Autotask credentials, while gateway mode expects credentials on each request. The interactive ticket card is available in MCP Apps hosts; other clients use the textual and structured ticket response.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Autotask

Autotask is an MCP server that connects AI assistants to Kaseya Autotask PSA. Its main tools search, retrieve, create, and update companies, contacts, tickets, projects, time entries, billing records, contracts, invoices, assets, and attachments, allowing MCP-compatible clients to perform service-management work through natural-language requests.

Install it through the released MCPB bundle, Claude Code, Docker, or from source. The bundle requires opening the file in Claude Desktop and entering Autotask credentials. Source installation requires Node.js 18 or newer, followed by npm ci and npm run build.

The server requires an Autotask API username, secret, and integration code. Local and standard Docker configurations provide these as AUTOTASK_USERNAME, AUTOTASK_SECRET, and AUTOTASK_INTEGRATION_CODE. Gateway deployments instead receive the three values through HTTP headers.

Yes, Autotask supports Claude Desktop through the downloadable MCPB bundle or a local stdio configuration. Claude Desktop can also render the ticket-details interactive card, including its in-card add-note action.

Yes, Docker can run Autotask with MCP Streamable HTTP. The deployment exposes the MCP endpoint on port 8080, requires CONDUIT_S2S_SECRET, and authenticates MCP requests with X-Gateway-S2S. Gateway mode can inject Autotask credentials through request headers.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAutotask AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/autotask-2?style=directory)](https://allmcps.com/mcp/autotask-2)
HTML Embed
<a href="https://allmcps.com/mcp/autotask-2"><img src="https://allmcps.com/api/badge/autotask-2?style=directory" alt="Autotask on AllMCPs" /></a>