The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Tidyports listing page.
Let your coding agent see and control the local dev servers it starts.
If you run Claude Code, Cursor or Codex across several git worktrees, each one starts dev
servers you never typed a command for. Ports collide, and an agent that hits EADDRINUSE
often can't tell a port conflict from a bug — so it "fixes" working code instead.
These integrations give the agent a way to look, rather than guess.
mcp/ | An MCP server — typed tools for any MCP client (Claude Code, Cursor, Claude Desktop, Windsurf, Zed). |
skills/ | A Claude Code skill, if you'd rather it shelled out to the CLI directly. |
guard/ | Wrap your dev command so EADDRINUSE names what is holding the port, instead of only saying that something is. |
raycast/ | A Raycast extension for the same list, without leaving the launcher. |
| Tool | What it does |
|---|---|
list_servers | Listening dev servers: port, process, branch, owner, idle. Read-only. |
kill_port | Stop the server on a given port. |
alloc_port | A stable, collision-free port for this worktree — the fix for parallel agents fighting over :3000. |
free_port | A port nothing is listening on right now, to bind immediately. |
The skill, for any agent (Claude Code, Cursor, Copilot, Gemini…):
The MCP server:
Then register it with your client, pointing at the installed tidyports-mcp binary. For
Claude Code:
These are a thin layer over the tidy-ports CLI, which ships inside
TidyPorts — a free macOS menu-bar app that shows every dev server
running on your Mac and which agent started it.
Or download it from tidyports.app/download. macOS 15+.
The integrations here are MIT (see LICENSE). The TidyPorts app itself is source-available under its own licence.