Skip to main content
Glama
Mile-Host

MileHost MCP Server

Official
by Mile-Host

Related Servers

Alternatives to MileHost MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      15
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provisions Docker-based development environments on demand, allowing AI agents to create, manage, and inspect containerized dev environments without manual setup.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    TDQS

    C2.9/5.0

    Scored across 24 tools

    Disambiguation1/5

    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.

    Naming Consistency1/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues