In-depth architectural comparison of the Easypanel MCP Server and Xahau MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Easypanel MCP Server
Developer Tools · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Xahau MCP
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Easypanel MCP Server if you need specialized Developer Tools tools running via a local process. Choose Xahau MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Easypanel MCP Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: EASYPANEL_URL, EASYPANEL_TOKEN.
Full Easypanel control from Claude Code and Cursor — 37 tools for deployments, services, env vars, logs, domains, databases and monitoring. Safety guards require explicit confirmation for all destructive actions.
First MCP for the Xahau network — offline Hook WASM VM + static analyzer, read-only ledger tools.
Lista todos os projetos do Easypanel com seus serviços e status. Use para descobrir o que existe no painel antes de operar.
get_project
Retorna detalhes completos de um projeto: lista de serviços, configurações e status atual.
create_project
Cria um novo projeto no Easypanel.
delete_project
⚠️ DESTRUTIVO — Remove permanentemente o projeto e TODOS os seus serviços e dados. Irreversível. Requer confirm: "CONFIRMO".
inspect_service
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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Easypanel MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Xahau MCP belongs to Developer Tools using local stdio subprocess. Select Easypanel MCP Server when you need capabilities focused on developer tools and Xahau MCP when you require tools for developer tools.
Cria um novo serviço de app em um projeto. Após criar, configure a source com set_source_github ou set_source_image.
rename_service
⚠️ Renomeia ou move um serviço. Webhooks, DNS e referências internas que usam o nome antigo deixarão de funcionar. Requer confirm: "CONFIRMO".
destroy_service
⚠️ DESTRUTIVO — Remove permanentemente o serviço e seus dados. Irreversível. Requer confirm: "CONFIRMO".
deploy_service
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).
start_service
Inicia um serviço que está parado. Funciona para app e compose (em compose, equivale a um redeploy/compose up).
stop_service
⚠️ PARA o serviço em produção. Usuários não conseguirão acessar enquanto parado. Requer confirm: "CONFIRMO".
restart_service
Reinicia o serviço. Causa breve indisponibilidade. Funciona para app E compose — em compose, reinicia via redeploy (docker compose up recria os containers).
+45 more tools listed on main page
Xahau MCP Tools (53)
execute_hook
Run the real Hook bytecode in a local VM** against a simulated tx/state → actual accept/rollback, return code, state writes, emits, trace (`LOCAL_VM`).
simulate_transaction
PRE-SIGN FLIGHT SIMULATOR** — predict an unsigned tx's fate: originator + stakeholder hook chains (order canonical from xahaud `Transactor.cpp`/`applyHook.cpp`) run as real bytecode against live state; per-hook verdicts, decoded emits, state writes, static engine preflights, scam score.
what_if
TIME MACHINE** — fetch a real historical tx, apply your overrides, re-simulate at its original ledger. Reproduces the real reward claim's `GenesisMint` to the drop (test-locked).
fuzz_hook
Differential fuzzing**: sweep many generated transactions through the VM to map the hook's accept/rollback **decision boundary** (which tx types / amounts it accepts vs rejects).
annotate_hook_trace
Decode an `execute_hook` `trace[]`** into human-readable values by byte-width: canonical XFL float (`definite`), int64/native-drops (both endians), UInt32 + Ripple-epoch date, candidate account-id → r-address (`possible`), 32-byte hash. Raw hex always preserved; offline.
Post-mortem a real on-chain tx's hooks**: fetch the tx + its `meta.HookExecutions` + engine result, then run each fired hook's **real bytecode** through the VM and compare the VM's accept/rollback to what the chain recorded. On-chain decision is authoritative; VM run is `LOCAL_VM`; `agree` is `null…
vm_fidelity_report
Honest fidelity metric**: replays a committed corpus of real mainnet HookExecutions through the VM and reports agreement % over **comparable (non-degraded)** runs only; offline.
classify_hook
Infer in plain English what a hook does (firewall/emitter/stateful/financial/…).