Meraki MCP Server
Related Servers
Alternatives to Meraki MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides MCP tools for Cisco Meraki Dashboard API, enabling management of networks, configuration templates, and health checks via natural language commands.-
- FlicenseNot gradedqualityAmaintenanceProvides AI assistants with structured access to the Cisco Meraki Dashboard for managing organizations, networks, devices, clients, wireless, switching, and appliance operations.1-
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server for Cisco Meraki Dashboard, enabling LLMs to discover devices, check health, troubleshoot, and generate reports via natural language.MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with the Meraki Dashboard API for LLMs, allowing seamless integration of Meraki network management capabilities within an AI assistant's conversational interface.1MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP (Model Context Protocol) server that enables interaction with the Cisco Meraki Dashboard API, allowing users to manage Meraki networks, devices, and configurations through natural language.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Cisco Meraki networks through natural language, including organizations, networks, devices, switches, wireless, and appliances.1GPL 3.0
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: organizations, devices, firmware upgrades at org/network level, licenses, and networks. The only potentially confusing pair (get vs update firmware) is clearly separated by verb and scope, leaving no ambiguity.
All tool names follow a consistent verb-first camelCase pattern: 'get' for read operations and 'update' for the single write operation. The pattern is uniformly applied across resources, with no mixing of conventions.
The server has 6 tools, which is well within the ideal 3-15 range. Each tool covers a meaningful aspect of the Meraki domain, and the set feels neither sparse nor bloated.
The server covers core organization-level reads (orgs, networks, devices, firmware, licenses) and one update for network firmware. Minor gaps exist, such as no per-network device listing or create/delete operations, but these are acceptable for a focused read-heavy server.