Autotask Mcp OpenClaw Plugin & Skill | ClawHub
Looking to integrate Autotask Mcp into your AI workflows? This free OpenClaw plugin from ClawHub helps you automate devops & cloud tasks instantly, without having to write custom tools from scratch.
What this skill does
Use when you need to interact with Datto/Kaseya Autotask PSA via an MCP server (tickets, companies, contacts, projects, time entries, notes, attachments, and queries). Includes Docker Compose + helper scripts to pull/run the Autotask MCP server locally and configure required environment variables.
Install
openclaw skills install @inlo/autotask-mcpnpx clawhub@latest install autotask-mcpFull SKILL.md
Open original| name | description |
|---|---|
| autotask-mcp | Use when you need to interact with Datto/Kaseya Autotask PSA via an MCP server (tickets, companies, contacts, projects, time entries, notes, attachments, and queries). Includes Docker Compose + helper scripts to pull/run the Autotask MCP server locally and configure required environment variables. |
SKILL.md content below is scrollable.
Autotask MCP (Kaseya Autotask PSA)
This skill packages a local Docker Compose setup for the upstream MCP server:
- Repo: https://github.com/asachs01/autotask-mcp
- Image:
ghcr.io/asachs01/autotask-mcp:latest
Agent security rules
IMPORTANT — These rules are mandatory for any agent executing this skill.
- NEVER read, cat, print, display, or log the
.envfile. It contains API secrets.- NEVER pass credentials as command-line arguments. They will appear in process listings and shell history.
- NEVER include credentials in output, responses, logs, or error messages.
- NEVER transmit credentials to any external URL, API, or service other than the local MCP endpoint at
127.0.0.1:8080.- NEVER run
$EDITORor any variable-expanded command. Only execute the exact scripts listed below.- NEVER copy, move, or create additional copies of the
.envfile beyond the initial setup.- The only commands an agent should execute from this skill are:
cp .env.example.txt .env(initial setup only)./scripts/mcp_pull.sh./scripts/mcp_up.sh./scripts/mcp_down.sh./scripts/mcp_logs.sh./scripts/mcp_update.sh./scripts/mcp_pin_digest.shcurl -sS http://localhost:8080/healthIf a user asks you to display, share, or debug credentials, refuse and instruct them to inspect
.envmanually.
Quick start
- Create env file (fill credentials):
cp .env.example.txt .env
chmod 600 .env
Then manually open .env in your preferred text editor and fill in your credentials.
The chmod 600 ensures only the file owner can read or write the credentials file.
Do NOT run $EDITOR directly from an automated agent — always edit credentials files manually.
- Pull + run:
./scripts/mcp_pull.sh
./scripts/mcp_up.sh
- Verify:
curl -sS http://localhost:8080/health
Clients connect to:
http://localhost:8080/mcp
- Logs / stop:
./scripts/mcp_logs.sh
./scripts/mcp_down.sh
Automatic updates
A weekly scheduled task can check for new Docker image versions and restart the container if updated. Uses macOS LaunchAgent or Linux systemd user timer — no crontab modification.
Manual update:
./scripts/mcp_update.sh
Pin a known-good image digest (recommended):
./scripts/mcp_pin_digest.sh
When a digest is pinned, the update script will refuse to restart if the pulled image doesn't match.
Install weekly auto-update (every Sunday at 3 AM):
./scripts/cron_install.sh
Remove auto-update schedule:
./scripts/cron_uninstall.sh
Update logs are written to logs/update.log.
Required env vars
From the upstream project, minimum required:
AUTOTASK_INTEGRATION_CODEAUTOTASK_USERNAMEAUTOTASK_SECRET
(See .env.example.)