Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
Every Huntress endpoint, plus a local SQLite mirror that delivers fleet-wide incident, coverage
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PRINTING_PRESS_CLIENT_PROFILE, HUNTRESS_API_KEY, HUNTRESS_API_SECRET, HUNTRESS_BASE_URL, HUNTRESS_MCP_READ_ONLY, HUNTRESS_NO_LOCAL_DATA, HUNTRESS_USER_AGENT, HUNTRESS_MCP_HTTP_TOKENValues 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.
HUNTRESS_BASE_URL envHUNTRESS_MCP_READ_ONLY envHUNTRESS_NO_LOCAL_DATA envHUNTRESS_USER_AGENT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: PRINTING_PRESS_CLIENT_PROFILE, HUNTRESS_API_KEY, HUNTRESS_API_SECRET, HUNTRESS_MCP_HTTP_TOKEN
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).
The GitHub repo last changed –, and the latest version (0.1.12) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
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
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
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.
Unofficial. Community-built Claude Code Skill and MCP server for the Huntress
API. Not affiliated with, endorsed by, or sponsored by Huntress Labs, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Huntress endpoint, plus a local SQLite mirror that delivers fleet-wide incident, coverage, and billing rollups the API and official MCP can't. 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.
Security note. Local agents use the default stdio transport and need no
network listener. HTTP mode (
--transport http, for remote agents) refuses to
start until
HUNTRESS_MCP_HTTP_TOKENis set, rejects any request without that
bearer token, serves
http://127.0.0.1:7777/mcpby default, and needs--tls-cert
and
--tls-keyfor any other address. It refuses a request body over 4 MiB or
one that takes longer than 30 seconds to arrive. Whoever holds the token can
call every tool with your Huntress credentials, including tools that change
your tenant, so treat it like a password, and set
HUNTRESS_MCP_READ_ONLY=1on
a remote host that only needs to read. See mcp-install.md.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Huntress skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register huntress-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add huntress-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 huntress-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs huntress-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support 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. Setup steps: mcp-install.md.
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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionhuntress-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 setHUNTRESS_CLI_PATHto an existing binary). Details: #331.
Download Huntress MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Huntress 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 huntress@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Huntress 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/huntress/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/huntress/install.ps1 | iex. Then authenticate per the README and runhuntress-cli --helpto explore.
The same prompt works in any agent that can run shell.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/huntress/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/huntress/install.sh)
The installer drops both huntress-cli (the CLI) and huntress-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
huntress-cli --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/huntress/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/huntress/install.ps1 | iex
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update huntress@msp-skills.
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.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/huntress --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/huntress --force
Hermes speaks MCP natively, so it can also use the huntress-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the huntress skill from https://github.com/servosity/msp-skills/tree/main/skills/huntress. The skill defines how its required CLI (
huntress-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.
Set the credentials the CLI needs (from your Huntress portal):
HUNTRESS_API_KEY=<value> HUNTRESS_API_SECRET=<value> huntress-cli doctor
doctor 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.
| Question your MSP keeps asking | Command |
|---|---|
| Which incidents are oldest across every client org? | huntress-cli fleet-incidents --sort age |
| Where are my posture gaps - stale callbacks, disabled Defender or firewall? | huntress-cli coverage-gaps |
| Has this IP or file hash touched any of my clients? | huntress-cli blast-radius --indicator 203.0.113.10 |
| Am I billed for more seats than I have agents deployed? | huntress-cli billing-reconcile |
| Which agents went dark in the last week? | huntress-cli stale-agents --days 7 |
| What is my mean time-to-resolve per client? | huntress-cli mttr --group-by org |
| What changed across the fleet since my last shift? | huntress-cli handoff --since 12h |
| Give me a QBR scorecard for one client. | huntress-cli org-scorecard --org 12345 |
| Which detection types did the SOC report where this week? | huntress-cli signal-digest --since 7d |
| Which escalations are still unresolved, critical first? | huntress-cli escalation-queue --severity critical |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Huntress 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 "which incident is oldest across all 40 of my client organizations right now?" or "did this attacker IP touch any other tenant?" - the portal answers one org at a time and the API offers no single query for it.
This skill syncs Huntress 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 fleet-incidents, blast-radius, and billing-reconcile join across incident reports, agents, external ports, and invoices from every organization at once - work a stateless API wrapper can't do.
On r/msp, the recurring Huntress complaint from multi-tenant shops is that the dashboard has no native cross-client incident queue, no fleet-wide posture rollup, and no built-in reconciliation of invoiced seats against deployed agents. The API does list agents and incident reports across the whole account, but the incident list returns only the first 10 remediations per incident and the account-wide limit is 60 requests per minute. At 20, 40, 80 client tenants, "which fire do I put out first?" becomes a tab-switching exercise, and billing drift is caught by hand at month-end.
This skill closes that gap:
Only the beginning is shown; read the rest in the repo