Localdock shows every dev server, who started it, and kills the orphans in one click. With an MCP server built in so Claude Code and Cursor stop fighting over ports.
$19 one time · single device · 3-day free trial
0:15 · two Claude Code sessions collide on :3000, Localdock resolves it
Every process is tagged with the session, the project directory, and the terminal that launched it.
Servers whose session has ended are flagged as orphaned. Idle ones show how long they have been quiet.
One click sends SIGTERM, waits, then falls back to SIGKILL. Child processes go with it.
The built-in MCP server gives Claude Code and Cursor three tools, so they ask for a port instead of guessing.
The agent asks before it starts. No collision, no retry loop.
While it works, the session and project stay attached to the process.
When the session ends, the agent shuts down what it started.
Secure checkout · prices in USD
Built by one person. If it does not fit your workflow, email me and I refund it.
No. Localdock only sees and signals processes owned by your user account. It never asks for a password.
Nothing about your processes, ever. Ports, paths, PIDs and session names stay local. The only network call is the license check.
Any MCP client. It is tested with Claude Code and Cursor. The tools are list_ports, get_free_port and cleanup.
The trial is full-featured and starts without an email. When the 3 days are up, Localdock stops managing processes until you enter a license.
You can. lsof tells you a PID holds a port. It does not tell you which agent session started it, whether anyone is still using it, or hand your agent a free port to use next.
No. $19 once, for a single device. Updates for version 1 are included.
Localdock ships August 9, 2026. Join the list and get the download link and the trial on day one.
$19 one time · single device · 3-day free trial