MileHost MCP Server
OfficialRelated Servers
Alternatives to MileHost MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to run shell commands, spawn persistent background tasks, and read/write files inside isolated remote container sandboxes on a VPS. It also provides project workspace listing, task attach/kill controls, and a searchable knowledge graph for memory continuity across sessions.-
- AlicenseAqualityBmaintenanceEnables AI coding agents to safely execute commands, run tests, and modify project files inside disposable, policy-enforced Docker sandboxes that are isolated from the host machine and its credentials.15MIT
- FlicenseNot gradedqualityDmaintenanceProvisions Docker-based development environments on demand, allowing AI agents to create, manage, and inspect containerized dev environments without manual setup.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to work in a persistent, isolated Linux workspace with file management, Bash execution, SSH/SFTP access, and durable storage while keeping workloads contained from the host and private networks.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to operate a persistent Linux sandbox in the cloud, running commands, managing files, using Git, and publishing artifacts through a Streamable HTTP MCP endpoint.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform DevOps tasks including Kubernetes management, cloud provider operations, CI/CD, security scanning, and infrastructure monitoring through natural language.MIT
TDQS
Scored across 24 tools
Many tools are exact duplicates or near-identical: list_servers and list_folders share the same description, three tools execute commands in the container, and multiple tools create/write/deploy files. Agents cannot reliably distinguish tool purposes, so misselection risk is very high.
Names mix snake_case and kebab-case inconsistently, e.g. milehost_run_command vs milehost-run-command and clear_session vs clear-session. Even identical operations appear under multiple naming conventions, so there is no predictable pattern.
At 24 tools the list is heavily padded by duplicates such as three reboot variants, three command executors, and multiple file-writing tools. The actual distinct surface is roughly 10 tools, so the count is inflated and should be consolidated.
The underlying domain of remote container management is well covered: connect, list resources, run commands, clear sessions, restart/reboot, file CRUD, and self-update are all present. Minor gaps like dedicated log or process status tools exist, but command execution and file reads can compensate.