radkit -community

This MCP server acts as a lightweight middleware between Cisco RADKit and any MCP-compatible client. It exposes tools that let an MCP client discover devices registered in the RADKit inventory, fetch device attributes, and run CLI commands on devices through the RADKit service. Use get_device_inventory_names() to list onboarded devices, then get_device_attributes(target_device) to inspect a specific device. When you need to execute CLI commands, use exec_cli_commands_in_device(...) to send commands to a chosen device with optional timeout and line-limit controls. For SNMP-oriented checks, snmp_get(...) can fetch OIDs from devices without invoking the CLI. If you need structured command results, use exec_command(...) which returns a dictionary or list of dictionaries with status and output. This set of tools lets you build richer conversational flows where an LLM can inspect devices, check configurations, and issue commands through RADKit.

Prerequisites:

• Python 3.10+ installed on the host
• Access to Cisco RADKit service with at least one read-only or read/write user
• Git for cloning the repository

Install steps:

1. Clone the repository bash git clone https://github.com/ponchotitlan/radkit-mcp-server-community.git cd radkit-mcp-server-community

2. Create and activate a virtual environment

   • Linux/macOS: python -m venv .venv source .venv/bin/activate
   • Windows (PowerShell): ..venv\Scripts\activate

3. Install dependencies (from pyproject.toml is preferred if using PEP 621 tooling)

   • If a requirements file exists: pip install -r requirements.txt
   • Otherwise, install core dependencies: pip install fastmcp cisco_radkit_client==1.9.0 cisco_radkit_common==1.9.0 cisco_radkit_service==1.9.0

4. Run the MCP server

   • Ensure the RADKit environment variables are set (see environment variables in mcp_config below).
   • Start the server: python -m radkit_mcp_server.community

5. Verify the server is reachable via your MCP client and the exposed tools are functional.

Environment variables/config options:

• RADKIT_USERNAME, RADKIT_PASSWORD: Credentials for RADKit authentication
• RADKIT_HOST, RADKIT_PORT: RADKit service endpoint
• RADKIT_CERTS_PATH: Optional path for client certificates used for authentication

Common issues:

• If the RADKit service requires a certificate-based login, ensure the certificate workflow is completed and certificates are accessible to the server process.
• Ensure firewall/network rules permit outbound connections to the RADKit service.
• If the MCP server cannot authenticate with RADKit, double-check credentials and host/port values; enable verbose logging if available to diagnose authentication failures.

Monitoring:

• Look for startup logs indicating successful RADKit connection and inventory fetch. If inventory is empty, confirm RADKit service has devices onboarded and that your credentials have read access.
• For CLI execution, verify that the target device supports the requested commands and that the user has permission to execute those commands via RADKit.