Skip to main content
Glama
vahagn-madatyan

juniper-mist-mcp

by vahagn-madatyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to juniper-mist-mcp

No user-submitted related servers found.

    Related Servers

    • network-mcp-server

      edutacara
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for network operations that lets AI assistants interact with Cisco/Juniper network devices through safe, well-defined tools like compliance audits and configuration backups.
      MIT

    • NetPulse

      hind77
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.
      6
      MIT

    • domotz-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Domotz network monitoring and management. Enables AI assistants to query network devices, alerts, and topology via the Domotz API.
      2
      18 npm
      Apache 2.0

    • defined-mcp

      geoffbelknap
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to manage Defined Networking / Managed Nebula infrastructure, supporting tasks like network topology design, host provisioning, and security auditing through natural language.
      4
      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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct Mist resource or metric (organizations, device stats, SLE summary, client stats, RF templates, alarms, site events, WLANs, inventory, device config). There is no functional overlap or ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent 'mist_[verb]_[noun]' pattern in snake_case. Two use 'list' for enumeration and eight use 'get' for specific data, maintaining a clear and predictable naming convention.

    Tool Count5/5

    Ten tools is an appropriate scope for a Mist network management MCP server. It covers key read-only operations without being excessive or too minimal.

    Completeness3/5

    The tool set is entirely read-only, lacking create, update, or delete operations. Additionally, basic entity listings like sites or detailed device endpoints are missing, which limits full lifecycle coverage for the Mist domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources