Skip to main content
Glama
Mile-Host

MileHost MCP Server

Official
by Mile-Host
README.md
# MileHost MCP Server
<img width="2560" height="1564" alt="image" src="https://github.com/user-attachments/assets/ca8f435a-7572-461b-9c77-b1e770064e89" />
Это официальный mcp сервер от команды MiLe Host (совместно с lgteamai и Astro Ai)
Исходный код полностью открыт,
Файлы репозитория распространяются по лицензии MIT.


# Чтобы установить, попроси своего ИИ агента 

```пиши это в Claude Code/Antigravity
установи этот mcp https://github.com/Mile-Host/MileHost-MCP"
```

# Ручной вариант, если не хочешь тратить лимиты. (Для Antigravity)
1. Скачай install.py
2. Запусти нажатием или
 ```cmd
python install.py
```
3. Следуй инструкциям.
4. Готово!

# Функции
<img width="2560" height="1564" alt="image" src="https://github.com/user-attachments/assets/b5c3b668-df68-4f4b-979e-4ee7fafc8d7b" />

Создавание файлов,
редактирование файлов,
выполнение команд,
деплой,
и много других...

### Готовы начать? 
<img width="2560" height="1564" alt="image" src="https://github.com/user-attachments/assets/d7f0c56d-6ce0-4588-95d1-5fa43fe6f917" />


Зайдите на mile.host и купите контейнер, далее подключите этот mcp и начните работу в Claude Code!

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