Homelab MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOMELAB_CONFIG_FILE | No | Path to the homelab configuration file. If not set, the server will check for config files in default locations: ./homelab.config.json, ~/.config/homelab-mcp/config.json, or ~/.homelab-mcp.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| homelabA | Unified homelab Docker management tool. ACTIONS: container - Container operations list - List containers with filters start/stop/restart - Control container state pause/unpause - Pause/unpause container logs - Get container logs stats - Get resource usage stats inspect - Get detailed container info search - Search containers by query pull - Pull latest image for container recreate - Recreate container with latest image compose - Docker Compose operations list - List compose projects status - Get project status up/down/restart - Control project state logs - Get project logs build - Build project images pull - Pull project images recreate - Force recreate containers host - Host operations status - Check host connectivity resources - Get CPU/memory/disk via SSH docker - Docker daemon operations (host parameter required) info - Get Docker system info df - Get disk usage prune - Remove unused resources image - Image operations list - List images pull - Pull an image build - Build from Dockerfile remove - Remove an image scout - Remote file operations via SSH read - Read file content list - List directory contents tree - Show directory tree exec - Execute command find - Find files by pattern transfer - Transfer file between hosts diff - Diff files across hosts EXAMPLES: { action: "container", subaction: "list", state: "running" } { action: "container", subaction: "restart", container_id: "plex" } { action: "compose", subaction: "up", host: "tootie", project: "plex" } { action: "host", subaction: "resources", host: "tootie" } { action: "docker", subaction: "info", host: "tootie" } { action: "docker", subaction: "df", host: "tootie" } { action: "docker", subaction: "prune", host: "tootie", prune_target: "images", force: true } { action: "image", subaction: "pull", host: "tootie", image: "nginx:latest" } { action: "scout", subaction: "read", host: "tootie", path: "/etc/hosts" } { action: "scout", subaction: "list", host: "tootie", path: "/var/log" } { action: "scout", subaction: "exec", host: "tootie", path: "/tmp", command: "ls -la" } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
The single tool 'homelab' has clearly distinct subactions organized by resource type (container, compose, host, docker, image, scout), each with specific operations that don't overlap. Subactions like 'list', 'start', 'logs' are unambiguous within their categories.
All subactions follow a consistent verb_noun pattern (e.g., 'list', 'start', 'logs', 'inspect') across all categories. The naming is uniform with clear, descriptive verbs that match their functions without mixing conventions.
With only 1 tool, the server feels under-scoped for its broad domain of homelab Docker management. The single tool bundles multiple distinct functionalities (container management, compose operations, host monitoring, etc.) that might be better served as separate tools for clarity and modularity.
The tool provides comprehensive coverage for Docker and homelab management, including CRUD-like operations for containers, images, and compose projects, plus host monitoring and remote file operations. Minor gaps might include advanced features like container networking or volume management, but core workflows are well-covered.