About Ansible MCP Server
Ansible MCP Server, called Homelab MCP Server in its README, is a Python MCP server for homelab infrastructure management. It is intended for users managing systems through AI assistants, with tools for SSH discovery, service deployment, VM and container operations, network mapping, and Ansible and Terraform workflows.
Key features
- 01Discover host hardware and software over SSH
- 02Deploy common services from templates
- 03Manage Proxmox, VMs, and containers
- 04Discover devices and map network topology
- 05Deploy with Ansible and Terraform
- 06Store and reuse SSH and Proxmox credentials
Use cases
- 01Inventory host hardware and installed software
- 02Deploy Jellyfin or Home Assistant
- 03Manage Proxmox VM and container lifecycles
- 04Discover network devices and track topology changes
MCP support
The MCP server exposes infrastructure management tools to compatible clients over stdio, covering host discovery, service installation, VM and container operations, network mapping, and credential management.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEHomelab MCP Server
AI-Powered Homelab Infrastructure Management via the Model Context Protocol
A Python MCP server that enables AI assistants to manage, deploy, and monitor homelab infrastructure. Tools span SSH discovery, VM management, service installation, network topology mapping, Proxmox operations, and credential management.
Key Features
- SSH Discovery -- Gather comprehensive hardware and software information from any system
- Service Installation -- Deploy Jellyfin, Pi-hole, Ollama, Home Assistant, and more from templates
- Proxmox Integration -- Full API access plus community script discovery
- VM/Container Lifecycle -- Deploy, control, and remove Docker and LXD workloads
- Network Mapping -- Discover devices, analyze topology, and track changes
- Terraform and Ansible -- State-managed deployments with drift detection and playbooks
- Credential Management -- Register servers once, connect without re-entering credentials
Quick Start
# Install from PyPI (recommended — no clone needed)
uvx homelab-mcp
# Or clone and run from source
git clone https://github.com/washyu/homelab_mcp.git
cd homelab_mcp
uv sync && uv run python run_server.py
For the full walkthrough (environment variables, MCP client configuration, first tool call), see the Setup Guide.
Documentation
| Guide | Description |
|---|---|
| Setup Guide | From zero to first tool call |
| Tool Reference | All tools with arguments and examples |
| Configuration | Environment variables and CLI options |
| Claude Desktop Setup | Claude Desktop integration guide |
| HTTP Service | REST/OpenAPI mode, endpoints, and error contract |
How It Works
- Setup -- The server generates an SSH key pair on first run (
~/.ssh/mcp_admin_rsa) - Onboard a host -- Use
setup_mcp_adminto create a managed user on the target system - Verify -- Use
verify_mcp_adminto confirm passwordless SSH access - Manage -- Discover hardware, install services, control VMs, and map your network
The server communicates over stdio using the MCP protocol. Connect it to any MCP-compatible client (Claude Desktop, etc.) and interact through natural language.
Credential Management
Store SSH and Proxmox credentials once so the server auto-injects them on every connection:
# Store an SSH credential
homelab-mcp credentials add 192.168.1.10 admin
# Store an SSH key-based credential (stores the key file path in the keyring, not the key)
homelab-mcp credentials add 192.168.1.10 admin --key-path ~/.ssh/id_ed25519
# Store a Proxmox API credential
homelab-mcp credentials add 192.168.1.200 root@pam --type proxmox
# Update an existing credential — `add` is upsert; re-running replaces the stored entry
homelab-mcp credentials add 192.168.1.10 admin
# List stored credentials
homelab-mcp credentials list
homelab-mcp credentials list --type proxmox
# Remove a credential
homelab-mcp credentials remove 192.168.1.10
The CLI provides full CRUD over credentials: add (create/update — upsert), list (read), remove (delete). There is no separate update subcommand — re-running add replaces both the keyring secret and the registry entry's auth type.
Credentials are stored in the OS keyring (libsecret on Linux, Keychain on macOS). When the OS keyring is unavailable (headless servers), credentials fall back to environment variables.
See Credentials CLI reference for full documentation.
MCP Client Configuration
From PyPI (uvx) — recommended:
{
"mcpServers": {
"homelab": {
"command": "uvx",
"args": ["homelab-mcp"]
}
}
}
From source clone:
{
"mcpServers": {
"homelab": {
"command": "uv",
"args": ["run", "python", "run_server.py"],
"cwd": "/path/to/homelab_mcp"
}
}
}
Development
# Install with dev dependencies
uv sync --group dev
# Run tests (unit only, no Docker required)
uv run pytest tests/ -m "not integration"
# Code quality
uv run ruff check src/ tests/
uv run mypy src/
See DEPLOYMENT.md for production deployment details.
Project Structure
src/homelab_mcp/
server.py # MCP server with JSON-RPC protocol
tool_schemas/ # Tool definitions (8 schema files)
tool_annotations.py # MCP annotation hints per tool
ssh_tools.py # SSH discovery and hardware detection
service_installer.py # Service installation framework
infrastructure_crud.py # Infrastructure lifecycle management
vm_operations.py # VM/container operations
sitemap.py # Network topology mapping
database.py # SQLite device tracking
error_handling.py # Centralized error handling
credential_store.py # OS keyring credential storage
log_filter.py # Credential redaction for log output
prompt_registry.py # MCP prompts registry
resource_readers.py # MCP resource read handlers
service_templates/ # YAML service definitions
tests/ # Unit and integration tests
docs/ # Full documentation
Acknowledgments
Proxmox community script integration powered by community-scripts/ProxmoxVE (MIT License).
Contributing
- Fork the repository
- Create a feature branch
- Write tests for new functionality
- Ensure all tests pass
- Submit a pull request
License
MIT License -- see LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.