autotask

Autotask MCP Server provides a structured MCP interface to access Kaseya Autotask PSA data and operations. It exposes a suite of tools that cover core entities such as companies, contacts, tickets, projects, billing items, time entries, notes, and attachments, with CRUD capabilities and advanced search. The server also includes id-to-name resolution, smart caching for performance, and supports both local stdio transport and HTTP streamable transport for remote deployments. To use it, configure credentials and transport, then run the server so that your MCP client (e.g., Claude Desktop or Claude Code) can connect to the MCP endpoint and issue MCP requests to manage Autotask data via the provided tools.

• Prerequisites:
  • Node.js 18+ installed on your machine
  • npm (comes with Node.js) or pnpm
  • Autotask API credentials (username/email, secret, integration code)
  • Access to the MCP client you plan to use (Claude Desktop/Claude Code or compatible MCP client)

1. Clone the repository and install dependencies:

git clone https://github.com/wyre-technology/autotask-mcp.git
cd autotask-mcp
npm ci

2. Build the project (if you are running from source):

npm run build

3. Run or configure the MCP server using the Node.js entry (example config shown in mcp_config):

{
  "mcpServers": {
    "autotask": {
      "command": "node",
      "args": ["/path/to/autotask-mcp/dist/entry.js"],
      "env": {
        "AUTOTASK_USERNAME": "your-user@company.com",
        "AUTOTASK_SECRET": "your-secret",
        "AUTOTASK_INTEGRATION_CODE": "your-code"
      }
    }
  }
}

4. Alternative deployment (Docker): follow the README’s Docker options to run in stdio or HTTP transports, if you prefer containerized deployment. Ensure you supply the same AUTOTASK_* environment variables when starting the container.

• The server supports multiple transport modes: stdio for local desktop usage and HTTP streamable transport for remote deployments behind a gateway or in Docker.
• In gateway mode, credentials can be injected by a gateway, so you may set AUTH_MODE=gateway and MCP_TRANSPORT=http, with credentials passed via HTTP headers.
• Ensure MCP client configuration points at the correct transport endpoint (e.g., dist/entry.js for node-based from-source setup, or the HTTP endpoint when using Docker).
• Use the provided environment variables to keep credentials out of your codebase; consider using a secrets manager in production.
• If you experience connection or authentication issues, verify that AUTOTASK_API_URL (if overridden) is reachable and that the Autotask credentials are valid.
• The server exposes 39+ tools and comprehensive API coverage; consult the API Reference section in the README for details on specific resources and operations.