mcp-oxidized
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port the MCP server listens on | 8000 |
| OXIDIZED_URL | Yes | Base URL of your Oxidized instance | |
| OXIDIZED_PASS | Yes | Basic Auth password | |
| OXIDIZED_USER | Yes | Basic Auth username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | Return all devices managed by Oxidized. Each entry includes: name, model, group, ip, last backup time, status. |
| find_devicesA | Find Oxidized devices by exact or partial name, full name, or IP address. Matching is case-insensitive. Use this before other device tools when only part of a device name is known. |
| get_device_statusA | Return status details for a single device. The node may be an exact name or a unique partial name. |
| get_device_versionsA | Return all available configuration versions for a device. The node may be an exact name or a unique partial name. Versions are numbered oldest-first: version 1 is the oldest and the highest number is the newest. Each entry includes its timestamp and OID. |
| prepare_configA | Prepare one device's current configuration for the static get_content resource. The node may be an exact name or a unique partial name. This tool returns only device metadata; read oxidized://config/get_content for the configuration. |
| prepare_blameA | Prepare one device's configuration blame for the static get_blame resource. The node may be an exact name or a unique partial name. This tool returns only device metadata; read oxidized://config/get_blame for the annotated config. |
| get_config_with_inline_diffA | Return the complete current configuration with inline change markers relative to a reference version number. The node may be an exact name or a unique partial name. |
| get_diff_between_versionsA | Return a unified diff between two historical versions of a device configuration. The node may be an exact name or a unique partial name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Get prepared current configuration | Returns the current configuration selected by prepare_config in this MCP session. Call prepare_config first. The configuration is fetched live from Oxidized for every resource read. |
| Get prepared configuration blame | Returns the annotated configuration selected by prepare_blame in this MCP session. Call prepare_blame first. The current and historical configurations are fetched live from Oxidized for every resource read. |
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.