Dev MCP Server

MCP Dev Server Manager - A daemon for managing development servers. The dev mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.

What it actually does

A daemon that accepts requests from MCP clients to start dev servers, allocating unique ports to avoid collisions and shutting down idle connections after 120s of inactivity.

• Run multiple dev servers in parallel — useful if you want to use automated testing tools eg Playwright or Google Dev Tools MCP
• Avoid port collisions — when working with websites, it's often necessary to specify different ports if you want to run multiple dev servers
• Automatic port allocation — starting at 3010 with reuse
• Log capture — with 512KB ring buffers per server
• Auto-cleanup — of idle sessions after 120 seconds (configurable via --idle-timeout)

Its toolset

Everything the assistant can do here goes through one of these:

• start — Start a development server. Auto-generates a unique 4-character session key
• stop — The stop tool exposed by this server
• status — The status tool exposed by this server
• tail — The tail tool exposed by this server
• Modules — The Modules tool exposed by this server

Adding it to your client

The server ships on npm as dev-manager-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Dev's toolset — start, stop, status and 2 more — is a fair guide to whether it matches your workflow. It is maintained by louiskw; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Dev's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the dev mcp server does with a few real requests.