# Autotask [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/WYRE-AI/autotask-mcp  
**GitHub Stars:** 58  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/autotask-2

## Description
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.

## Tools
Capabilities this server exposes over MCP:

- **autotask_search_companies** — Search companies with filters
- **autotask_create_company** — Create new company
- **autotask_update_company** — Update existing company
- **autotask_search_contacts** — Search contacts with filters
- **autotask_create_contact** — Create new contact
- **autotask_search_tickets** — Search tickets with filters
- **autotask_get_ticket_details** — Get a ticket by ID: description, status/priority/queue, company, contact, assignee, dates, linked configuration item, resolution, custom fields (UDFs), recent notes and the full record (`fullDetails: true` for untruncated text and all UDFs)
- **autotask_create_ticket** — Create new ticket
- **autotask_create_time_entry** — Log time entry
- **autotask_search_time_entries** — Search time entries with filters (resource, ticket, task, date range); each entry includes `summaryNotes` and `internalNotes`
- **autotask_search_billing_items** — Search approved and posted billing items
- **autotask_get_billing_item** — Get specific billing item by ID
- **autotask_search_billing_item_approval_levels** — Search multi-level approval records for time entries
- **autotask_search_projects** — Search projects with filters
- **autotask_create_project** — Create new project
- **autotask_search_resources** — Search resources (technicians/users)
- **autotask_get_ticket_attachment** — Get ticket attachment
- **autotask_search_ticket_attachments** — Search ticket attachments
- **autotask_get_ticket_note_attachment** — Get an attachment on a ticket note (e.g. a pasted screenshot)
- **autotask_search_ticket_note_attachments** — Search attachments on a ticket note
- **autotask_update_opportunity** — Update an opportunity (stage, status, revenue/cost lines, UDFs)
- **autotask_search_invoices** — Search invoices
- **autotask_search_contracts** — Search contracts (name, company, status, type, end-date range)
- **autotask_get_contract** — Get a single contract by ID
- **autotask_list_expiring_contracts** — Expiring/expired contracts report (next N days, per company or org-wide)
- **autotask_update_contract** — Update a contract (e.g. extend/renew end date)
- **autotask_search_configuration_items** — Search configuration items (assets)
- **autotask_search_tasks** — Search project tasks
- **autotask_create_task** — Create project task
- **autotask_test_connection** — Test API connectivity

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "autotask": {
    "command": "npx",
    "args": ["-y","github:WYRE-AI/autotask-mcp"],
    "env": {
      "AUTOTASK_USERNAME": "",
      "AUTOTASK_SECRET": "",
      "AUTOTASK_INTEGRATION_CODE": "",
      "CONDUIT_S2S_SECRET": "",
      "AUTH_MODE": ""
    }
  }
}
```

**Requires environment variables:** `AUTOTASK_USERNAME`, `AUTOTASK_SECRET`, `AUTOTASK_INTEGRATION_CODE`, `CONDUIT_S2S_SECRET`, `AUTH_MODE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/autotask-2/readme_