Supabase
by supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Computer or cloud★ 2,993Apache-2.0Updated today
Install
Autotask MCP
Overview
Description from the maker (original English)
Every Autotask entity at the command line, plus a local SQLite mirror that answers ticket-aging
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Databases & datasets
- You need to fill in: AUTOTASK_API_INTEGRATION_CODE, AUTOTASK_PSA_SECRET, AUTOTASK_PSA_USER_NAME, AUTOTASK_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
AUTOTASK_API_INTEGRATION_CODE,AUTOTASK_BASE_URL,AUTOTASK_PSA_SECRET,AUTOTASK_PSA_USER_NAME,AUTOTASK_MCP_READ_ONLY,AUTOTASK_NO_LOCAL_DATA,AUTOTASK_MCP_HTTP_TOKEN,AUTOTASK_USER_AGENT,PRINTING_PRESS_CLIENT_PROFILE
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Sets AUTOTASK_API_INTEGRATION_CODE for the Autotask PSA MCP server.
AUTOTASK_BASE_URLenvBase URL for the Autotask PSA API. Leave the prefilled default unless your account uses a different regional or self-hosted host.- Set the AUTOTASK_PSA_SECRET credential for the Autotask MCP server.
- Set the AUTOTASK_PSA_USER_NAME credential for the Autotask MCP server.
AUTOTASK_MCP_READ_ONLYenvOptional. Set to exactly 1 to expose only read-only tools and refuse any tool that changes Autotask. Leave blank to keep every tool (each write still previews and acts only with confirm: true).AUTOTASK_NO_LOCAL_DATAenvOptional. Set to 1 to keep no local copy of API responses: reads go to the API and sync refuses to run. Leave blank to keep the local store.- Required only when running the MCP server with --transport http (a remote/hosted deployment). Callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transpo…
AUTOTASK_USER_AGENTenvOverrides the User-Agent the CLI sends on Autotask requests. Leave blank to use the CLI's own built-in User-Agent.- Only for tenant-gated multi-client deployments: binds the MCP server to an existing Printing Press client profile. Leave blank for a single-tenant install.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Databases & datasetsi
- More stars than 0% of the other 953 servers in this category
- Published to the registry more recently than 98% of the other 953 servers in this category
- Basic checks equal to or better than 100% of the other 953 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Autotask MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: AUTOTASK_API_INTEGRATION_CODE, AUTOTASK_PSA_SECRET, AUTOTASK_PSA_USER_NAME, AUTOTASK_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.10) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MongoDB MCP Server
by mongodb-js
MongoDB Model Context Protocol Server
Runs on your computer★ 1,157Apache-2.0Updated 2 days ago
Install
Elasticsearch MCP Server
by cr7258
MCP server for interacting with Elasticsearch
Runs on your computer★ 315Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Autotask + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the Autotask
API. Not affiliated with, endorsed by, or sponsored by Datto, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Autotask entity at the command line, plus a local SQLite mirror that answers ticket-aging, workload, unbilled-time, and account-360 questions no other Autotask tool can. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Works with your agent
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build has no password,
listens on every network interface, and predates the browser-rebinding guard,
so a web page you open can reach it. The MCP tools can also make changes with
your credentials. Use the default stdio transport. If you set up a tunnel for
a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Autotask skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register autotask-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add autotask-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add autotask-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs autotask-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Also for the Microsoft and Google stacks
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Claude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionautotask-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setAUTOTASK_CLI_PATHto an existing binary). Details: #331.
Download Autotask MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Autotask release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills/plugin install autotask@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Autotask Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/autotask/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/autotask/install.ps1 | iex. Then authenticate per the README and runautotask-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/autotask/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/autotask/install.sh)The installer drops both autotask-cli (the CLI) and autotask-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
autotask-cli --versionUpgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/autotask/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/autotask/install.ps1 | iexClaude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update autotask@msp-skills.
Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
Install for Hermes
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/autotask --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/autotask --forceHermes speaks MCP natively, so it can also use the autotask-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the autotask skill from https://github.com/servosity/msp-skills/tree/main/skills/autotask. The skill defines how its required CLI (
autotask-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Set the credentials the CLI needs (from your Autotask portal):
AUTOTASK_API_INTEGRATION_CODE=<value> AUTOTASK_PSA_SECRET=<value> AUTOTASK_PSA_USER_NAME=<value> autotask-cli doctordoctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
What this skill does
| Question your MSP keeps asking | Command |
|---|---|
| Which approved time entries haven't been invoiced yet? | autotask-cli unbilled |
| How stale is the service desk right now, bucketed by age? | autotask-cli ticket-aging |
| Which open tickets has nobody touched in a week? | autotask-cli stale --days 7 |
| Which unassigned tickets should the dispatcher pick up first? | autotask-cli triage |
| Who's overloaded before I assign the next ticket? | autotask-cli workload |
| How burned are our block-hour contracts, and when do they run out? | autotask-cli retainer |
| Everything we know about one company at once? | autotask-cli company-360 "1234" |
| The month-end billing picture in one table? | autotask-cli reconcile |
| What's the label-to-ID map for a picklist field? | autotask-cli picklist "Tickets" "status" |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Most Autotask integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "how much approved time is unbilled across every client this month" or "which retainers run out before the next renewal" - each one a multi-call dance against a per-tenant zone URL, every categorical filter gated by integer picklist IDs that vary per instance, and all of it spending your hourly API request budget.
This skill syncs Autotask into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like reconcile, retainer, and company-360 join across tickets, time entries, contracts, invoices, and resources - work a stateless API wrapper can't do.
The pain this closes
Ask any MSP owner where Autotask hurts and you get two answers: time that never gets billed, and reporting that means an export. Techs close tickets without entering time, or approved hours never make it onto an invoice, and nobody catches it until the billing run - because Autotask has no single screen joining approved time to the invoices it belongs on. And when you want the cross-object picture, Autotask's native LiveReports is a copy-and-edit report designer that outputs to Excel, PDF, RTF, or CSV (per Kaseya's own Autotask PSA reporting help) - so anything joining tickets to time to contracts gets pushed into Power BI or another BI tool. An entire third-party connector market exists for exactly that.
This skill answers those questions where the data already lives - one offline query, no report build, no spreadsheet:
| The pain | The command |
|---|
| Approved hours quietly falling off invoices | `autotask-c
Only the beginning is shown; read the rest in the repo