Supabase
MCP server for interacting with the Supabase platform
Descripción del creador (original en inglés)
Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
DOMOTZ_API_KEY, DOMOTZ_BASE_URL, DOMOTZ_REGION, DOMOTZ_MCP_READ_ONLY, DOMOTZ_NO_LOCAL_DATA, DOMOTZ_USER_AGENT, DOMOTZ_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILELos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
DOMOTZ_BASE_URL envDOMOTZ_REGION envDOMOTZ_MCP_READ_ONLY envDOMOTZ_NO_LOCAL_DATA envDOMOTZ_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: DOMOTZ_API_KEY, DOMOTZ_MCP_HTTP_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.8) llegó al registro hoy.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP server for interacting with the Supabase platform
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Unofficial. Community-built Claude Code Skill and MCP server for the Domotz
API. Not affiliated with, endorsed by, or sponsored by Domotz Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions. 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 Domotz skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register domotz-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add domotz-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 domotz-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs domotz-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 companiondomotz-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 setDOMOTZ_CLI_PATHto an existing binary). Details: #331.
Download Domotz MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Domotz 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 domotz@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Domotz 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/domotz/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.ps1 | iex. Then authenticate per the README and rundomotz-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/domotz/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.sh)
The installer drops both domotz-cli (the CLI) and domotz-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
domotz-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/domotz/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/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 domotz@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/domotz --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/domotz --force
Hermes speaks MCP natively, so it can also use the domotz-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the domotz skill from https://github.com/servosity/msp-skills/tree/main/skills/domotz. The skill defines how its required CLI (
domotz-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 Domotz portal):
DOMOTZ_API_KEY=<value> DOMOTZ_REGION=<value> domotz-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 |
|---|---|
| Is anything on fire across all my sites? | domotz-cli fleet health --agent |
| Which Collectors (sites) are offline or degraded right now? | domotz-cli fleet agents --agent |
| What devices are offline across every client? | domotz-cli fleet offline --agent |
| What new devices appeared on any network in the last day? | domotz-cli fleet new --since 24h --agent |
| Give me one asset inventory across every site | domotz-cli fleet inventory --csv |
| Where are IP conflicts across the fleet? | domotz-cli fleet ip-conflicts --agent |
| Which devices can't be fully monitored (auth/SNMP gaps)? | domotz-cli fleet unmonitored --agent |
| Which important devices could go down with nobody alerted? | domotz-cli fleet unalerted --vital-only --agent |
| How many devices of each vendor do we manage? | domotz-cli fleet breakdown --by vendor --agent |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Domotz integrations and MCP servers proxy each question into a live, agent-scoped API call. That's fine for one device. It dies at scale, when you're asking "which of my 40 client sites has a device offline right now?" or "give me one asset inventory across every Collector for the QBR."
This skill syncs Domotz into a local SQLite mirror with full-text search. Aggregate questions become one local query: instant, offline, and the AI sees the answer, not raw pages of JSON. Compound commands like fleet health, fleet inventory, and fleet new roll up across every Collector, device, and site at once - work a stateless API wrapper can't do in one call.
Network-monitoring threads on r/msp keep surfacing the same gap with per-site tools: visibility is organized one Collector at a time, but the questions you actually ask are fleet-wide. "Which client has something down?" "What appeared on a network overnight?" "Give me one asset list for the QBR." In the portal each of those means clicking through every site by hand or exporting per-site and merging spreadsheets - the data is all there, it just doesn't roll up across clients in a single view.
This skill closes that gap:
See pain-point.md for the longer narrative.
Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way domotz-mcp runs, and shares MCP configuration with Codex (OpenAI): add domotz-mcp under Settings > MCP servers as a STDIO server, or add it once to Codex's ~/.codex/config.toml. ChatGPT on the web is not supported by msp-skills yet: it needs a remote server. If your team works there, a [hosted gateway](https://msp-skills.compoundingteams.com/answers/mcp-servers-for-msps-2026/#when-a-hosted
Solo se muestra el principio; lee el resto en el repo