autotask-mcp

What This Skill Does

The autotask-mcp skill provides a robust, localized interface for interacting with the Kaseya Autotask PSA platform. By deploying an MCP (Model Context Protocol) server via Docker Compose, it enables your OpenClaw agent to perform CRUD operations on essential PSA entities like tickets, companies, contacts, and project tasks without needing a direct integration into the core codebase. This architecture keeps your credentials isolated on your local machine and ensures that all communication with Autotask occurs through a standardized local endpoint.

Installation

To begin, ensure you have Docker installed and running. First, clone the repository and navigate to the directory. Initialize your configuration by running cp .env.example.txt .env and chmod 600 .env. You must manually open the .env file in your system editor to input your AUTOTASK_INTEGRATION_CODE, AUTOTASK_USERNAME, and AUTOTASK_SECRET. Once configured, execute ./scripts/mcp_pull.sh to fetch the latest Docker image, followed by ./scripts/mcp_up.sh to start the service. You can verify the operational status by running curl -sS http://localhost:8080/health. For long-term maintenance, the tool includes helper scripts for updating images and configuring automatic weekly maintenance tasks.

Use Cases

This skill is perfect for MSPs (Managed Service Providers) looking to automate administrative tasks. Use it to automatically query pending tickets, sync project statuses, create new time entries after completing a task, or update customer contact information during a support session. Because it is an MCP server, it creates a stable bridge for any agent-based workflow that requires real-time synchronization between Autotask PSA and other external data sources or local system processes.

Example Prompts

1. "List all high-priority tickets currently assigned to me in Autotask and provide a summary of the pending work items."
2. "Create a new time entry for ticket #12345, recording 30 minutes for 'Investigation and root cause analysis'."
3. "Update the status of company profile for 'Acme Corp' to verify their current service agreement details."

Tips & Limitations

Security is paramount: never share, log, or display your .env file contents in chat. The agent is strictly prohibited from accessing your credentials directly. Always prefer the provided shell scripts for operations. If the service becomes unreachable, use ./scripts/mcp_logs.sh to inspect container health or check for authentication errors. Note that the agent cannot edit the .env file itself; if credentials rotate, you must manually update them in your local file system.