Spec Driven Development
de formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar
Cisco Meraki MCP
Resumen
Descripción del creador (original en inglés)
Meraki Dashboard for MSPs: every API operation plus cross-org outages, renewals, and changes
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en tu computadora
- Transporte: stdio
- Categoría: Otros
- Debes completar: MERAKI_DASHBOARD_API_KEY, CISCO_MERAKI_MCP_HTTP_TOKEN
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
- Debes completar tú:
MERAKI_DASHBOARD_API_KEY,CISCO_MERAKI_BASE_URL,CISCO_MERAKI_MCP_READ_ONLY,CISCO_MERAKI_NO_LOCAL_DATA,CISCO_MERAKI_USER_AGENT,CISCO_MERAKI_MCP_HTTP_TOKEN,PRINTING_PRESS_CLIENT_PROFILE
Los 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.
Valores que debes completar
- Meraki Dashboard API key (Dashboard > My profile > API access); reaches every org its admin can see.
CISCO_MERAKI_BASE_URLenvRegional dashboard API URL, e.g. https://api.meraki.ca/api/v1. Leave blank for https://api.meraki.com/api/v1.CISCO_MERAKI_MCP_READ_ONLYenvSet to 1 to refuse every write from the MCP server (GET only; fleet push --apply refused).CISCO_MERAKI_NO_LOCAL_DATAenvSet to 1 to keep no local copy of API responses (reads go to the API; the response cache is off).CISCO_MERAKI_USER_AGENTenvOverrides the User-Agent the CLI sends on Meraki requests.- Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
PRINTING_PRESS_CLIENT_PROFILEenvBinds this MCP server to one tenant-gated client profile. Leave blank to use the default client profile.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con otros en Otrosi
- Más estrellas que el 0% de los otros 18436 servidores de esta categoría
- Publicado en el registro más recientemente que el 98% de los otros 18436 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 18436 servidores de esta categoría
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.
Preguntas frecuentes
¿Es seguro Cisco Meraki MCP?
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.
¿Qué claves o códigos necesita?
Debes completar: MERAKI_DASHBOARD_API_KEY, CISCO_MERAKI_MCP_HTTP_TOKEN
¿Se ejecuta en mi computadora o en la nube?
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).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.1.4) llegó al registro hoy.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
¿Qué puedo usar en su lugar?
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Alternativas
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
Remote Desktop Commander
de desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Se ejecuta en la nube★ 211Actualizado hace 3 días
Instalar
Tethered Trust
de tetheredtrust.com
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Se ejecuta en la nubeActualizado hoy
Instalar
README del creador
Abrir el README
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.
Cisco Meraki + 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 Cisco Meraki
API. Not affiliated with, endorsed by, or sponsored by Cisco Systems, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Meraki Dashboard operation, plus cross-org fleet views that read every page, and a local mirror built for MSPs running many client orgs. 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
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Cisco Meraki skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register cisco-meraki-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add cisco-meraki-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 cisco-meraki-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs cisco-meraki-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.
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
Download Cisco Meraki MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Cisco Meraki 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 cisco-meraki@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Cisco Meraki 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/cisco-meraki/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-meraki/install.ps1 | iex. Then authenticate per the README and runcisco-meraki-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/cisco-meraki/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-meraki/install.sh)The installer drops both cisco-meraki-cli (the CLI) and cisco-meraki-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
cisco-meraki-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/cisco-meraki/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-meraki/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 cisco-meraki@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/cisco-meraki --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/cisco-meraki --forceHermes speaks MCP natively, so it can also use the cisco-meraki-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the cisco-meraki skill from https://github.com/servosity/msp-skills/tree/main/skills/cisco-meraki. The skill defines how its required CLI (
cisco-meraki-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
Generate a Dashboard API key (Meraki Dashboard > My profile > API access) and set it:
export MERAKI_DASHBOARD_API_KEY=<your-api-key>cisco-meraki-cli doctor cisco-meraki-cli fleet health --limit 5
The key reaches every organization the admin who generated it can see, with that admin's permissions - generate it from a read-only admin if you only want reporting. Each org needs Dashboard API access turned on (Organization > Settings). doctor checks config and reachability and test-calls the key; read its Credentials line, because it exits 0 even when the key is rejected. On a regional dashboard, also set CISCO_MERAKI_BASE_URL (for example https://api.meraki.ca/api/v1 for Canada).
What this skill does
| Question your MSP keeps asking | Command |
|---|---|
| Which client org is in the worst shape right now? | cisco-meraki-cli fleet health --agent |
| What is offline or alerting across every org, and for how long? | cisco-meraki-cli fleet down --agent |
| Which MX WAN uplinks have failed? | cisco-meraki-cli fleet down --kind uplink --json |
| Which licenses, subscriptions, and end-of-support dates are due in 90 days? | cisco-meraki-cli fleet renewals --within 90d --agent |
| Who changed what across all orgs this week? | cisco-meraki-cli fleet changes --since 7d --group-by admin --agent |
| Did a change land right before this device went offline? | cisco-meraki-cli fleet blame "Q2QN-9J8L-SLPD" --window 2h --agent |
| Which org and network owns this MAC, IP, or serial? | cisco-meraki-cli fleet find "00:18:0a:12:34:56" --agent |
| Which admins have two-factor off or stale access, and where does a departed tech still have access? | cisco-meraki-cli fleet admins --stale 90d --flagged --agent |
Beyond the fleet views, all 1,035 Dashboard API operations are typed commands under organizations, networks, devices, and administered; cisco-meraki-cli which "offline devices" finds the right one.
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 Meraki integrations and MCP servers proxy one question into one live API call against one organization, and often read only the first page of a list. That's fine for one record. It dies at MSP scale, when you're asking "what is down for all 30 clients, and since when?"
This skill is built for that question. The fleet commands run across every org the key can see under one rate limiter, follow every Link-header page, and never count an org that fails to answer as zero devices: fleet health keeps it as an unreachable row and the other fleet commands name it on stderr. Compound views do the joins a stateless wrapper can't: fleet down joins device status to org and network names and computes downtime, fleet blame lines up each outage with the config changes made just before it, and fleet renewals merges three licensing models with hardware end-of-support dates into one date-sorted list. The fleet views query the Dashboard live; sync also keeps a local SQLite mirror of the org-level data so search "Acme" --data-source local, fleet find, and fleet changes --data-source local can answer offline. Single-endpoint reads through the MCP server say when Meraki has more pages (has_more, plus the cursor to resume, or how to re-request a page too large for one result).
The pain this closes
Meraki's MSP Portal (now the Global Overview page), as Meraki documents it, lists each client org with device counts, license status, and one co-term expiration date. It documents no cross-org list of which devices are down, no cross-org change log, and no admin management across orgs - so "what is broken for every client right now?" still means clicking into each org. Scripting it runs into the API's shape: paginated lists come back as bare arrays paged only by a Link header, so a one-call script silently stops at page one (the Meraki Communit
Solo se muestra el principio; lee el resto en el repo