VPS MCP Server
# MCP Server para Gerenciamento Portainer
Servidor MCP (Model Context Protocol) que permite ao modelo de IA gerenciar containers Docker através da API do Portainer.
## 📋 Visão Geral
Este projeto implementa um MCP Server que expõe ferramentas para gerenciar:
- **Containers**: listar, criar, iniciar, parar, remover, inspecionar
- **Imagens**: listar, pull, remover, inspecionar
- **Networks**: listar, criar, remover
- **Volumes**: listar, criar, remover
- **Configuração**: definir/obter credenciais do Portainer
## 🚀 Quick Start
```bash
# Clonar o repositório
git clone https://github.com/onlitec/VPS-MCP-SERVER.git
cd VPS-MCP-SERVER
# Instalar dependências
npm install
# Configurar variáveis de ambiente
cp .env.example .env
# Editar .env com suas credenciais do Portainer
# Build
npm run build
# Testar conexão
npm run test:connection
```
## 📚 Documentação
- [**Antigravity Setup**](docs/ANTIGRAVITY_SETUP.md) - Como instalar no Antigravity IDE
- [Setup Guide](docs/SETUP.md) - Guia de instalação e configuração
- [Architecture](docs/ARCHITECTURE.md) - Arquitetura do sistema
- [API Reference](docs/API_REFERENCE.md) - Referência completa das ferramentas MCP
- [Install Node.js](docs/INSTALL_NODEJS.md) - Como instalar Node.js
## 🔧 Requisitos
- Node.js 18+
- Acesso a uma instância Portainer
- Chave de API do Portainer
## 📝 Licença
MIT
TDQS
Scored across 21 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific Docker/Portainer resources (containers, images, networks, volumes, Portainer config) and actions (create, get, list, remove, start/stop/restart), making it easy for an agent to select the correct one. For example, 'create_container' vs 'start_container' serve different lifecycle stages.
All tool names follow a consistent verb_noun pattern using snake_case throughout. Verbs like create, get, list, remove, start, stop, restart, pull, test, and set are applied predictably to nouns like container, image, network, volume, and portainer_config. There are no deviations in naming conventions.
With 21 tools, the count is slightly high but reasonable for the server's purpose of managing Docker and Portainer operations. It covers a comprehensive set of actions across multiple resource types, though it might feel heavy compared to a more minimal set. Each tool earns its place by addressing a specific need in container management.
The tool surface provides complete CRUD/lifecycle coverage for Docker resources (containers, images, networks, volumes) and Portainer configuration. It includes creation, retrieval, listing, removal, and operational controls (start/stop/restart), with no obvious gaps. The Portainer tools handle connection testing and configuration, ensuring agents can manage the full workflow.