Cisco Meraki

MCP server for the Cisco Meraki Dashboard: networks, devices, wireless, switch, appliance.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "cisco-meraki": {
      "command": "npx",
      "args": [
        "-y",
        "cisco-meraki"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Meraki MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with structured access to the Cisco Meraki Dashboard — organizations, networks, devices, clients, wireless, switching, and appliance operations.

Note: This project is maintained by Wyre Technology.

Quick Start

Claude Code (CLI):

Terminal

claude mcp add meraki-mcp \
  -e MERAKI_API_KEY=your-api-key \
  -e MERAKI_ORG_ID=your-org-id \
  -- npx -y github:WYRE-AI/meraki-mcp

See Installation for Docker and from-source methods.

Features

🔌 MCP Protocol Compliance: Full support for MCP tools over stdio and HTTP transports
🌐 Network Coverage: Tools spanning organizations, networks, devices, clients, wireless, switching, and appliance (MX) operations
🔍 Flattened Navigation: meraki_navigate and meraki_status are stateless discovery aids — every tool is callable at any time
🛟 Safety by Default: Read-only mode is ON by default; writes are gated and destructive actions require explicit confirmation
🖼️ Interactive Device Card (MCP Apps): meraki_devices_get renders as a read-only interactive card in MCP Apps hosts (SEP-1865) — neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars
🧰 Long-Tail Escape Hatch: meraki_raw_request reaches any Meraki v1 endpoint not covered by a curated tool
🐳 Docker Ready: Containerized deployment with HTTP transport and health checks
📊 Structured Logging: Configurable log levels

Installation

Option 1: Docker

Terminal

docker run -d \
  -e MERAKI_API_KEY=your-key \
  -e MERAKI_ORG_ID=your-org-id \
  -p 8080:8080 \
  ghcr.io/wyre-ai/meraki-mcp:latest

Option 2: From Source

bash

git clone https://github.com/WYRE-AI/meraki-mcp.git
cd meraki-mcp
npm ci
npm run build

Configuration

Variable	Description	Default
`MERAKI_API_KEY`	Meraki Dashboard API key	—
`MERAKI_ORG_ID`	Default organization ID (optional)	—
`MERAKI_BASE_URL`	Override the Meraki API base URL (optional)	—
`READ_ONLY_MODE`	Safety switch — blocks all writes when `true`	`true`
`MCP_TRANSPORT`	Transport mode (`stdio` or `http`)	`stdio`
`MCP_HTTP_PORT`	HTTP server port	`8080`
`AUTH_MODE`	Auth mode (`env` or `gateway`)	`env`
`LOG_LEVEL`	Log level (`debug`, `info`, `warn`, `error`)	`info`

The legacy READ_ONLY variable is also honored; READ_ONLY_MODE takes precedence.

Safety Model

This server defaults to read-only. Write operations (updates, reboots, deletions) are blocked unless you explicitly set READ_ONLY_MODE=false.

Read tools (*_list, *_get) are always available.
High-impact writes (e.g. meraki_networks_update, meraki_clients_update_policy) are gated by read-only mode.
Confirmation-gated tools additionally require a confirm_destructive_action: true argument, even once READ_ONLY_MODE=false. The confirmation flag is never forwarded to the Meraki API. Two groups qualify:
- Irreversible — meraki_networks_delete, meraki_devices_remove.
- High blast radius — meraki_appliance_firewall_l3_update, meraki_switch_ports_update, meraki_wireless_ssids_update, meraki_devices_reboot. These are reversible in principle, but each is applied over the same network link the change can break, so an operator can lose the connectivity needed to undo it. meraki_appliance_firewall_l3_update also replaces the rule set — any rule not in the payload is deleted — and meraki_wireless_ssids_update drops every client on the SSID when the PSK or auth mode changes.
Confirmation is not an escape hatch from read-only mode: while READ_ONLY_MODE is on, a confirmed call is still blocked.
The meraki_raw_request escape hatch classifies the call by HTTP method: GET is a read; POST/PUT/DELETE are writes; DELETE is destructive.

Domains

All tools are returned upfront. Use meraki_navigate to explore a domain's tools, or meraki_status to check connectivity and the configured organization.

Domain	Tools
organizations	`meraki_organizations_list`, `meraki_organizations_get`, `meraki_organizations_inventory_list`
networks	`meraki_networks_list`, `meraki_networks_get`, `meraki_networks_update` ⚠, `meraki_networks_delete` ⚠⚠
devices	`meraki_devices_list`, `meraki_devices_get`, `meraki_devices_reboot` ⚠⚠, `meraki_devices_remove` ⚠⚠
clients	`meraki_clients_list`, `meraki_clients_get`, `meraki_clients_get_policy`, `meraki_clients_update_policy` ⚠
wireless	`meraki_wireless_ssids_list`, `meraki_wireless_ssids_update` ⚠⚠, `meraki_wireless_rf_profiles_list`
switch	`meraki_switch_ports_list`, `meraki_switch_ports_update` ⚠⚠, `meraki_switch_port_statuses_list`
appliance	`meraki_appliance_firewall_l3_get`, `meraki_appliance_firewall_l3_update` ⚠⚠, `meraki_appliance_vpn_status_get`
(long tail)	`meraki_raw_request` ⚠⚠ (on `DELETE`)

⚠ = high-impact write, gated by read-only mode · ⚠⚠ = additionally requires confirm_destructive_action: true

Docker Deployment

Copy .env.example to .env and fill in your credentials:

bash

cp .env.example .env
# Edit .env with your Meraki API key (and org ID)
docker run --env-file .env -p 8080:8080 ghcr.io/wyre-ai/meraki-mcp:latest

Development

Terminal

npm ci
npm run build       # Build the project
npm run start       # Run over stdio
npm run start:http  # Run the HTTP transport
npm run test        # Run tests

Testing

Terminal

npm test

The test suite covers the safety contract: read-only enforcement, destructive confirmation, and that confirm_destructive_action is never forwarded to the SDK.

License

Apache 2.0 — Copyright WYRE Technology

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Cisco Meraki

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "cisco-meraki": { "command": "npx", "args": ["-y", "Cisco Meraki"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/cisco-meraki?style=directory)](https://allmcps.com/mcp/cisco-meraki)

HTML Embed

<a href="https://allmcps.com/mcp/cisco-meraki"><img src="https://allmcps.com/api/badge/cisco-meraki?style=directory" alt="Cisco Meraki on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Cisco Meraki →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

Meraki MCP Server

Note: This project is maintained by Wyre Technology.

Quick Start

Claude Code (CLI):

Terminal

claude mcp add meraki-mcp \
  -e MERAKI_API_KEY=your-api-key \
  -e MERAKI_ORG_ID=your-org-id \
  -- npx -y github:WYRE-AI/meraki-mcp

See Installation for Docker and from-source methods.

Features

🔌 MCP Protocol Compliance: Full support for MCP tools over stdio and HTTP transports
🌐 Network Coverage: Tools spanning organizations, networks, devices, clients, wireless, switching, and appliance (MX) operations
🔍 Flattened Navigation: meraki_navigate and meraki_status are stateless discovery aids — every tool is callable at any time
🛟 Safety by Default: Read-only mode is ON by default; writes are gated and destructive actions require explicit confirmation
🖼️ Interactive Device Card (MCP Apps): meraki_devices_get renders as a read-only interactive card in MCP Apps hosts (SEP-1865) — neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars
🧰 Long-Tail Escape Hatch: meraki_raw_request reaches any Meraki v1 endpoint not covered by a curated tool
🐳 Docker Ready: Containerized deployment with HTTP transport and health checks
📊 Structured Logging: Configurable log levels

Installation

Option 1: Docker

Terminal

docker run -d \
  -e MERAKI_API_KEY=your-key \
  -e MERAKI_ORG_ID=your-org-id \
  -p 8080:8080 \
  ghcr.io/wyre-ai/meraki-mcp:latest

Option 2: From Source

bash

git clone https://github.com/WYRE-AI/meraki-mcp.git
cd meraki-mcp
npm ci
npm run build

Configuration

Variable	Description	Default
`MERAKI_API_KEY`	Meraki Dashboard API key	—
`MERAKI_ORG_ID`	Default organization ID (optional)	—
`MERAKI_BASE_URL`	Override the Meraki API base URL (optional)	—
`READ_ONLY_MODE`	Safety switch — blocks all writes when `true`	`true`
`MCP_TRANSPORT`	Transport mode (`stdio` or `http`)	`stdio`
`MCP_HTTP_PORT`	HTTP server port	`8080`
`AUTH_MODE`	Auth mode (`env` or `gateway`)	`env`
`LOG_LEVEL`	Log level (`debug`, `info`, `warn`, `error`)	`info`

The legacy READ_ONLY variable is also honored; READ_ONLY_MODE takes precedence.

Safety Model

This server defaults to read-only. Write operations (updates, reboots, deletions) are blocked unless you explicitly set READ_ONLY_MODE=false.

Read tools (*_list, *_get) are always available.
High-impact writes (e.g. meraki_networks_update, meraki_clients_update_policy) are gated by read-only mode.
Confirmation-gated tools additionally require a confirm_destructive_action: true argument, even once READ_ONLY_MODE=false. The confirmation flag is never forwarded to the Meraki API. Two groups qualify:
- Irreversible — meraki_networks_delete, meraki_devices_remove.
- High blast radius — meraki_appliance_firewall_l3_update, meraki_switch_ports_update, meraki_wireless_ssids_update, meraki_devices_reboot. These are reversible in principle, but each is applied over the same network link the change can break, so an operator can lose the connectivity needed to undo it. meraki_appliance_firewall_l3_update also replaces the rule set — any rule not in the payload is deleted — and meraki_wireless_ssids_update drops every client on the SSID when the PSK or auth mode changes.
Confirmation is not an escape hatch from read-only mode: while READ_ONLY_MODE is on, a confirmed call is still blocked.
The meraki_raw_request escape hatch classifies the call by HTTP method: GET is a read; POST/PUT/DELETE are writes; DELETE is destructive.

Domains

All tools are returned upfront. Use meraki_navigate to explore a domain's tools, or meraki_status to check connectivity and the configured organization.

Domain	Tools
organizations	`meraki_organizations_list`, `meraki_organizations_get`, `meraki_organizations_inventory_list`
networks	`meraki_networks_list`, `meraki_networks_get`, `meraki_networks_update` ⚠, `meraki_networks_delete` ⚠⚠
devices	`meraki_devices_list`, `meraki_devices_get`, `meraki_devices_reboot` ⚠⚠, `meraki_devices_remove` ⚠⚠
clients	`meraki_clients_list`, `meraki_clients_get`, `meraki_clients_get_policy`, `meraki_clients_update_policy` ⚠
wireless	`meraki_wireless_ssids_list`, `meraki_wireless_ssids_update` ⚠⚠, `meraki_wireless_rf_profiles_list`
switch	`meraki_switch_ports_list`, `meraki_switch_ports_update` ⚠⚠, `meraki_switch_port_statuses_list`
appliance	`meraki_appliance_firewall_l3_get`, `meraki_appliance_firewall_l3_update` ⚠⚠, `meraki_appliance_vpn_status_get`
(long tail)	`meraki_raw_request` ⚠⚠ (on `DELETE`)

⚠ = high-impact write, gated by read-only mode · ⚠⚠ = additionally requires confirm_destructive_action: true

Docker Deployment

Copy .env.example to .env and fill in your credentials:

bash

cp .env.example .env
# Edit .env with your Meraki API key (and org ID)
docker run --env-file .env -p 8080:8080 ghcr.io/wyre-ai/meraki-mcp:latest

Development

Terminal

npm ci
npm run build       # Build the project
npm run start       # Run over stdio
npm run start:http  # Run the HTTP transport
npm run test        # Run tests

Testing

Terminal

npm test

The test suite covers the safety contract: read-only enforcement, destructive confirmation, and that confirm_destructive_action is never forwarded to the SDK.