MCP server de DevWebUI
Commit 15 nov 2026Proporciona una GUI y un plano de control MCP para gestionar, monitorizar y automatizar servidores de desarrollo locales desde un único panel de control.
También conocido como LunarWerxs/DevWebUI
- Stars
- 29
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 15 nov 2026
- Licencia
- —
¿Qué es DevWebUI MCP?
Proporciona una GUI y un plano de control MCP para gestionar, monitorizar y automatizar servidores de desarrollo locales desde un único panel de control.
Resumen generado a partir del README del proyecto
Acerca del MCP server de DevWebUI
DevWebUI ofrece un panel centralizado y un plano de control MCP para gestionar servidores de desarrollo locales. Sustituye la necesidad de tener múltiples pestañas de la terminal al permitirte iniciar, detener y reiniciar diversos procesos desde una única interfaz. Los desarrolladores pueden monitorizar el estado en vivo, el uso de CPU, el consumo de memoria y los logs de cada proyecto en ejecución. El sistema funciona como un daemon local, normalmente en el puerto 4000, y es compatible con comandos existentes como npm run dev o bun run dev sin necesidad de contenerización o cambios de configuración complejos.
Esta herramienta está diseñada tanto para desarrolladores humanos que usan la GUI como para agentes de IA que usan el MCP server. Mientras que la GUI ofrece controles de un solo clic y un log de errores persistente con integración con el editor, la implementación de MCP proporciona 43 herramientas que permiten a los agentes controlar el mismo daemon. Esto garantiza que tu asistente de codificación de IA y tu panel manual operen siempre desde una única fuente de verdad. Incluye funciones como el rescate de conflictos de puertos, detección automática de dependencias mediante lockfiles y soporte para archivos .devwebui para agrupar procesos relacionados.
Qué puedes hacer con él
- 1Automatizar la gestión de servidores con IAUn agente de IA puede usar las herramientas de MCP para iniciar, detener o reiniciar procesos de desarrollo específicos.
- 2Monitorizar el uso de recursos y logsUn desarrollador puede observar en tiempo real la CPU, la memoria y los logs en streaming de todos los proyectos activos en un solo panel.
- 3Depurar errores con integración en el editorPuedes hacer clic en los enlaces de error del log persistente para abrir el archivo y la línea exacta en tu IDE preferido.
- 4Resolver conflictos de puertos automáticamenteEl sistema identifica qué proceso está ocupando un puerto específico y ofrece liberarlo.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Configuración
DEVWEBUI_URL
| Nombre | Descripción | Tipo |
|---|---|---|
| DEVWEBUI_URL | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblelunarwerxs/devwebui is public and reachablegithub.com/lunarwerxs/devwebui ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)No licenseHallazgo
- Commit o lanzamiento en el último añoLast commit or release 2026-11-11github.com/lunarwerxs/devwebui ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubA GUI + MCP control plane for your local dev servers
Run every dev server from one pane: click to start, stop and restart, and watch live status, CPU,
memory and logs. Then let your AI agents drive the same daemon over MCP.
No more bun run dev babysitting across a dozen terminal tabs.
Website · Quick start · .devwebui files · MCP · Changelog
DevWebUI is a GUI and MCP control plane for local dev servers that lets developers start, stop,
restart, and monitor every dev process in a project from one dashboard, and lets AI coding agents
drive the same daemon over MCP, replacing a dozen terminal tabs of manual bun run dev babysitting.
Why it exists
The good local-dev GUIs (hotel, exo) are abandoned. PM2's web UI is paid. Everything else that's still maintained is a TUI or a heavy container/k8s tool. Nobody ships the one thing you actually want for a fleet of dev servers: a GUI and MCP over one daemon, so you click, your agents automate, and everyone works off a single source of truth.
How it compares
- vs. hotel and exo: both are local dev-server GUIs, but neither has shipped a release in a while. DevWebUI is actively maintained and pairs its GUI with an MCP server, which neither offers.
- vs. PM2's web UI (PM2 Plus / PM2.io): PM2 itself is free from the CLI, but its hosted monitoring dashboard is a paid product beyond a limited free tier. DevWebUI's GUI is free and runs entirely on your machine, no account needed for core functionality.
- vs. Docker Compose / devcontainers: these give you full container isolation, which is more
infrastructure than most local dev-server juggling needs. DevWebUI runs your existing commands
(
npm run dev,bun run dev, etc.) directly, no containers or config rewrite required.
Quick start
Prebuilt Windows app: not published yet. There are no GitHub Releases for this repository, so
install from source (below). When a release with devwebui-windows-x64.exe is published, this section
will link it again.
The tray icon and its Quit and auto-restart supervisor come from a small launcher
(misc\DevWebUI-Tray.exe). misc\Create-Shortcut.ps1 makes a shortcut that launches through the
tray host directly.
Windows source checkout: double-click the DevWebUI shortcut. It runs hidden with a tray
icon: right-click for Open / Rebuild & Restart / Restart / Stop all processes / Quit
(Stop all processes halts every dev server and leaves DevWebUI running). The first launch builds once;
after that it's instant. Changed the GUI? Hit Rebuild & Restart.
Any OS: from a terminal:
bun install
bun run dev # daemon on :4000 + GUI on http://localhost:4010
On its first launch DevWebUI scans once for .devwebui files and recognizable
dev-script projects. After that, startup scanning stays off unless you enable it in Settings; use
Add project, drop a folder or .devwebui file onto the Windows launcher, or run
devwebui open <path> whenever you want to register something new. Want a dependency-free sample?
Add server/examples/extra.devwebui. The GUI and API share one port (default 4000); if it's
taken, the daemon hops to the next free one and opens the URL it actually bound.
What you get
- One-click control: start / stop / restart any dev server; live status, CPU, memory, logs.
- One panel per repo: a
.devwebuifile groups every process under one collapsible header; your projects auto-reload next launch. - Runtime-aware launches: automatic mode follows each project's lockfile, and compatible Bun/Node commands launch without a permanent shell wrapper.
- Port-conflict rescue: detects a taken port, tells you which process is holding it, and frees it on request.
- One origin for every server: open any managed process through DevWebUI's own port at
http://<target>.localhost:4000(or/proxy/<target>/), where<target>is a process id likep1a2b3c4.web, a project name likemy-app, or a declared port; HTTP and WebSocket (HMR) are relayed, only to ports a registered process declares, behind the same cross-site guard as the API. - Persistent error log: de-duplicated stderr / crashes / error-looking stdout that survives restarts. Every
file:line:colin it is a link that opens that line in the editor you already have running (VS Code and its forks, JetBrains IDEs, Zed, Sublime Text, Notepad++); setDEVWEBUI_EDITORto the editor's executable to pick one explicitly. - Desktop shortcuts (Windows): send any server (or a whole repo) to your Desktop from the ⋮ menu; double-click starts it, linked servers and all, in a small window with a Stop button.
- Built for agents: a full set of MCP tools drives the same daemon you click, off one shared state.
- Localized & themed: full i18n (English base; add a language), light/dark.
- Lives in your tray: a Windows tray app runs the daemon hidden; Open / Rebuild / Restart / Quit.
.devwebui files
One small file per repo lists the servers to run. Drop it in the repo root and click Add project:
{
"name": "Connections",
"processes": [
{ "id": "main", "name": "Main SPA", "command": "bun run dev:main", "autostart": true },
{ "id": "pay", "name": "Pay plane", "command": "bun run dev:pay", "port": 4020 }
]
}
Per-process: id, name, command, plus optional cwd, port, url, color, env,
autostart, waitForPort, links, companion, compose, answers. You can also add and edit
processes right in the GUI, and DevWebUI writes them back to the file. links groups servers that
run as one unit (starting or stopping one starts or stops them all); companion marks a process,
like a shared database, that starts alongside any other process in the project you start by hand.
A compose block brings the repo's docker compose stack up first, waits for its ports, and
injects DATABASE_URL/REDIS_URL-style env derived from each service's image. answers lists expect/send rules that type a reply into stdin when a program that reads it without
a TTY check (a shell read, set /p, Python input(), a custom setup script) stops at a prompt,
so it does not wait forever with no terminal to type into.
Full field spec + a copy-paste prompt that writes the file for you → AI_GUIDE.md
Drive it from an AI agent (MCP)
The MCP server is a thin stdio client over the running daemon, so the GUI and your agents share one state. Start the daemon, then register:
{
"mcpServers": {
"devwebui": {
"command": "bun",
"args": ["server/src/mcp.ts"],
"cwd": "/absolute/path/to/devwebui",
"env": { "DEVWEBUI_URL": "http://localhost:4000" }
}
}
}
43 tools cover projects, processes (start/stop/restart, enable/disable, all), logs, the error
log (with jump-to-source via open_in_editor), threshold alerts, and the live browser tabs of your dev apps: an opt-in <script> snippet lets
an agent read a page's client-side errors and call inspection tools the app registers on the page. Full list → AI_GUIDE.md
CLI
devwebui start | stop | status | list # boot / stop the daemon, inspect state
devwebui start-process | stop-process | restart-process <id|name>
devwebui start-all | stop-all
devwebui alerts list | add | remove | events | clear # threshold alert rules + fired-event history
devwebui open <folder|file.devwebui> # add/drop a project; starts it if already added
devwebui pairing codes | clients | revoke <id> # local API auth: pairing codes + paired browsers
devwebui mcp # the stdio MCP server for agents
A thin client over the same REST API the GUI and MCP use. Run devwebui --help for the rest;
DEVWEBUI_URL / DEVWEBUI_PORT point it at another daemon.
Locking the local API to you
By default the daemon's REST API answers any local caller that is not a cross-site browser page.
Start it with DEVWEBUI_REQUIRE_AUTH=1 to require a credential on every /api route except
/api/health and the pairing handshake. That includes /api/browser/*: the page snippet has no
credential to send, so with the flag on, dev pages cannot connect and the browser-tab tools find none.
- Cookie file. Every boot the daemon writes a fresh random secret to
.cookiein its data dir (~/.devwebui, owner-only) and deletes it on exit. The CLI and the MCP server read it and send it automatically, so nothing needs configuring; a process that cannot read your data dir is refused. The secret is only ever sent to a loopback address, even whenDEVWEBUI_URLpoints elsewhere. - Pairing a browser. A browser cannot read that file, so the GUI shows a pairing screen. Click
Get a pairing code, then type the 6-digit code the daemon prints (or that
devwebui pairing codeslists). The browser keeps its own key in the GUI origin's local storage and sends it as a header, never as a cookie: browsers share cookies across every localhost port, so a cookie would reach the dev servers you open from the dashboard. List paired browsers withdevwebui pairing clientsand revoke one withdevwebui pairing revoke <id>. Codes expire after 5 minutes. Ten wrong guesses (from anyone) lock pairing for 15 minutes, so a misbehaving local process can hold pairing shut for that long; the CLI and MCP are unaffected.
The tray's own restart/quit carry its session token and keep working. Stop all processes in the
native tray and the stopAll action of DevWebUI-Tray.ps1 do not send a credential yet, so both
are refused while enforcement is on; use devwebui stop-all instead.
Stack
Bun + Hono daemon (HTTP + SSE) with a zero-dependency stdio MCP engine; Vue 3 + Vite, shadcn-vue on Reka UI, Tailwind v4 (zinc + indigo, light/dark). See the changelog for what's landed.
Local-first
DevWebUI runs entirely on your machine: a single daemon on your localhost, with its source on GitHub under the PolyForm Noncommercial License. Core functionality needs no account and no cloud. Two optional extras:
- Settings sync: sign in with a LunarWerx Connections account to sync a small allowlist of
portable prefs + theme across machines. Off by default; only runs after you explicitly enable it
in Settings, and
@cnct/connect(the SDK it needs, which also ships the settings-store locker client) is an optional dependency that is installed but never imported or initialized unless you do. - Anonymous install ping: the update check (
GET /api/updates, cached 5 minutes, fired when the GUI loads or on the opt-in auto-update timer) is answered by an install counter atstudio.connections.icuthat proxies GitHub's own releases feed, and the request carries a random per-install id plus your app version and OS family (Windows / macOS / Linux) so we know roughly how many installs exist. From that request, the server also derives and stores a coarse location (country, region, city, timezone), your network's ASN, locale, and a truncated user agent, but never an IP address. No hostname, username, path, or account info is ever sent. The request also fails silently and never blocks anything if it can't reach the network. SetDEVWEBUI_NO_PING=1to turn it off (the olderDEVWEBUI_PULSE_DISABLE=1/CONNECTIONS_PULSE_DISABLE=1still work too); it's already off automatically in dev/test/CI runs.
FAQ
Is DevWebUI free?
For personal and other noncommercial use, yes. DevWebUI is free under the PolyForm Noncommercial
License (commercial use needs a licence, see licensing), and core functionality,
starting, stopping,
and monitoring your dev servers from the GUI or over MCP, needs no account and no cloud. The only
optional extras are cross-machine settings sync, off unless you enable it, and an anonymous install
ping for update checks, on unless you set DEVWEBUI_NO_PING=1.
Does it work offline?
Yes. The daemon and GUI run entirely on your local machine, and starting, stopping, and monitoring
dev servers works with no network connection at all. The only features that reach the internet are
optional: settings sync (off by default) and a lightweight install ping used for update checks,
which you can disable with DEVWEBUI_NO_PING=1.
Is my data sent anywhere?
No project data, commands, logs, or file paths leave your machine. If you enable it, settings sync
shares a small allowlist of prefs and theme via a LunarWerx Connections account. A separate
anonymous install ping (disable with DEVWEBUI_NO_PING=1) sends a random install id, app version,
and OS family, but never your IP address, hostname, username, or file paths.
What are the system requirements?
There is no prebuilt download yet (no GitHub Release is published), so run it from source with Bun
installed on any OS: bun install then bun run dev starts the
daemon on port 4000 and the GUI on port 4010. macOS and Linux tray support is on the roadmap.
How is DevWebUI different from PM2's web UI, hotel, or exo? Hotel and exo are local dev-server GUIs that haven't shipped a release in a while, and PM2's web dashboard (PM2 Plus / PM2.io) is a paid product beyond its free tier. DevWebUI is actively maintained, free, and local-first, and pairs its GUI with a 43-tool MCP server so AI agents can drive the same daemon you click.
Can AI agents control DevWebUI directly?
Yes. DevWebUI ships a stdio MCP server (devwebui mcp, or server/src/mcp.ts) with 43 tools
covering projects, starting/stopping/restarting processes, enabling/disabling them, logs, the
error log, and threshold alerts. It's a thin client over the same running daemon the GUI uses, so
an agent and a human see and change the same state.
What is safe mode?
If the DevWebUI daemon did not shut down cleanly last time (a crash, or a hard kill), the next
launch comes up in safe mode: your projects load, but nothing starts automatically, so a dev
server that takes the daemon down on start cannot put it in a crash loop. A banner links to the
recorded crash entry and offers Leave safe mode, which runs the skipped autoStartOnLaunch
set (servers an auto-update was resuming are not restarted). A reboot or logoff is not a crash
and does not trigger safe mode. You can
also start quietly on purpose with devwebui --safe-mode (or DEVWEBUI_SAFE_MODE=1).
How do I add a project?
Drop a .devwebui file (one per repo, listing its dev servers) in the repo root and click Add
project in the GUI, or run devwebui open <path> from the CLI. On first launch DevWebUI also
scans once for .devwebui files and recognizable dev-script projects automatically.
Can I use DevWebUI without the GUI?
Yes. The devwebui CLI is a thin client over the same REST API the GUI and MCP server use:
devwebui start / stop / status / list manage the daemon, and start-process /
stop-process / restart-process control individual servers by id or name.
On the roadmap: macOS / Linux tray, an in-GUI env editor, and multi-host.
License
PolyForm Noncommercial 1.0.0 © LunarWerx Studios, from 2026-10-22 on. The source is available and free for personal and other noncommercial use; commercial use needs a licence from LunarWerx (request one). Releases through 1.2.0 were MIT, and that grant stays in effect for those copies; see licensing details.
Made by LunarWerx Studios, also behind RepoYeti, AgentHydra, and SageThumbs.
Preguntas sobre DevWebUI MCP
¿Puedo usar DevWebUI con Docker?
Sí, incluye un bloque de compose que puede levantar una pila de docker compose primero, esperar a que sus puertos estén disponibles e inyectar variables de entorno.
¿Cómo interactúan los agentes de IA con mis servidores de desarrollo?
Los agentes de IA pueden usar el MCP server para controlar el mismo daemon que utiliza la GUI, proporcionando 43 herramientas para gestionar proyectos, procesos, logs y pestañas del navegador.
¿Se envían mis datos a la nube?
No, DevWebUI es local-first y se ejecuta completamente en tu máquina.