Cisco RADKit MCP Server

Disclaimer: This MCP Server is not an official Cisco product. It was developed for experimentation and learning purposes.

🚀 Overview

This MCP server acts as a lightweight middleware layer between the Cisco RADKit service and an MCP-compatible client.
It allows the LLM to inspect and interact with devices onboarded in the RADKit inventory, fetch device attributes, and even execute CLI commands — all through structured MCP tools.

⚙️ Features

🔌 Plug-and-play MCP server — works with any MCP-compatible client.
🔍 Inventory discovery — list all onboarded network devices.
🧠 Device introspection — fetch device attributes and capabilities.
🖥️ Command execution — run CLI commands on network devices.
📦 Fully type-hinted tools for clarity and extensibility.

📚 Included libraries

All required libraries are mentioned in the file requirements.txt, including their fixed versions.

cisco_radkit_client==1.9.0
cisco_radkit_common==1.9.0
cisco_radkit_service==1.9.0
fastmcp==2.13.1

🧰 Exposed MCP Tools

Tool Name	Description	Inputs	Returns	Use Case
`get_device_inventory_names()`	Returns a string containing the names of devices onboarded in the Cisco RADKit inventory.	None	`str` : List of onboarded devices (e.g. `{"p0-2e", "p1-2e"}` )	Use this first when the user asks about "devices", "network", or "all devices".
`get_device_attributes(target_device: str)`	Returns detailed information about a specific device in JSON format.	`target_device (str)` : Target device name.	`str` : JSON with attributes including name, host, type, configs, SNMP/NETCONF status, capabilities, etc.	Use this when the user asks about a specific device.
`exec_cli_commands_in_device(target_device: str, cli_command: str)`	Executes a CLI command or commands on a target device and returns the raw text result.	`target_device (str)` : Device name. `cli_commands ([str])` : CLI command or commands to execute.	`str` : Raw output of the executed command.	Use this only if info is unavailable in `get_device_attributes()` or when explicitly asked to “run” or “execute” a command.

🧩 Requirements

Python 3.10+
Active Cisco RADKit service
At least one read-only/RW user onboarded in the Cisco RADKit service

For more information about setting up a Cisco RADKit service, visit this link.

🛠️ Installation

Clone the repository in your deployment environment.

git clone https://github.com/ponchotitlan/radkit-mcp-server.git cd radkit-mcp-server

⚙️ Setup

Execute the included assistant script in a terminal based on your type of host OS:

🐧🍎 Linux/MacOS:

chmod +x setup.sh

bash setup.sh

🪟 Windows:

setup.bat

The assistant will first create a virtual environment folder radkit-mcp-server/.venv/ with all the python libraries required. Afterwards, it will trigger the following assistant:

╭─────────────────────────────────────────╮ │ 🚀 Cisco RADKit MCP Server Utility Tool │ ╰─────────────────────────────────────────╯ ? Choose an option: (Use arrow keys) » 1. 👾 Onboard user to non-interactive Cisco RADKit authentication 2. 📚 Generate .env file for Cisco RADKit MCP server Exit

👾 1. Non-interactive Cisco RADKit authentication setup

The MCP server makes use of certificate login to avoid asking for Web UI authentication every time a tool is used. For that, the certificates need to be generated in the host. Select the first option and follow the instructions.

╭─────────────────────────────────────────╮ │ 🚀 Cisco RADKit MCP Server Utility Tool │ ╰─────────────────────────────────────────╯ ? Choose an option: 1. 👾 Onboard user to non-interactive Cisco RADKit authentication ? Enter Cisco RADKit username: ponchotitlan@cisco.com ╭───────────────────────────────────────────────────────────────────╮ │ Starting Cisco RADKit onboarding for user: ponchotitlan@cisco.com │ ╰───────────────────────────────────────────────────────────────────╯ A browser window was opened to continue the authentication process. Please follow the instructions there. Authentication result received. New private key password: *********** Confirm: *********** The private key is a very sensitive piece of information. DO NOT SHARE UNDER ANY CIRCUMSTANCES, and use a very strong passphrase. Please consult the documentation for more details. <frozen radkit_client.async_.client>:891: UserWarning: The private key is a very sensitive piece of information. DO NOT SHARE UNDER ANY CIRCUMSTANCES, and use a very strong passphrase. Please consult the documentation for more details.

Take note of the password provided, as it will be needed for the 2nd option! Now, select the second option:

📚 2. Generate .env file

Provide the information requested. The password is the one just setup in the first option.

? Choose an option: 2. 📚 Generate .env file for Cisco RADKit MCP server ╭───────────────────────────────────────────────────────────────────────────────╮ │ Warning: Make sure Cisco RADKit certificates for this username already exist. │ │ If not, run the onboarding process first using option 1. │ ╰───────────────────────────────────────────────────────────────────────────────╯ ? Enter Cisco RADKit username: ponchotitlan@cisco.com ? Enter Cisco RADKit service code: aaaa-bbbb-cccc ? Enter non-interactive authentication password: ***********

This MCP server supports both stdio and https transport methods. When prompted, choose the one that you would like to use:

? Select MCP transport mode: (Use arrow keys) » stdio https

Default choice is stdio. Otherwise, if https is selected, you will be prompted for the following information:

? Select MCP transport mode: https ? Enter MCP host: 0.0.0.0 ? Enter MCP port: 8000 ╭──────────────────────────────────────╮ │ ✅ .env file generated successfully! │ │ Saved as .env │ ╰──────────────────────────────────────╯

The file radkit-mcp-server/.env is generated with environment variables that the MCP Server needs. ✅ Your MCP server is ready for use!

⚡️ Usage example: Claude Desktop

The Claude Desktop application provides an environment which integrates the Claude LLM and a rich MCP Client compatible with this MCP Server.

To get started, download the Claude Desktop app for your host OS, and choose the LLM usage plan that best fits your needs.

Afterwards, edit the radkit-mcp-server/claude_desktop_config.json file included in this repository to point to the absolute paths of your .venv and mcp_server.py files:

{ "mcpServers": { "radkit-mcp-server": { "command": "/Users/ponchotitlan/Documents/radkit-mcp-server-community/.venv/bin/python", "args": [ "/Users/ponchotitlan/Documents/radkit-mcp-server-community/mcp_server.py" ], "description": "Cisco RADKit MCP Server - Community" } } }

Then, copy this file to the location of your Claude Desktop application' configurations. The directory varies depending on your host OS:

🍎 MacOS:

cp claude_desktop_config.json ~/Library/Application\ Support/Claude

🪟 Windows:

cp claude_desktop_config.json %APPDATA%\Claude\

🐧 Linux:

cp claude_desktop_config.json ~/.config/Claude/

Now, restart your Claude Desktop app. Afterwards, if you navigate to Configurations/Developer/, you should see the MCP Server up and running:

✨ Prompt examples

📚 Show the inventory of your Cisco RADKit service One of the MCP server tools provides a list of device names.

🎰 Ask specific questions about a device Another MCP server tool provides information of the device if available directly in the Cisco RADKit SDK.

Otherwise, a command is executed in the device via a MCP server tool to get the information required.

🗺️ Complex querying using networking data The LLM can use the information from multiple data network queries to build, for example, a topology diagram.

This diagram can be later refined with more information from the network as required.

⬇️ Push configurations Not everything is query information! If the Cisco RADKit user onboarded in the MCP server is enabled with Write privileges, commit operations can take place.

These are just some examples of what can be done with this MCP server!