Skip to main content
Glama
mhajder

oxidized-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to oxidized-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-oxidized

      meks007
      F
      license
      A
      quality
      B
      maintenance
      Provides MCP tools to query, compare, and analyze network device configurations managed by Oxidized, such as listing devices, viewing backup status, and generating diffs between configuration versions.
      8
      -

    • NetBox MCP Server

      mhajder
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and manage NetBox network infrastructure data via MCP. Supports querying all object types, search, changelogs, GraphQL, IP/prefix/VLAN allocation, cable tracing, config rendering, and write operations with safety modes.
      MIT

    • 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

    • Cisco NSO MCP Server

      NSO-developer
      A
      license
      B
      quality
      D
      maintenance
      Exposes Cisco Network Services Orchestrator (NSO) operations and data as MCP tools and resources, enabling AI-powered network automation through natural language. It supports tasks like retrieving device configurations, checking sync status, and managing services via the NSO RESTCONF API.
      9
      14
      MIT

    • 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
    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.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing vs searching nodes, fetching node metadata vs configuration, viewing versions vs diffs, and explicit actions like triggering backups and reloading. Even overlapping tools like get_node and get_node_config are separated by their outputs (device details vs configuration content).

    Naming Consistency5/5

    All 11 tools follow a consistent verb_noun snake_case pattern (e.g., list_nodes, get_node_config, diff_node_versions). Verbs are descriptive and uniform, with no style mixing or vague generic names.

    Tool Count5/5

    11 tools is well-scoped for an Oxidized MCP server. Each tool serves a distinct function in the backup management workflow—discovery, inspection, search, versioning, and operational triggers—without redundancy or excessive granularity.

    Completeness5/5

    The surface covers the full lifecycle of Oxidized operations: discovering nodes (list/find), checking backup health (stats), retrieving configs (current and historical), comparing versions, triggering backups, and refreshing the node list. No obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources