Labsco
MCP SERVER

DevServer MCP

by Uninen

Start, stop and read the logs of your project's dev servers, and optionally drive a browser against them.

Containers, Kubernetes & Cluster Operations
Summary
Log pagination, which is what makes reading a dev server's output survivable.

Both the log tool and the console-message tool take an offset, a limit and a direction, with negative offsets counting from the end — so an agent can ask for the last twenty lines instead of receiving the whole buffer. The project describes itself as alpha; treat the browser half as experimental.

What it is

A server that manages the processes declared in a devservers.yml — backend, frontend, worker — and streams their logs into a terminal UI you can also click. An experimental Playwright layer adds browser control against what those servers are serving.

What you get
  • start_server and stop_server by name, including servers it did not start
  • get_devserver_statuses — the state of everything configured
  • get_devserver_logs with offset, limit and reverse, so a long log is paginated rather than dumped
  • browser_navigate, browser_snapshot, browser_click, browser_type, browser_resize and browser_screenshot
  • browser_console_messages with the same pagination and an option to clear after reading
  • A terminal UI with live log streaming and clickable start and stop
Requirements

Installed with uv from the repository, then a devservers.yml at the project root declaring each server's command, working directory and port. The client connects over HTTP to http://localhost:3001/mcp while the TUI runs in a terminal. The browser tools need Playwright and its drivers installed separately and the experimental flag switched on in the config.

Setup effort

One command — uv add --dev git+https://github.com/Uninen/devserver-mcp.git --tag v0.6.0