Skip to main content
Glama
meks007

mcp-oxidized

by meks007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-oxidized

No user-submitted related servers found.

    Related Servers

    • io.github.AIops-tools/network

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Provides MCP tools for governed multi-vendor network device operations, including configuration management (backup, diff, merge, replace, rollback) and read-only queries (facts, interfaces, BGP, LLDP, ARP) via NAPALM, with optional NetBox source-of-truth integration.
      33
      MIT

    • network-mcp

      JohnGilligan2
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to managed network devices over SSH or Telnet via MCP, allowing users to probe devices, retrieve redacted running or startup configs, gather facts and interfaces, back up multiple devices, and compare configs for drift or unsaved changes.
      -

    • NERD MCP

      MickalSpeller
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only MCP tools that let an LLM client query network inventories, inspect devices over SSH, and diagnose network conditions such as interfaces, routes, BGP, OSPF, and VPN state. Configuration changes stay in the local CLI, while the MCP surface remains strictly read-only.
      Apache 2.0

    • juniper-junos-mcp

      anderson-jason573
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables safe interaction with Juniper Junos devices (SRX firewalls) via MCP, providing operational read tools and a configuration change flow with device-side diff preview and automated rollback.
      Apache 2.0
    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 8 tools

    Disambiguation4/5

    Tools are mostly distinct: list/find/status cover device discovery and health, while version/config/diff tools focus on configuration history. Some overlap exists between get_device_versions, get_config_with_inline_diff, and get_diff_between_versions, but descriptions clarify their specific purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lowercase snake_case (list_devices, find_devices, get_device_status, prepare_config, etc.). The pattern is predictable and uniform across the set.

    Tool Count5/5

    8 tools is well within the ideal range for a network device configuration management server. Each tool addresses a distinct aspect of device listing, status, versioning, and configuration diffing without unnecessary redundancy.

    Completeness3/5

    Core operations are covered: device discovery, status, version listing, current config, and diffs. However, there is no direct way to retrieve a full historical config version (as opposed to a diff), which is a notable gap for a configuration backup tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources