Back to Browse
Free
Server data from the Official MCP Registry
MCP server for the Cisco Meraki Dashboard: networks, devices, wireless, switch, appliance.
About
MCP server for the Cisco Meraki Dashboard: networks, devices, wireless, switch, appliance.
Security Report
5.2
Moderate5.2Moderate RiskThis MCP server demonstrates solid security practices with a well-designed safety model. Read-only mode is enabled by default, write operations are properly gated, and destructive actions require explicit confirmation. The code is clean, input validation is delegated to the underlying SDK, and there are no hardcoded credentials or malicious patterns. Minor code quality suggestions around error handling do not meaningfully impact the security posture. Supply chain analysis found 5 known vulnerabilities in dependencies (2 critical, 2 high severity).
7 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Cisco Meraki Dashboard API keyRequired
Environment variable: MERAKI_API_KEY
Default Meraki organization ID (optional)
Environment variable: MERAKI_ORG_ID
Override the Meraki API base URL (optional)
Environment variable: MERAKI_BASE_URL
Safety switch. When true (the default), all write operations are blocked. Set to false to enable writes.
Environment variable: READ_ONLY_MODE
Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
Environment variable: MCP_TRANSPORT
Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
Environment variable: AUTH_MODE
Log verbosity: debug, info, warn, error
Environment variable: LOG_LEVEL
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-wyre-technology-meraki-mcp": {
"env": {
"AUTH_MODE": "your-auth-mode-here",
"LOG_LEVEL": "your-log-level-here",
"MCP_TRANSPORT": "your-mcp-transport-here",
"MERAKI_ORG_ID": "your-meraki-org-id-here",
"MERAKI_API_KEY": "your-meraki-api-key-here",
"READ_ONLY_MODE": "your-read-only-mode-here",
"MERAKI_BASE_URL": "your-meraki-base-url-here"
},
"args": [
"-y",
"@wyre-technology/meraki-mcp"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
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):
claude mcp add meraki-mcp \
-e MERAKI_API_KEY=your-api-key \
-e MERAKI_ORG_ID=your-org-id \
-- npx -y github:wyre-technology/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_navigateandmeraki_statusare 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
- 🧰 Long-Tail Escape Hatch:
meraki_raw_requestreaches 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
docker run -d \
-e MERAKI_API_KEY=your-key \
-e MERAKI_ORG_ID=your-org-id \
-p 8080:8080 \
ghcr.io/wyre-technology/meraki-mcp:latest
Option 2: From Source
git clone https://github.com/wyre-technology/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_ONLYvariable is also honored;READ_ONLY_MODEtakes 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_devices_reboot,meraki_wireless_ssids_update) are gated by read-only mode. - Destructive tools (
meraki_networks_delete,meraki_devices_remove) additionally require aconfirm_destructive_action: trueargument. The confirmation flag is never forwarded to the Meraki API. - The
meraki_raw_requestescape hatch classifies the call by HTTP method:GETis a read;POST/PUT/DELETEare writes;DELETEis 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 |
⚠ = high-impact write · ⚠⚠ = destructive / irreversible
Docker Deployment
Copy .env.example to .env and fill in your credentials:
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-technology/meraki-mcp:latest
Development
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
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
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
80.0K
Stars
6
Installs
5.3
Security
No ratings yet
Local
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
80.0K
Stars
6
Installs
6.5
Security
No ratings yet
Local
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
137
Stars
533
Installs
8.0
Security
4.8
Local