Cisco Meraki MCP

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):

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.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *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, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cisco-meraki/install.ps1 | iex. Then authenticate per the README and run cisco-meraki-cli --help to 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 | iex

macOS / 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 --version

Upgrade 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 | 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 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 --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/cisco-meraki --force

Hermes 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 the openclaw: 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

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