Supabase
MCP server for interacting with the Supabase platform
作者提供的说明(英文原文)
Every Tactical RMM endpoint as a typed command, plus an offline SQLite mirror and cross-entity
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TACTICAL_RMM_BASE_URL, TRMM_API_KEY, TACTICAL_RMM_MCP_READ_ONLY, TACTICAL_RMM_NO_LOCAL_DATA, TACTICAL_RMM_USER_AGENT, TACTICAL_RMM_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
运行前请先填写空着的值。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
TACTICAL_RMM_MCP_READ_ONLY envTACTICAL_RMM_NO_LOCAL_DATA envTACTICAL_RMM_USER_AGENT env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 servosity 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TACTICAL_RMM_BASE_URL, TRMM_API_KEY, TACTICAL_RMM_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.8)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Supabase, MongoDB MCP Server, Elasticsearch MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP server for interacting with the Supabase platform
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Unofficial. Community-built Claude Code Skill and MCP server for the Tactical RMM
API. Not affiliated with, endorsed by, or sponsored by AmidaWare LLC.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Tactical RMM endpoint as a typed command, plus an offline SQLite mirror and cross-entity fleet queries the web UI can't express. 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.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Tactical RMM skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register tactical-rmm-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add tactical-rmm-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 tactical-rmm-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs tactical-rmm-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.
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 companiontactical-rmm-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 setTACTICAL_RMM_CLI_PATHto an existing binary). Details: #331.
Download Tactical RMM MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Tactical RMM 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 tactical-rmm@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Tactical RMM 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/tactical-rmm/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/tactical-rmm/install.ps1 | iex. Then authenticate per the README and runtactical-rmm-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/tactical-rmm/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/tactical-rmm/install.sh)
The installer drops both tactical-rmm-cli (the CLI) and tactical-rmm-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
tactical-rmm-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/tactical-rmm/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/tactical-rmm/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 tactical-rmm@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/tactical-rmm --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/tactical-rmm --force
Hermes speaks MCP natively, so it can also use the tactical-rmm-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the tactical-rmm skill from https://github.com/servosity/msp-skills/tree/main/skills/tactical-rmm. The skill defines how its required CLI (
tactical-rmm-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.
Tactical RMM is self-hosted, so point the CLI at your instance and give it an API key from Settings > Global Settings > API Keys:
TACTICAL_RMM_BASE_URL=https://api.yourdomain.com TRMM_API_KEY=<value> tactical-rmm-cli doctor
doctor confirms the base URL and 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 |
|---|---|
| What's the overall health of my fleet right now? | tactical-rmm-cli fleet health |
| Which agents need attention first? | tactical-rmm-cli triage --limit 20 |
| Which agents have gone dark or stopped checking in? | tactical-rmm-cli agents stale --days 7 |
| Where are patches and reboots pending across every client? | tactical-rmm-cli patch posture --by client |
| What changed across the fleet in the last few hours? | tactical-rmm-cli since "2h" |
| Which endpoints have no checks configured (monitoring gaps)? | tactical-rmm-cli coverage |
| Which checks are failing on the most agents? | tactical-rmm-cli checks worst |
| Which agents have a given software package installed? | tactical-rmm-cli software find --name openssl |
| Run a command across a filtered cohort (preview first) | tactical-rmm-cli agents bulk-run --command whoami --filter "os=windows,online=true" |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Tactical RMM 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 many of my 40 clients have machines pending a reboot tonight, across every site" and the answer would page through every endpoint on your server.
This skill syncs Tactical RMM 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 health, triage, and clients scorecard join across agents, checks, alerts, and Windows-update state per client and site - work a stateless API wrapper can't do.
Tactical RMM is the budget-friendly, self-hosted favorite on r/msp and in the MSPGeek community - you own the data and pay nothing per endpoint. The recurring gripe is reporting: the web UI shows you one agent or one client at a time, with no built-in fleet-wide view of health, patch posture, or "what changed overnight" across every client. Everything is in the API, but a cross-client rollup means scripting against it yourself - so the questions that matter at a Monday stand-up or a QBR go unanswered.
This skill closes that gap:
--execute.See pain-point.md for the longer narrative.
Yes, in the **C
只显示了开头部分;其余内容请在仓库中阅读