Skip to main content
Glama
easypanel-mcp-server

easypanel-mcp-server

easypanel-mcp-server

MCP Server for full Easypanel control via Claude Code, Cursor and Claude Desktop.

npm version License: MIT GitHub Stars GitHub Forks GitHub Issues CI Glama Quality

TypeScript Node.js MCP Claude Code Cursor Claude Desktop

Instagram YouTube LinkedIn Buy Me A Coffee Strat Academy


What is this

easypanel-mcp-server connects Claude Code, Cursor and Claude Desktop directly to your Easypanel instance — a modern Docker-based server control panel — through the Model Context Protocol.

Instead of switching between your editor and the Easypanel dashboard, you control everything from inside Claude: deploy from GitHub, update env vars, read live logs, exec into containers, manage domains, databases, volumes and ports, set resource limits, run Docker maintenance and monitor your server — all in natural language.

It maps the Easypanel API to 57 typed tools across 15 categories, plus a single easypanel_raw escape hatch that reaches any of Easypanel's ~375 API operations for everything not covered by a dedicated tool. It speaks all three API generations — the tRPC API of panels ≤ 2.30, the RPC layer of 2.31–2.32, and the public API introduced in Easypanel 2.33 — auto-detecting which one your panel uses. Every destructive action is gated behind an explicit confirmation, every response opens with a context banner so Claude always knows what it is touching, and an optional read-only mode lets you connect safely to a production panel.

📖 API reference: docs/easypanel-api.md — architecture, the API generations, confirmed operations mapped tool-by-tool, and how to discover new ones.


Related MCP server: easypanel-mcp

Compatibility

Easypanel changed its API twice in quick succession:

  • 2.31 replaced the internal tRPC API with an RPC layer (/api/rpc/*). On panels ≥ 2.31, every v1.x call that carries parameters fails with 400 Input validation failed.

  • 2.33 shipped a documented public API (/api/<operation>, GET for reads, POST for writes) and stated that the old internal API "may change without notice and should not be relied upon". v3 targets the public API on those panels.

Your Easypanel version

Use

any (recommended)

easypanel-mcp-server@latest (v3.x) — auto-detects the generation, works on all three

≤ 2.30.x only, pinned

easypanel-mcp-server@legacy (v1.3.x) — frozen tRPC-only line, last validated against v2.30.1

v3 detects the generation with a single probe request on first call (cached) and logs the panel version to stderr. To skip detection, set EASYPANEL_API_FLAVOR to trpc (≤ 2.30), rpc (2.31–2.32) or public (≥ 2.33).

Upgrading from v2? If you pinned EASYPANEL_API_FLAVOR=rpc to work around the 2.32 issues, remove it — otherwise the client stays on the internal API that Easypanel now declares unstable.

This MCP vs. Easypanel's built-in MCP

Easypanel 2.33 also ships its own MCP endpoint (/api/mcp, connection details next to your API key). It's a thin wrapper over the public API. This server is a different trade-off:

Easypanel built-in MCP

easypanel-mcp-server

Runtime container logs

—

✅ via /ws/serviceLogs (no Loki/licence needed)

Exec inside a container

—

✅ exec_in_container with destructive-command gate

Live Docker events

—

✅ get_docker_events

Read-only mode

—

✅ MCP_ACCESS_MODE=readonly blocks every write at the source

Confirmation gate on destructive ops

—

✅ confirm: "CONFIRMO"

Secret masking on every tool response

—

✅ env values, passwords, tokens, deploy-webhook token, credentials in URLs

Env var read-modify-write

—

✅ never clobbers other variables

Connection-string building

—

✅ inspect_database

Coverage of every API operation

✅

✅ via easypanel_raw

Zero install

✅

needs npx/node

Using both at once is fine — they don't conflict.


Prerequisites

  • Easypanel instance running and accessible

  • API token — generate at Easypanel → Settings → API → Generate Token

  • Node.js ≥ 18 and Claude Code, Cursor or Claude Desktop


Quick start

Option A — npx (no install needed)

Add .mcp.json to your project root:

{
  "mcpServers": {
    "easypanel-mcp": {
      "command": "npx",
      "args": ["-y", "easypanel-mcp-server"],
      "env": {
        "EASYPANEL_URL": "https://your-panel.example.com",
        "EASYPANEL_TOKEN": "your-api-token"
      }
    }
  }
}

Option B — local build

git clone https://github.com/helbertparanhos/easypanel-mcp-server
cd easypanel-mcp-server
npm install && npm run build
{
  "mcpServers": {
    "easypanel-mcp": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/easypanel-mcp-server/dist/index.js"],
      "env": {
        "EASYPANEL_URL": "https://your-panel.example.com",
        "EASYPANEL_TOKEN": "your-api-token"
      }
    }
  }
}

Cursor — reuse env vars across projects

In Cursor Settings → Tools & MCPs → Environment Variables, set:

  • EASYPANEL_URL = https://your-panel.example.com

  • EASYPANEL_TOKEN = your-api-token

Then your .cursor/mcp.json uses references that apply automatically to every project:

{
  "mcpServers": {
    "easypanel-mcp": {
      "command": "npx",
      "args": ["-y", "easypanel-mcp-server"],
      "env": {
        "EASYPANEL_URL": "${EASYPANEL_URL}",
        "EASYPANEL_TOKEN": "${EASYPANEL_TOKEN}"
      }
    }
  }
}

Environment variables

Variable

Required

Default

Description

EASYPANEL_URL

✅

—

Panel URL, no trailing slash (e.g. https://panel.example.com)

EASYPANEL_TOKEN

✅

—

API token (Easypanel → Settings → API → Generate Token)

MCP_ACCESS_MODE

—

full

Set to readonly to block all writes (curated tools and easypanel_raw). Reads stay available — ideal for connecting to a production panel for inspection only.

EASYPANEL_API_FLAVOR

—

(auto)

Force the panel's API generation instead of auto-detecting: trpc (≤ 2.30), rpc (2.31–2.32) or public (≥ 2.33). Aliases: legacy / modern. Leave unset unless you have a reason — a stale rpc pin keeps a 2.33 panel on the internal API.

EASYPANEL_RAW_DISABLED

—

(enabled)

Set to 1 to fully disable the easypanel_raw escape hatch. Recommended when the MCP is exposed to untrusted content (prompt-injection risk), since easypanel_raw reads are not covered by read-only mode and secret masking is best-effort (by name and shape).


Adding context to a project

Place this in your project's CLAUDE.md so Claude knows which Easypanel project and service it should operate on by default:

## Easypanel
Project: `my-project` | Service: `my-api` | Branch: `main`
Repo: `owner/repo`

No folder copying needed — one MCP install serves all your projects.


Use cases

"Deploy my app" — Claude lists projects, inspects the current service, triggers deploy_service, then watches list_actions until it completes.

"Why is my service down?" — Claude calls get_service_error, get_service_logs and get_build_logs, and can exec_in_container to inspect files/env live.

"Add DATABASE_URL to staging" — Claude reads current env vars with get_env_vars, adds only the new key with set_env_var (never wipes others), and reminds you to redeploy.

"Give this service 512MB and half a core" — Claude calls set_service_resources (reads current limits and merges your change) and reminds you to restart.

"Persist /app/data and expose port 5432" — Claude calls create_mount (named volume) and create_port, both applied on the next deploy.

"My disk is full" — Claude runs get_storage_stats, then cleanup_docker_images or prune_docker (with confirmation) to reclaim space.

"Show me the Traefik dashboard config" — for anything without a dedicated tool, Claude uses easypanel_raw to call the procedure directly.


Available tools (57)

Category

Tools

Projects

list_projects, get_project, create_project, delete_project ⚠️

Services

inspect_service, create_service, rename_service ⚠️, destroy_service ⚠️, deploy_service, start_service, stop_service ⚠️, restart_service, get_service_error, get_exposed_ports, get_service_notes, set_service_notes, set_service_resources

Deploy / GitHub

set_source_github, set_source_image, enable_github_deploy, disable_github_deploy, list_actions, get_action

Env Vars

get_env_vars, set_env_var, delete_env_var ⚠️

Logs

get_service_logs, get_build_logs, get_system_stats

Containers

list_containers, exec_in_container ⚠️, get_docker_events

Domains

list_domains, add_domain, remove_domain ⚠️, set_primary_domain

Databases

create_database, inspect_database, destroy_database ⚠️

Volumes / Mounts

list_mounts, create_mount ⚠️

Ports

list_ports, create_port ⚠️

Compose

create_compose, inspect_compose, deploy_compose

Monitoring

get_docker_stats, get_storage_stats, get_service_stats

Maintenance

prune_docker ⚠️, cleanup_docker_images

Server / Infra

list_users, list_certificates, list_nodes, restart_panel ⚠️, reboot_server ⚠️

Raw access

easypanel_raw ⚠️

⚠️ = requires confirm: "CONFIRMO". For exec_in_container, create_mount, create_port and easypanel_raw the confirmation is conditional (only for destructive commands, sensitive host-path bind mounts, privileged ports < 1024, and writes respectively).

Full tool descriptions with parameters are in llms.txt. For the underlying API (all generations), see docs/easypanel-api.md.

easypanel_raw — reach any of the ~375 operations

Covering every Easypanel operation with a typed tool isn't practical, so anything without a dedicated tool is reachable directly:

// read (default) — flat name, as documented in your panel's /api/openapi.json
{ "procedure": "listCertificates" }
{ "procedure": "getPanelDomain" }
{ "procedure": "listVolumeBackups", "input": { "projectName": "app", "serviceName": "api" } }

// the old dot notation still works and is translated
{ "procedure": "certificates.listCertificates" }

// write — requires isMutation:true AND confirm:"CONFIRMO"
{ "procedure": "setLogoSettings", "input": { /* ... */ },
  "isMutation": true, "confirm": "CONFIRMO" }

Areas only reachable via easypanel_raw: Traefik, branding, Cloudflare Tunnel, Box, middlewares, notifications, volume/database backups, WordPress, storage providers, Docker builders, Git keys, cluster and update management. To discover names, read GET <your-panel>/api/openapi.json.

The client classifies each operation against the panel's own OpenAPI spec, fail-closed: a read only executes if the spec says it's a read, so writes can't sneak past readonly mode or the confirmation gate — and the reverse is caught too (calling a read with isMutation:true is refused with a clear message). On 2.33+ that classification is exact, since the public API declares GET for reads and POST for writes. On 2.31 it's the documented HTTP method; on 2.32, where the spec is POST-only and carries no such marker, the client falls back to the panel's naming convention (get/list/inspect/check/query/search = read, anything else = write), restricted to operations present in the spec.

One deliberate exception: on 2.33+ the panel validates query params without type coercion, so ?limit=5 arrives as the string "5" and is rejected. Whenever an input carries a non-string value, the client routes that read through the internal /api/rpc transport (which sends JSON in the body) and logs the reason to stderr. The read/write classification still comes from the spec first, so the guard is unaffected.


Safety features

Context banner

Every response that touches a specific project/service starts with:

[Contexto ativo: projeto="my-project" | serviço="my-api"]

Claude always knows what it is modifying before taking any action.

Confirmation guard

Destructive or production-impacting actions return BLOQUEADO until they receive confirm: "CONFIRMO":

{
  "status": "BLOQUEADO",
  "acao": "stop_service",
  "alvo": "serviço \"api\" (usuários perderão acesso)",
  "instrucao": "Para confirmar, passe o parâmetro: confirm: \"CONFIRMO\"",
  "aviso": "⚠️  Esta ação pode ser IRREVERSÍVEL. Confirme apenas se tiver certeza."
}

This gates project/service deletion, stop/rename, env/domain removal, database destruction, the global server ops (prune_docker, restart_panel, reboot_server), and — conditionally — dangerous container commands, sensitive bind mounts, privileged ports and raw mutations.

Read-only mode

Set MCP_ACCESS_MODE=readonly to block every write at the source (client.mutate), covering both curated tools and easypanel_raw. Reads remain available — perfect for a production panel you only want to inspect.

Raw escape-hatch controls

easypanel_raw validates the operation name (flat or namespace.procedure, no path/query injection), requires the input to be an object (≤ 50KB), and demands CONFIRMO for any mutation. Set EASYPANEL_RAW_DISABLED=1 to turn it off entirely.

User redaction

list_users strips apiToken, twoFactorSecret and password fields before returning — only id, email, admin, twoFactorEnabled and createdAt reach the model.

Safe env vars (read-modify-write)

set_env_var and delete_env_var read the current state, apply only the requested change, and write back. The Easypanel API replaces the entire env string on every update — without this protection it is easy to accidentally wipe all variables at once.

Secret masking on every response

Every tool result — including easypanel_raw — goes through one central masking step (src/mascarar.ts) before it reaches the model. Masked values become ***, with nothing of the original kept:

  • Fields with a sensitive name, at any depth — secret, password/pwd/pass, token, key, credential, private, auth, pepper, salt, cookie, webhook, deploymentUrl/deployUrl. Everything under such a field is masked (booleans/null are kept); { key: "X_SECRET", value: "..." } pairs mask the value.

  • The deploy-webhook token in any string: …/api/deploy/<token> → …/api/deploy/***.

  • Env as text (KEY=value per line, the way Easypanel stores it, plus compose KEY: value / - KEY=value and inline -e KEY=value / ?api_key=): the value is masked when the key is sensitive.

  • Credentials embedded in URLs — postgres://user:pass@host/db, https://user:token@github.com/... (env values, git sources, connection strings) → postgres://***@host/db. Scheme, host, port and path stay.

  • Bearer <token> and PEM PRIVATE KEY blocks.

Names, images, domains, ports, replicas and other non-sensitive fields pass through untouched. Masking is best-effort: a secret stored under an innocent name (FOO=abc) with no recognisable shape is not caught.

Explicit exceptions, for calls whose purpose is to reveal: get_env_vars with include_values: true and inspect_database with include_secrets: true (both strictly the boolean true).

Token never leaks

HTTP errors and WebSocket failures are logged to stderr and surfaced to the model as a generic message — the bearer token (sent in the WebSocket query string, as Easypanel requires) never reaches the model context.

Input validation

projectName / serviceName are validated against ^[a-z0-9][a-z0-9_-]*$ before being used to build a Docker service name or WebSocket query (defense-in-depth against target confusion / parameter injection). Ports are validated as integers 1–65535; resource values must be positive numbers.


Companion skill /ep

Install the workflow skill for guided deploy operations in Claude Code:

mkdir -p ~/.claude/skills/ep
cp skill/SKILL.md ~/.claude/skills/ep/SKILL.md

Then use /ep for an interactive deploy workflow without needing to remember tool names.


How it works

The Easypanel panel talks to its backend over tRPC (/api/trpc/<router>.<procedure>), not a public REST API. This server uses the same endpoints:

  • Reads are tRPC queries; writes are tRPC mutations — see docs/easypanel-api.md.

  • Live logs, container exec and Docker events use the panel's WebSocket channels (/ws/serviceLogs, /ws/containerShell, /ws/dockerEvents) — the same ones the UI uses — so they work without the licensed Advanced Logs (Loki).

  • A few input schemas (mounts, ports, resources) were validated against a live Easypanel and are documented in the API reference.


Known limitations

  • WordPress / Box service types — not exposed as dedicated tools; reach them via easypanel_raw (e.g. inspectWordPressService, createBoxService).

  • easypanel_raw reads bypass read-only mode — read-only blocks writes only. A raw read can return sensitive data; use EASYPANEL_RAW_DISABLED=1 in untrusted environments.

  • Cluster tools — list_nodes returns the local node only on single-server setups (no Swarm cluster).

  • Docker events are real-time only (no history) — an idle server may return an empty window.


Testing without Claude

npx @modelcontextprotocol/inspector dist/index.js

Opens a browser UI where you can call any tool manually and inspect the response.


Comparison with similar packages

Feature

easypanel-mcp-server

easypanel-mcp (sitp2k)

Curated tools

57

~15

Raw access to all ~375 API operations

✅ (easypanel_raw)

❌

Auth method

Bearer token

Email + password

Confirmation guard

✅

❌

Read-only mode

✅

❌

Container exec + live logs (WebSocket)

✅

❌

Volumes / ports / compose / resources

✅

❌

Server maintenance (prune / reboot)

✅

❌

Safe env update (read-modify-write)

✅

❌

Secret redaction & value masking

✅

❌

Companion Claude skill

✅

❌

Known limitations documented

✅

❌


🤝 Contributing

Contributions are welcome! See CONTRIBUTING.md for how to add tools, report bugs and open PRs.


👤 Author

Created by Helbert Paranhos from Strat Academy.

Instagram YouTube LinkedIn Buy Me A Coffee

If this project was useful, consider giving it a ⭐ and following Strat Academy for more AI automation content.


📄 License

MIT © Helbert Paranhos / Strat Academy

See LICENSE for details.

Available Tools

57 tools
add_domainB

Adiciona um domínio customizado ao serviço com HTTPS automático via Let's Encrypt.

Inputs: host (required), port (required), projectName (required), serviceName (required), +2 more.

cleanup_docker_imagesA

Remove do servidor apenas as imagens Docker não utilizadas (dangling/sem container), liberando espaço sem mexer em containers, redes ou volumes. Operação mais leve e segura que prune_docker — imagens podem ser recriadas em um novo deploy. Escopo global do servidor.

Inputs: no named parameters.

create_composeA

Cria um serviço do tipo Docker Compose em um projeto. Depois use set_compose_file (via easypanel_raw) ou o painel para definir o docker-compose, e deploy_compose para subir.

Inputs: projectName (required), serviceName (required).

create_databaseA

Cria um serviço de banco de dados (Postgres, MySQL, MariaDB, MongoDB ou Redis) em um projeto.

Inputs: type (required), projectName (required), serviceName (required), password.

create_mountA

Adiciona um volume/mount a um serviço para persistir dados entre deploys. Use type 'volume' para volume nomeado gerenciado, 'bind' para mapear um caminho do host. Aplica no próximo deploy.

Inputs: type (required), mountPath (required), projectName (required), serviceName (required), +3 more.

create_portA

Publica uma porta de um serviço no host (port mapping), expondo-a externamente sem passar pelo proxy/domínio. Útil para TCP/UDP brutos (bancos, jogos, etc). Aplica no próximo deploy. ⚠️ Portas privilegiadas (publishedPort < 1024, ex: 80/443/22) exigem confirm: "CONFIRMO".

Inputs: targetPort (required), projectName (required), serviceName (required), publishedPort (required), +2 more.

create_projectB

Cria um novo projeto no Easypanel.

Inputs: projectName (required).

create_serviceA

Cria um novo serviço de app em um projeto. Após criar, configure a source com set_source_github ou set_source_image.

Inputs: projectName (required), serviceName (required).

delete_env_varA

⚠️ Remove UMA variável de ambiente. Lê estado atual antes de escrever. Requer confirm: "CONFIRMO".

Inputs: key (required), confirm (required), projectName (required), serviceName (required).

delete_projectA

⚠️ DESTRUTIVO — Remove permanentemente o projeto e TODOS os seus serviços e dados. Irreversível. Requer confirm: "CONFIRMO".

Inputs: confirm (required), projectName (required).

deploy_composeC

Dispara o deploy (docker compose up) de um serviço Compose com a configuração atual.

Inputs: projectName (required), serviceName (required).

deploy_serviceA

Dispara o deploy do serviço com a configuração atual. Usa o source configurado (GitHub, image, dockerfile). Funciona para serviços app E compose — detecta o tipo e roteia para o namespace certo (não precisa saber de antemão se é compose).

Inputs: projectName (required), serviceName (required).

destroy_databaseA

⚠️ DESTRUTIVO — Remove o banco de dados e TODOS os seus dados permanentemente. Irreversível. Requer confirm: "CONFIRMO".

Inputs: type (required), confirm (required), projectName (required), serviceName (required).

destroy_serviceA

⚠️ DESTRUTIVO — Remove permanentemente o serviço e seus dados. Irreversível. Requer confirm: "CONFIRMO".

Inputs: confirm (required), projectName (required), serviceName (required).

disable_github_deployA

Desativa o auto-deploy via GitHub. Deploys precisarão ser disparados manualmente.

Inputs: projectName (required), serviceName (required).

easypanel_rawA

Chama diretamente qualquer operação da API do Easypanel (~375) não coberta pelas tools dedicadas. Use para recursos avançados: Traefik, branding, Cloudflare Tunnel, Box, WordPress, backups de volume/banco, notificações, storage providers, etc. Leitura (isMutation=false) é o padrão. ⚠️ Reads podem retornar dados sensíveis (env vars/secrets de qualquer projeto). Para escrita, passe isMutation:true E confirm:"CONFIRMO" — escritas arbitrárias pulam as proteções das tools curadas. Para descobrir os nomes disponíveis, leia GET /api/openapi.json.

Inputs: procedure (required), input, confirm, isMutation.

enable_github_deployA

Ativa o auto-deploy via GitHub: a cada push no branch configurado, um deploy é disparado automaticamente.

Inputs: projectName (required), serviceName (required).

exec_in_containerA

Executa um comando dentro do container de um serviço e retorna a saída (stdout/stderr). Use para debugar em runtime: inspecionar arquivos, checar variáveis, testar conectividade, rodar migrations, etc. Roda no primeiro container do serviço (ou no containerId informado). ⚠️ Executa comandos arbitrários — comandos potencialmente destrutivos (rm -rf, dd, mkfs, shutdown, kill, pipe para shell, etc.) exigem confirm: "CONFIRMO".

Inputs: command (required), projectName (required), serviceName (required), confirm, +1 more.

get_actionB

Retorna detalhes e logs de uma ação específica (deploy, build, etc).

Inputs: actionId (required).

get_build_logsB

Retorna os logs de build/deploy do último action registrado para o serviço. Use para debugar falhas de build.

Inputs: projectName (required), serviceName (required).

get_docker_eventsA

Captura eventos Docker do servidor em tempo real durante uma janela curta (~8s) — start, stop, kill, die, exec, health_status, etc. Use para investigar reinícios e falhas. Obs: só mostra eventos que ocorrem durante a captura (não há histórico); um servidor ocioso pode retornar vazio.

Inputs: limit.

get_docker_statsA

Retorna o estado das tasks Docker de cada serviço: réplicas em execução (actual) vs desejadas (desired). Use para ver rapidamente o que está no ar, escalado ou caído. Para CPU/memória de um serviço use get_service_stats.

Inputs: no named parameters.

get_env_varsA

Lista as variáveis de ambiente do serviço. Valores de variáveis sensíveis (KEY, SECRET, PASSWORD, TOKEN) são mascarados por padrão. Use include_values: true para ver os valores completos.

Inputs: projectName (required), serviceName (required), include_values.

get_exposed_portsB

Lista as portas expostas (publicadas no host) de um serviço. Use para descobrir em quais portas o serviço está acessível externamente.

Inputs: projectName (required), serviceName (required).

get_projectA

Retorna detalhes completos de um projeto: lista de serviços, configurações e status atual.

Inputs: projectName (required).

get_service_errorA

Retorna o último erro registrado do serviço. Use para debugar falhas de deploy ou runtime.

Inputs: projectName (required), serviceName (required).

get_service_logsB

Busca os logs do container de um serviço. Use para debugar erros em runtime. Retorna as últimas N linhas.

Inputs: projectName (required), serviceName (required), lines.

get_service_notesA

Lê as notas/anotações salvas no serviço.

Inputs: projectName (required), serviceName (required).

get_service_statsB

Retorna métricas de um serviço específico: CPU, memória e rede do container.

Inputs: projectName (required), serviceName (required).

get_storage_statsB

Retorna uso de armazenamento do servidor.

Inputs: no named parameters.

get_system_statsA

Retorna métricas do servidor: CPU, memória, disco, rede e uptime. Use para verificar saúde do servidor.

Inputs: no named parameters.

inspect_composeA

Retorna a configuração de um serviço Docker Compose: arquivo compose, env, source e estado. Use antes de qualquer alteração.

Inputs: projectName (required), serviceName (required).

inspect_databaseA

Retorna detalhes do banco de dados: credenciais, porta exposta, connection string e status.

Inputs: type (required), projectName (required), serviceName (required).

inspect_serviceA

Retorna configuração completa de um serviço: source, env vars, deploy config, mounts, ports, domínios, recursos. Use SEMPRE antes de qualquer update para preservar o estado.

Inputs: projectName (required), serviceName (required).

list_actionsA

Lista as ações/jobs em execução ou recentes (deploys, builds, restarts). A lista global guarda apenas uma janela curta — passe projectName/serviceName para filtrar no servidor e não perder ações de um serviço específico.

Inputs: type, limit, projectName, serviceName.

list_certificatesA

Lista os certificados SSL/TLS gerenciados pelo Easypanel (domínios cobertos, emissor, validade). Use para auditar HTTPS e renovações.

Inputs: no named parameters.

list_containersA

Lista os containers Docker em execução de um serviço (ID, nome, imagem, comando, status, portas). Use para descobrir o container antes de exec_in_container ou para checar se o serviço está rodando.

Inputs: projectName (required), serviceName (required).

list_domainsB

Lista todos os domínios configurados em um serviço.

Inputs: projectName (required), serviceName (required).

list_mountsA

Lista os volumes/mounts de um serviço (volumes nomeados, bind mounts e arquivos montados). Use para ver onde os dados persistentes do serviço estão.

Inputs: projectName (required), serviceName (required).

list_nodesA

Lista os nós do cluster Docker Swarm gerenciado pelo Easypanel (manager/worker, status, disponibilidade). Em servidor único retorna apenas o nó local.

Inputs: no named parameters.

list_portsA

Lista os mapeamentos de porta de um serviço (porta publicada no host → porta do container). Complementa get_exposed_ports com a configuração completa de portas. Use para ver o que está exposto e em qual protocolo.

Inputs: projectName (required), serviceName (required).

list_projectsA

Lista todos os projetos do Easypanel com seus serviços e status. Use para descobrir o que existe no painel antes de operar.

Inputs: no named parameters.

list_usersA

Lista os usuários do painel Easypanel (admin, e-mails, papéis).

Inputs: no named parameters.

prune_dockerA

Executa um "docker system prune" no servidor inteiro via Easypanel: remove containers parados, redes sem uso, cache de build e imagens não referenciadas para liberar espaço em disco. ⚠️ Ação destrutiva e de escopo GLOBAL (afeta todos os projetos do servidor, não um serviço específico) — exige confirm: "CONFIRMO". Use cleanup_docker_images para uma limpeza mais leve (só imagens não usadas).

Inputs: confirm.

reboot_serverA

⚠️ CRÍTICO — Reinicia o SERVIDOR inteiro (máquina host). TODOS os serviços e o painel ficam fora do ar até o boot completar. Use apenas em manutenção planejada. Requer confirm: "CONFIRMO".

Inputs: confirm.

remove_domainA

⚠️ Remove permanentemente um domínio. O tráfego para esse host parará de funcionar. Requer confirm: "CONFIRMO".

Inputs: confirm (required), domainId (required), projectName (required), serviceName (required).

rename_serviceA

⚠️ Renomeia ou move um serviço. Webhooks, DNS e referências internas que usam o nome antigo deixarão de funcionar. Requer confirm: "CONFIRMO".

Inputs: confirm (required), projectName (required), serviceName (required), newProjectName (required), +1 more.

restart_panelA

⚠️ Reinicia o próprio Easypanel. O painel/API ficam brevemente indisponíveis; os serviços hospedados continuam rodando. Requer confirm: "CONFIRMO".

Inputs: confirm.

restart_serviceA

Reinicia o serviço. Causa breve indisponibilidade. Funciona para app E compose — em compose, reinicia via redeploy (docker compose up recria os containers).

Inputs: projectName (required), serviceName (required).

set_env_varA

Adiciona ou atualiza UMA variável de ambiente. Lê o estado atual antes de escrever — não apaga outras variáveis.

Inputs: key (required), value (required), projectName (required), serviceName (required).

set_primary_domainA

Define qual domínio é o primário (usado como URL principal do serviço).

Inputs: domainId (required), projectName (required), serviceName (required).

set_service_notesB

Salva notas/anotações no serviço (markdown suportado).

Inputs: notes (required), projectName (required), serviceName (required).

set_service_resourcesA

Define limites e reservas de CPU e memória do serviço. Envie só os campos que quer alterar — os omitidos mantêm o valor atual (0 = sem limite). Memória em MB, CPU em núcleos (0.5 = meio núcleo). Aplica no próximo deploy/restart.

Inputs: projectName (required), serviceName (required), cpuLimit, memoryLimit, +2 more.

set_source_githubB

Configura a source do serviço para um repositório GitHub. O repo deve estar conectado no Easypanel (Settings > GitHub).

Inputs: ref (required), repo (required), owner (required), projectName (required), +2 more.

set_source_imageC

Configura a source do serviço para uma imagem Docker.

Inputs: image (required), projectName (required), serviceName (required), password, +1 more.

start_serviceA

Inicia um serviço que está parado. Funciona para app e compose (em compose, equivale a um redeploy/compose up).

Inputs: projectName (required), serviceName (required).

stop_serviceA

⚠️ PARA o serviço em produção. Usuários não conseguirão acessar enquanto parado. Requer confirm: "CONFIRMO".

Inputs: confirm (required), projectName (required), serviceName (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 57 tools

    Disambiguation3/5

    Most tools are clearly scoped by resource and action, but there are real overlaps: deploy_service already handles compose while deploy_compose also exists, and stats/port/log cleanup tools have close boundaries. The descriptions help, but an agent could still pick the wrong tool in several situations.

    Naming Consistency4/5

    Names overwhelmingly follow a snake_case verb_noun pattern with consistent list/get/create/set/delete/destroy prefixes. Minor deviations include easypanel_raw being noun-first and the mix of get_project, inspect_service, and inspect_compose, but the overall style is predictable.

    Tool Count2/5

    57 tools is far above the comfortable agent-facing range and makes selection and context usage heavy. Although the Easypanel domain is broad and most tools are individually purposeful, several could be consolidated or left to easypanel_raw to reduce surface area.

    Completeness3/5

    Core workflows like project/service lifecycle, env vars, domains, logs, and deploys are well covered. However, there is no dedicated set_compose_file tool, mounts and ports cannot be removed directly, and most admin operations are read-only, so agents must fall back to easypanel_raw for notable gaps.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server that builds itself by creating new tools as needed based on user requests (Requires restart of Claude Desktop to use newly created tools).
      4
      25
      -
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for EasyPanel that enables AI agents to manage servers, projects, services, databases, and domains via 40 curated tools or raw tRPC access to all 347 API procedures.
      42
      49 npm
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for Cloudways enabling server management, app deployment, backups, SSL, environment variables, and monitoring via Claude Code.
      12
      MIT