The dynamic build's roughly 804 endpoints give an agent the whole Dashboard API, which is a lot of tools to expose; the 40-endpoint manual build is the tighter, type-checked option when you know what you need. READ_ONLY_MODE being true out of the box, plus a separate confirm flag for destructive calls, is the reason it is safe to point at a live org while you learn what it does.
A Python server over the Meraki Dashboard API, shipped in two flavours: a dynamic build exposing about 804 SDK endpoints, and a manual build with 40 curated endpoints.
- Organization management — admins, networks, devices, inventory, licensing
- Wireless — SSIDs, RF profiles, Air Marshal, analytics
- Switching — ports, VLANs, stacks, QoS, access policies
- Appliance and security — firewall types, NAT, VPN, traffic shaping
- Cameras, network monitoring (events, alerts, health), and live troubleshooting — ping, cable test, ARP table
- The dynamic build tracks the SDK, so upgrading it exposes new endpoints with no manual coding
Python 3.13+, a Meraki Dashboard API key and organization ID in MERAKI_API_KEY and MERAKI_ORG_ID. Clone, create a venv, install requirements, then launch the chosen server file with fastmcp. READ_ONLY_MODE defaults to true, blocking create, update and delete; destructive calls additionally need confirm_destructive_action=true. MERAKI_BASE_URL points at another region if needed.
One command plus a key — uvx meraki-magic-mcp, then supply credentials