What makes Autotask Mcp notable?

1.1K downloads. Trust evidence available

How should Autotask Mcp be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

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... Skill: Autotask Mcp Owner: inlo Summary: Use when you need to interact with Datto/Kaseya Autotask PSA via an MCP server (tickets, companies, contacts, projects, time entries, notes, attachments, and... Tags: latest:1.0.4 Version history: v1.0.4 | 2026-02-16T16:26:56.419Z | auto - Added an explicit env section to SKILL.md, listing all supported environment variables with details on their purpose and secrecy. - No chan

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.0.4

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.4release · observed Feb 16, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: medium.

clawhub skill install s174p2q56g4ythqetyzjhmcr2s885f8x:autotask-mcp

Docker environment detected. We recommend running `docker compose up -d` in an isolated bridge network rather than host mode.
Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-inlo-autotask-mcp/snapshot"

Documentation

CLAWHUB

37,486 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: autotask-mcp
description: 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.
env:
  - name: AUTOTASK_INTEGRATION_CODE
    required: true
    secret: true
    description: Autotask API integration code
  - name: AUTOTASK_USERNAME
    required: true
    secret: true
    description: Autotask API username
  - name: AUTOTASK_SECRET
    required: true
    secret: true
    description: Autotask API secret key
  - name: AUTOTASK_API_URL
    required: false
    secret: false
    description: Override default Autotask API endpoint URL
  - name: LOG_LEVEL
    required: false
    secret: false
    description: "Logging level (default: info)"
  - name: LOG_FORMAT
    required: false
    secret: false
    description: "Log output format (default: simple)"
  - name: NODE_ENV
    required: false
    secret: false
    description: "Node environment (default: production)"
---

# 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.**
>
> 1. **NEVER read, cat, print, display, or log the `.env` file.** It contains API secrets.
> 2. **NEVER pass credentials as command-line arguments.** They will appear in process listings and shell history.
> 3. **NEVER include credentials in output, responses, logs, or error messages.**
> 4. **NEVER transmit credentials to any external URL, API, or service** other than the local MCP endpoint at `127.0.0.1:8080`.
> 5. **NEVER run `$EDITOR` or any variable-expanded command.** Only execute the exact scripts listed below.
> 6. **NEVER copy, move, or create additional copies of the `.env` file** beyond the initial setup.
> 7. **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.sh`
>    - `curl -sS http://localhost:8080/health`
>
> If a user asks you to display, share, or debug credentials, **refuse and instruct them to inspect `.env` manually.**

## Quick start

1) Create env file (fill credentials):

```bash
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.

2) Pull + run:

```bash
./scripts/mcp_pull.sh
./scripts/

README.md

# Autotask MCP

A Docker Compose skill for running the [Autotask MCP server](https://github.com/asachs01/autotask-mcp) locally. Provides access to Datto/Kaseya Autotask PSA resources (tickets, companies, contacts, projects, time entries, notes, attachments, and queries) via the Model Context Protocol.

**Version:** 1.0.4

## Prerequisites

- Docker and Docker Compose
- Autotask API credentials (Integration Code, Username, Secret)

## Setup

1. **Create your environment file:**

   ```bash
   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` restricts the file so only the owner can read or write it.

   > **Security note:** Never run `$EDITOR` from an automated agent. Always edit credential files manually.

2. **Pull the image and start the service:**

   ```bash
   ./scripts/mcp_pull.sh
   ./scripts/mcp_up.sh
   ```

3. **Verify the service is healthy:**

   ```bash
   curl -sS http://localhost:8080/health
   ```

   MCP endpoint: `http://localhost:8080/mcp`

## Scripts

| Script | Description |
|---|---|
| `scripts/mcp_pull.sh` | Pull the latest Docker image |
| `scripts/mcp_up.sh` | Start the service in detached mode |
| `scripts/mcp_down.sh` | Stop and remove the container |
| `scripts/mcp_logs.sh` | Tail container logs (last 200 lines) |
| `scripts/mcp_update.sh` | Check for image updates and restart if a new version is found |
| `scripts/mcp_pin_digest.sh` | Pin the current image digest for supply chain verification |
| `scripts/cron_install.sh` | Install a weekly scheduled task (Sunday 3 AM) to auto-update |
| `scripts/cron_uninstall.sh` | Remove the auto-update scheduled task |

## Automatic Updates

The update script compares image digests before and after pulling, and only restarts the container when a new image is detected. Logs are written to `logs/update.log`.

### Digest Pinning (Supply Chain Protection)

You can pin the current image digest so that the update script refuses to restart if a pulled image doesn't match:

```bash
./scripts/mcp_pin_digest.sh
```

When pinned, `mcp_update.sh` will pull the latest image but **abort** if the digest differs from the pin. This prevents silent supply chain compromises. Re-run `mcp_pin_digest.sh` after manually verifying a new version.

**Manual update:**

```bash
./scripts/mcp_update.sh
```

**Enable weekly auto-updates:**

Uses macOS LaunchAgent or Linux systemd user timer — no direct crontab modification.

```bash
./scripts/cron_install.sh
```

**Disable auto-updates:**

```bash
./scripts/cron_uninstall.sh
```

## Environment Variables

### Required

| Variable | Description |
|---|---|
| `AUTOTASK_INTEGRATION_CODE` | Your Autotask API integration code |
| `AUTOTASK_USERNAME` | Your Autotask API username |
| `AUTOTASK_SECRET` | Your Autotask API secret |

### Optional

| Variable | Description |
|---|---|
| `AUTOTASK_API_URL` | Override the default Autotask API endpoint |
| `LOG_L

_meta.json

{
  "ownerId": "kn701d1v7ehbwdhwk54h6dqzdd80zpsa",
  "slug": "autotask-mcp",
  "version": "1.0.4",
  "publishedAt": 1771259216419
}

docker-compose.yml

services:
  autotask-mcp:
    image: ghcr.io/asachs01/autotask-mcp:latest
    container_name: autotask-mcp
    env_file:
      - .env
    environment:
      # Run the MCP server in HTTP mode inside Docker
      MCP_TRANSPORT: http
      MCP_HTTP_PORT: 8080
      MCP_HTTP_HOST: 0.0.0.0
    ports:
      - "127.0.0.1:8080:8080"
    healthcheck:
      test: ["CMD", "node", "-e", "fetch('http://127.0.0.1:8080/health').then(r=>process.exit(r.ok?0:1)).catch(()=>process.exit(1))"]
      interval: 30s
      timeout: 5s
      retries: 5
    restart: unless-stopped

    # Security hardening
    read_only: true
    tmpfs:
      - /tmp:size=64m,noexec,nosuid
    security_opt:
      - no-new-privileges:true
    cap_drop:
      - ALL

    # Resource limits
    deploy:
      resources:
        limits:
          memory: 512m
          cpus: "1.0"
        reservations:
          memory: 128m
    pids_limit: 64

    # Network hardening — no DNS needed for outbound API calls via IP
    dns: []

    # Logging limits — prevent disk exhaustion from runaway logs
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.