SSH MCP Server

What is SSH MCP Server?

The SSH MCP Server is a centralized management system for network devices. It leverages an SSH API to execute commands on switches, providing advanced network monitoring, configuration validation, and reporting capabilities.

How to use SSH MCP Server?

Clone the repository, set up a Python virtual environment, install dependencies, configure environment variables (e.g., DATABASE_URL, REDIS_HOST, SSH_API_URL), create the PostgreSQL database, run Alembic migrations, and start the server with uvicorn app.main:app. Once running, access the interactive API documentation at http://localhost:8000/api/v1/docs.

Key features of SSH MCP Server

• Inventory of network devices with metadata and grouping
• Execute show commands via SSH API, scheduled or concurrently
• Command templating with variable substitution
• Parse command output into structured data and store history
• Detect changes in device configurations and states
• Generate reports in HTML, JSON, CSV with scheduled distribution

Use cases of SSH MCP Server

• Centralized inventory tracking of network switches by role and location
• Automated periodic execution of show commands across many devices for monitoring
• Comparing device configurations across time or between devices to detect drift
• Generating compliance reports on device OS versions and configuration baselines
• Scheduling daily or weekly report generation and email distribution to stakeholders

FAQ from SSH MCP Server

What are the runtime dependencies?

Python 3.8+, PostgreSQL 12+, Redis (for the task queue), and an SSH API Service for device communication.

Where is device data stored?

Device inventories, command outputs, and historical data are stored in a PostgreSQL database.

How is authentication handled?

JWT token-based authentication with role-based access control. Device credentials are encrypted at rest.

What transport and API does the server expose?

The server exposes a REST API over HTTPS. Swagger UI and ReDoc documentation are available at /api/v1/docs and /api/v1/redoc.

Are there any known limitations mentioned?

The README does not specify any limitations of the server or the underlying SSH API.