oxidized-mcp
Related Servers
Alternatives to oxidized-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceProvides 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-
- AlicenseAqualityBmaintenanceEnables 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.1899 PyPI3MIT
- AlicenseNot gradedqualityDmaintenanceMCP 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
- AlicenseBqualityDmaintenanceExposes 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.914MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to drive switches, servers, and consoles over SSH or serial Console through 28 MCP tools, auto-detecting vendors, paging through long output, and cleaning raw byte streams into readable text. Provides structured diagnostics (interfaces, ARP/MAC/routing tables, ping, logs, health checks) plus a three-tier safety model with audit logging, credential redaction, and dry-run config changes.MIT
- AlicenseAqualityBmaintenanceProvides 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.33MIT
TDQS
Scored across 11 tools
Most tools target clearly distinct actions on nodes (list, find, get, get_config, get_version, diff, list_versions, search, trigger_backup, stats, reload). The only mild overlap is between get_node_config (latest) and get_node_version (specific version), but the descriptions make the boundary clear.
Every tool follows a consistent snake_case verb_noun pattern (get_node, list_nodes, diff_node_versions, trigger_node_backup, search_configs, reload_nodes). No mixed conventions or vague verb styles.
11 tools is well-scoped for an Oxidized backup management server, covering the distinct facets of node management, config retrieval, versioning, health, and search without bloat.
The surface covers the full lifecycle of inspecting nodes, backups, versions, diffs, health, and search. Missing operations like adding/removing nodes are out of scope (nodes come from router.db/SQL/HTTP sources), so gaps are minor.