mcp-oxidized
Related Servers
Alternatives to mcp-oxidized
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to interact with Oxidized network device backups through MCP, including listing and filtering devices, checking backup health, reading and regex-searching configs, browsing git version history and diffs, and triggering backups with read-only and credential-redaction options.1156 PyPI1MIT
- 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
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseNot gradedqualityBmaintenanceExposes read-only tools that lint a supplied MCP client configuration, check version pins, compare configurations, explain rule findings, and export redacted SARIF reports. It flags plaintext credentials, unsafe command patterns, and insecure or overly privileged endpoints entirely offline, without opening files, running commands, or contacting URLs.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools for Cisco Meraki Dashboard API, enabling management of networks, configuration templates, and health checks via natural language commands.-
- AlicenseNot gradedqualityCmaintenanceProvides read-only MCP tools to list and inspect devices, read the live tailnet policy file with its ETag, validate candidate policies before deployment, and report credential capabilities.MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.