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

    • junos-mcp-server

      Conexon-Connect
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible clients such as Claude Desktop to interact with Juniper Junos network devices, exposing tools for running operational commands, applying and committing configuration changes with guardrails, and managing device connections over stdio or streamable-http transports. Supports password and SSH key authentication, connection pooling, and token-based access control for the HTTP transport.
      Apache 2.0

    • 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

    • rust-junosmcp

      mechubsec
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to operate Juniper Junos and SRX network devices over NETCONF and SCP, running operational CLI and PFE commands, inspecting and diffing configuration, validating and committing changes with confirmed auto-rollback, and managing SRX security workflows such as signature-package updates, chassis-cluster health, and read-only policy and address-book inspection.
      3
      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.8/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (facts, version, config, upgrade, reboot, RSI), and the daily_brief/daily_brief_start/daily_brief_result trio is well differentiated as sync/async-start/async-poll. The main risk is the show-command family (run_show_command, run_show_commands, run_show_command_batch), where the singular/plural naming and overlapping purposes could cause misselection, though descriptions do draw boundaries. Overall mostly distinct with one ambiguous cluster.

    Naming Consistency4/5

    Predominantly consistent snake_case verb_noun (get_config, push_config, collect_rsi, check_reachability, schedule_reboot). The one wrinkle is run_show_command vs run_show_commands, differing only by plural, which is a subtle and potentially confusing deviation. Still readable and largely predictable throughout.

    Tool Count3/5

    26 tools is at the heavy end for a single MCP server, and several are near-duplicates that could be consolidated (three show-command variants, three daily_brief lifecycle tools). The breadth of the domain (health checks, upgrades, RSI, config) justifies most tools, but the count is borderline heavy.

    Completeness4/5

    The surface covers a full device lifecycle: discovery (router list, facts, version), reachability, config get/diff/push, firmware copy/install/rollback/schedule, RSI collection, and inventory checksum verification. Gaps are minor, e.g. no explicit rollback/delete for pushed config or per-interface targeted operations, but core workflows have no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources