Skip to main content
Glama
amikum0504

Nexus Dashboard MCP Server

by amikum0504
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Nexus Dashboard MCP Server

No user-submitted related servers found.

    Related Servers

    • nodel-mcp

      mcartmel
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP sidecar that exposes a local Nodel runtime via the Model Context Protocol, read-only by default with optional write/lifecycle/delete operations and approval workflows.
      1
      Mozilla Public 2.0

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

    • MCP REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -
    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

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a unique role: generic read, specialized troubleshooting, change preparation, change application, operation discovery, and schema description. No two tools compete for the same action.

    Naming Consistency5/5

    All tools follow the pattern `nexus_<verb>_<target>`, with `nexus_read` being a slight exception but still consistent in verb-first style. Uniform snake_case throughout.

    Tool Count5/5

    Six tools is well-scoped for the server's purpose: two read paths, two change management steps, and two discovery/description tools. Each earns its place with no redundancy.

    Completeness4/5

    The server covers the essential workflow: discover operations, understand schemas, perform read-only calls, and safely prepare/apply changes. Minor gap is the lack of a dedicated change-status or history tool, but that is often achievable via read operations.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources