Clixon

You can use the Clixon MCP Server to fetch and query network device configuration via RESTCONF, making device data available to AI agents and other tooling. It connects to RESTCONF-capable devices and exposes an MCP interface you can query to retrieve current configurations or specific configuration sections on demand.

How to use

Set up and run the server locally, then connect your MCP client to fetch configuration data, cache it, and query for specific details like interfaces or routing.

How to install

Prerequisites: you need Python and the uv command available in your environment.

# If you are using a Python environment, install dependencies if required by your setup
# This step may vary depending on your project layout

Additional content

You can connect to the MCP server in your OpenCode setup using either a remote HTTP endpoint or a local stdio command. The server provides tools to fetch and inspect device configurations and to extract specific paths within the configuration.

Available tools include fetching the configuration from a RESTCONF source, returning the cached configuration, and extracting a specific configuration path by a dot-separated path, enabling you to answer questions about interfaces, routing, and other configuration aspects.

To start, run the server using the provided runtime command, and then connect your MCP client or OpenCode integration to the appropriate endpoint or process.

Available tools

fetch_config

Fetch device configuration via RESTCONF, supporting basic authentication and TLS variations.

get_config

Return the currently cached configuration in memory.

get_config_path

Extract a specific section from the configuration using a dot-separated path (for example, ietf-interfaces:interfaces.interface).

analyze_config

Analyze the fetched configuration to summarize interfaces, routing, and other configuration elements.