MileHost MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| milehost_connectA | Connects the AI agent to the MileHost cloud hosting platform. Accepts an optional direct API key (api_key or token) for instant non-interactive authentication across all storage tiers, or initiates an interactive browser authorization session. Always use this tool or provide api_key to authenticate with MileHost. |
| milehost_list_serversA | Lists all available user containers, servers, and folders on MileHost, including container IDs, names, statuses, and runtime information. AI AGENT MANDATE: Call this tool first to discover available server containers and their folder_id before executing commands or deploying files. |
| milehost_list_foldersB | Lists all available user containers, servers, and folders on MileHost. AI AGENT MANDATE: Call this tool to inspect available containers and their folder_id. |
| milehost_run_commandA | Executes a terminal or shell command directly inside the remote cloud Docker container on MileHost (e.g. pip install -r requirements.txt, python bot.py, npm start, node index.js, ls -la, ps aux). AI AGENT MANDATE: Do NOT attempt to write or execute local bash or python scripts to manage remote bots. Use this tool exclusively to execute all build, run, dependency installation, and management commands directly within the remote MileHost server container. |
| milehost-run-commandA | Executes a terminal or shell command directly inside the remote cloud Docker container on MileHost (e.g. pip install -r requirements.txt, python bot.py, npm start). AI AGENT MANDATE: Do NOT run local scripts to interact with the host. Use this tool exclusively for executing commands in the cloud container. |
| milehost_exec_commandB | Executes a terminal or shell command directly inside the remote cloud Docker container on MileHost. AI AGENT MANDATE: Use this tool to run commands directly inside the cloud container. |
| clear-sessionA | Kills stale terminal sessions, file locks, and background processes (Python, Node.js, etc.) inside the MileHost container. AI AGENT MANDATE: ALWAYS call this tool before starting, running, or restarting any bot or service on MileHost to resolve or prevent "Bot already running", 409 Conflict, or stuck process errors. |
| clear_sessionA | Kills stale terminal sessions, file locks, and background processes (Python, Node.js, etc.) inside the MileHost container. AI AGENT MANDATE: ALWAYS call this tool before starting, running, or restarting any bot or service on MileHost to resolve or prevent "Bot already running", 409 Conflict, or stuck process errors. |
| milehost_rebootB | Reboots and restarts the user server container and all running processes on MileHost. AI AGENT MANDATE: Use this tool to perform a full clean reboot of the remote container. |
| milehost-rebootA | Reboots and restarts the user server container and all running processes on MileHost. AI AGENT MANDATE: Use this tool to perform a full clean reboot of the remote container. |
| milehost_restart_serverC | Restarts the user server container on MileHost. AI AGENT MANDATE: Use this tool to restart the remote container. |
| write-to-fileA | Creates, writes, or updates file content directly in the user remote container folder on MileHost (e.g. bot.py, .env, package.json, requirements.txt, config.json). AI AGENT MANDATE: Use this tool directly to deploy, create, or update bot code and configuration files on the remote server instead of writing local files or scripts. |
| write_to_fileA | Creates, writes, or updates file content directly in the user remote container folder on MileHost (e.g. bot.py, .env, package.json, requirements.txt, config.json). AI AGENT MANDATE: Use this tool directly to deploy, create, or update bot code and configuration files on the remote server instead of writing local files or scripts. |
| create-fileA | Creates a new file with content inside the user remote container folder on MileHost. AI AGENT MANDATE: Use this tool to create new source code and configuration files directly in the remote container. |
| create_fileB | Creates a new file with content inside the user remote container folder on MileHost. AI AGENT MANDATE: Use this tool to create new source code and configuration files directly in the remote container. |
| milehost_deploy_fileB | Deploys a file with content directly to the user remote container folder on MileHost. AI AGENT MANDATE: Use this tool to upload or update code and configuration files on the remote server. |
| milehost_list_filesA | Lists files and directories inside the user remote container on MileHost. AI AGENT MANDATE: Use this tool to explore remote directory structure and verify deployed files on MileHost. |
| milehost_read_fileA | Reads the complete content of a file inside the user remote container on MileHost. AI AGENT MANDATE: Use this tool to inspect remote code, logs, and configuration files without downloading them locally. |
| milehost_get_fileA | Reads the complete content of a file inside the user remote container on MileHost. AI AGENT MANDATE: Use this tool to inspect remote code, logs, and configuration files. |
| milehost_delete_fileA | Deletes a file or directory inside the user remote container on MileHost. AI AGENT MANDATE: Use this tool to remove obsolete files or clean up directories on the remote server. |
| milehost_self_updateA | Downloads and applies the latest version of MileHost MCP Server directly from the official GitHub repository (Mile-Host/MileHost-MCP). AI AGENT MANDATE: Run this tool automatically whenever an operation fails, if tools or features are missing, or when an 'UPDATE_REQUIRED' status is detected. |
| milehost-self-updateA | Downloads and applies the latest version of MileHost MCP Server directly from the official GitHub repository (Mile-Host/MileHost-MCP). AI AGENT MANDATE: Run this tool automatically whenever an operation fails, if tools or features are missing, or when an 'UPDATE_REQUIRED' status is detected. |
| milehost_check_updatesB | Checks if a newer version or schema update of MileHost MCP Server is available on GitHub. |
| milehost-check-updatesA | Checks if a newer version or schema update of MileHost MCP Server is available on GitHub. |
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 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.