Cisco Meraki MCP Server

An MCP server for the Cisco Meraki Dashboard API (v1), the cloud-managed networking platform (security appliances, switches, wireless access points) MSPs run for their clients. It lets an AI agent browse organizations, networks, devices and connected clients, read switch ports, SSIDs, RF profiles, firewall rules and VPN settings, and - when an operator allows it - change them, reboot or remove devices, or call any other Dashboard API endpoint.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

• Read-only by default: every change is refused until the operator sets READ_ONLY_MODE=false, and even then each one needs confirm_destructive_action: true

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: Selent MCP

Authentication headers

Where to get them: enable API access under Organization > Settings in the Meraki dashboard, then generate a key under My profile > API access. The key has the same permissions as the dashboard user who created it (a read-only admin gives a read-only key). The organization id is in meraki_organizations_list.

How the key is sent: every call goes to https://api.meraki.com/api/v1/... with Authorization: Bearer <key>. Meraki may redirect to the organization's own shard host; those redirects are followed only to Meraki hosts, keeping the key.

A request to /mcp without the key gets HTTP 401; a malformed organization id gets HTTP 400.

Tools

All tools return a JSON string. Paged lists take per_page (default 50, max 200; larger values are capped) and starting_after, and return {count, has_more, next_cursor}; pass next_cursor back as starting_after. Lists Meraki returns in full (switch ports and port statuses, a network's devices, SSIDs and RF profiles, organizations) take offset and limit instead and return {count, total, offset, has_more, next_offset}: pass next_offset as offset to continue; when a result is cut to fit the size limit it starts right after the last record returned. A 404 on an organization-scoped call says that the organization may have API access disabled or the key no access to it. When a meraki_raw_request GET is cut, the note says how to page it with Meraki's own perPage / startingAfter query parameters.

Bold parameters are required. W marks a change: it is refused in read-only mode and returns {"done": false, "action": ...} until it is called again with confirm_destructive_action: true after the user approved that exact change. Pre-shared SSID keys are masked in results.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "Meraki returned HTTP 401 for organizations", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error; a change refused in read-only mode returns not_configured. Reads are retried with backoff on 429, 5xx and network errors; changes only on 429, so a change never runs twice. Meraki allows about 10 calls per second per organization.

Run locally

uv sync
uv run python -m meraki_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t meraki-mcp:dev .
docker run --rm -p 8080:8080 meraki-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO), READ_ONLY_MODE (default true; false allows changes), MERAKI_BASE_URL (default https://api.meraki.com/api/v1; for the China, Canada or India clouds, e.g. https://api.meraki.cn/api/v1, Meraki hosts only). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Meraki-Api-Key: your-api-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# networks of an organization
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Meraki-Api-Key: your-api-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"meraki_networks_list","arguments":{"organization_id":"549236"}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (27). Kept as is because the tool names are an existing contract; every earlier parameter is still accepted with the same required set.

• API source. The official Meraki Dashboard API OpenAPI specification (github.com/meraki/openapi, v1); every route was checked against it.

• Safety model kept. Read-only by default (READ_ONLY_MODE / READ_ONLY), and every change needs confirm_destructive_action: true, as before. meraki_raw_request accepts only a relative Dashboard API path (no host, //, .. or query string - use query).

• New optional parameter: starting_after on meraki_clients_list, so its pages can be followed like the other lists.

• Redirects to the organization's shard host are followed by hand (HTTP clients drop the Authorization header on a cross-host redirect), only to Meraki hosts.

• Not included: the device "card" UI resource of older versions (an MCP Apps HTML view); meraki_devices_get returns the same data as JSON. Credentials from environment variables (MERAKI_API_KEY / MERAKI_ORG_ID) are not supported: they would be shared by every caller.

License

Apache License 2.0 - see LICENSE and NOTICE.