Skip to main content
Glama
shigechika

io.github.shigechika/junos-mcp

by shigechika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to io.github.shigechika/junos-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

    • linux-ssh-mcp

      JINDEZHIDIYE
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.
      MIT

    • Device MCP Server

      rajib884
      A
      license
      A
      quality
      D
      maintenance
      A comprehensive MCP server for network device management via SSH/Telnet. Supports multiple vendors such as Cisco IOS and BDCOM, enabling AI assistants to execute commands and manage routers, switches, and firewalls.
      4
      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
    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 24 tools

    Disambiguation5/5

    Each tool targets a distinct operation: firmware lifecycle (copy, install, rollback), configuration (push, get, diff), health checks (daily_brief, check_reachability, etc.), and command execution (single/multi/batch). Despite some similar names like check_reachability vs check_local_inventory, their purposes and arguments are clearly differentiated.

    Naming Consistency5/5

    Tools follow a consistent verb_noun snake_case pattern (e.g., copy_package, run_show_command, collect_rsi_batch). Minor exceptions like 'daily_brief' are still intuitive. Batch variants are suffixed with '_batch', maintaining a predictable structure.

    Tool Count4/5

    With 24 tools, the server covers firmware, config, health checks, and batch operations for Juniper devices. The count is slightly high but justified by the breadth of functionality. Each tool serves a specific purpose, and no tool seems redundant.

    Completeness4/5

    The tool surface covers the full firmware upgrade lifecycle, configuration management (push, get, diff), health checks (including daily brief, reachability, inventory), and command execution. Minor gaps like a dedicated 'delete_package' or 'backup_config' are mitigated by existing tools (e.g., copy_package overwrites, collect_rsi includes config). Overall, very comprehensive.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources