Model Context Protocol (MCP) servers for managing homelab infrastructure through Claude Desktop.
Most browser automation work still happens through a UI a human drives. Homelab MCP MCP server moves it into the conversation instead. Model Context Protocol (MCP) servers for managing homelab infrastructure through Claude Desktop.
FastMCP is a lightweight framework that: - ✅ Reduces server code by 38% (1,754 lines eliminated) - ✅ Uses simple decorator pattern (@mcp.tool()) for tool definitions - ✅ Includes comprehensive tool annotations for behavioral hints - ✅ Adds support for HTTP and SSE transports (in addition to stdio) - ✅ Auto-generates schemas from Python type hints - ✅ Improves code maintainability and makes adding new servers easier
The server publishes 14 tools. What each one is for:
mcp-registry — inspector not available (deprecated)Web — based integrationsMulti — client scenariosReal — time monitoring applicationsBrowser — based integrationsEvent — driven architecturesWindows — %APPDATA%\Claude\claude_desktop_config.jsonmacOS — ~/Library/Application Support/Claude/claude_desktop_config.jsonLinux — ~/.config/Claude/claude_desktop_config.jsonlatest — Latest stable release from main branch (recommended)edge — Latest development build from main branchmain — - Specific commit builds for traceability (e.g., main-17bae01)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: ANSIBLE_INVENTORY_PATH, CLAUDE_CONFIG_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Homelab MCP's toolset — mcp-registry, Web, Multi and 11 more — is a fair guide to whether it matches your workflow. It is maintained by bjeans; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| mcp-registry | inspector not available (deprecated) |
| Web | based integrations |
| Multi | client scenarios |
| Real | time monitoring applications |
| Browser | based integrations |
| Event | driven architectures |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
| latest | Latest stable release from main branch (recommended) |
| edge | Latest development build from main branch |
| main | <git-sha> - Specific commit builds for traceability (e.g., main-17bae01) |
| Performance | ** Enums generate once at startup - minimal impact even with large inventories (100+ hosts) |
| get_claude_config | View Claude Desktop MCP configuration |
{
"mcpServers": {
"homelab-unified": {
"command": "python",
"args": ["C:\\Path\\To\\Homelab-MCP\\homelab_unified_mcp.py"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ANSIBLE_INVENTORY_PATH | Filesystem location the server is allowed to use. | Optional |
| CLAUDE_CONFIG_PATH | Filesystem location the server is allowed to use. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.