Skip to main content
Glama
CiscoDevNet

Meraki Magic MCP

by CiscoDevNet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Meraki Magic MCP

No user-submitted related servers found.

    Related Servers

    • meraki-mcp

      reshif
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for Cisco Meraki Dashboard, enabling LLMs to discover devices, check health, troubleshoot, and generate reports via natural language.
      MIT

    • Meraki Dashboard MCP Server

      rigzindorje
      F
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      -

    • Meraki MCP Server

      xaviervalette
      F
      license
      Not graded
      quality
      D
      maintenance
      This MCP (Model Context Protocol) Server provides a communication interface for the Meraki Dashboard API, auto-generated using AG2's MCP builder from the Meraki OpenAPI specification.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.4/5.0

    Scored across 22 tools

    Disambiguation2/5

    Multiple tools like getOrganizationAdmins, getDevice, etc., overlap with the generic call_meraki_api, which can perform all those actions and more. This creates ambiguity about which tool to use for a given operation.

    Naming Consistency2/5

    Tool names mix conventions: some use camelCase (getDevice, getNetworkClients) while others use snake_case (get_mcp_config, list_all_methods). This inconsistency makes it harder to predict tool names.

    Tool Count3/5

    With 22 tools, the count is on the higher side. Many tools are specific getters that could be subsumed by the generic call_meraki_api, making the set feel bloated for the domain.

    Completeness4/5

    The generic call_meraki_api provides access to all 804+ Meraki endpoints, so the tool surface is essentially complete. The specific tools cover common reads, but missing CRUD operations are addressed by the generic method.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources