Skip to main content
Glama
Flagler-County-BoCC

meraki-dashboard-api

by Flagler-County-BoCC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to meraki-dashboard-api

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 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.
      -

    • 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.
      -

    • appd-mcp

      jagalliers
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for AppDynamics that exposes 12 task-oriented tools to query applications, topology, metrics, snapshots, health rules, anomalies, events, alerting config, analytics events, and dependency maps via OAuth API-client credentials.
      12
      1
      MIT
    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.7/5.0

    Scored across 50 tools

    Disambiguation3/5

    Many tools have overlapping names like 'get-organization-devices' vs 'organizations-get-devices', and similar patterns for switches and wireless. While descriptions clarify the differences, the naming similarity could cause confusion for an agent.

    Naming Consistency2/5

    Inconsistent use of 'get' vs 'list' prefixes, mixed ordering (e.g., 'appliance-list-vlans' vs 'get-organization-uplinks-statuses'), and inconsistent pluralization (e.g., 'switch-get-ports' vs 'switch-list-ports'). No single naming convention is followed.

    Tool Count2/5

    50 tools is excessive for a single MCP server, especially with all being read-only. The large number makes it difficult for an agent to navigate and select the correct tool efficiently.

    Completeness1/5

    All tools are read-only, with no create, update, or delete operations. This severely limits the agent's ability to manage Meraki networks, leaving obvious gaps for a dashboard API.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources