Cisco Cli MCP

🚀 Cisco CLI MCP Server

A Telnet-based MCP tool for Cisco network device CLI, optimized for Cisco IOS devices. This tool simplifies the management and configuration of Cisco network devices through intelligent connection management and efficient command execution.

✨ Features

• Smart Connection Management: Automatically activates the terminal, warms up TCP, and disables pagination automatically.
• Device Mode Detection: Automatically detects user mode, privileged mode, and config mode.
• Smart Wait Mechanism: Returns immediately upon detecting the device prompt.
• Long-running Command Optimization: Automatically detects commands like ping and traceroute and extends the wait time.

📦 Installation

git clone https://github.com/XunMInt/cisco-cli-mcp.git
cd cisco-cli-mcp
pip install -e .

💻 Usage Examples

Basic Usage

Run as MCP Server

cisco-cli-mcp

Configure MCP Client

Add the following to the MCP client configuration:

{
  "mcpServers": {
    "cisco-cli-mcp": {
      "command": "cisco-cli-mcp"
    }
  }
}

Advanced Usage

The tool provides several useful functions for managing Telnet connections and executing commands:

• telnet_connect: Establishes a Telnet connection and returns the session ID and device mode.
• telnet_execute: Executes a command in a session and returns the output and device mode.
• telnet_list_sessions: Lists all active sessions.
• telnet_disconnect: Disconnects a session.

📚 Documentation

Response Format

telnet_connect

{
  "success": true,
  "sessionId": "xxx-xxx-xxx",
  "deviceMode": "SW3#",
  "message": "Connection successful"
}

telnet_execute

{
  "success": true,
  "output": "Command output...",
  "deviceMode": "SW3#"
}

System Prompt

You are a Cisco network device configuration assistant, skilled in configuring routers and switches.

1. You can use the cisco-cli-mcp tool to connect to devices.
2. For long-running operations like ping, traceroute, show tech-support, etc., set wait_ms to 3000 - 10000 milliseconds or longer.
3. When sending commands, always remember the current system mode (e.g., privileged mode, global config mode). Adjust commands based on mode (e.g., add "do" prefix for show commands in config mode, use "configure terminal" to enter config mode from privileged mode).
4. If already connected, use telnet_list_sessions to reuse existing sessions instead of reconnecting.
5. When unsure about configuration, run show commands first to verify before making changes.
6. All configurations should be based on the topology information provided by the user. Ask for clarification if anything is unclear.
7. If a command error occurs, use the "?" command to see available options.
8. Before calling a tool, briefly explain what you're about to do (no need for lengthy explanations).