See and kill the dev servers your coding agents leave running, and get collision-free ports.
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…):
npx skills add dan-fetch-studio/tidyports-integrations
The MCP server:
npm install -g @tidyports/mcp
Then register it with your client, pointing at the installed tidyports-mcp binary. For
Claude Code:
claude mcp add tidyports -- tidyports-mcp
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.
brew install --cask dan-fetch-studio/tap/tidyports
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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @tidyports/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-dan-fetch-studio-tidyports": {
"command": "npx",
"args": [
"-y",
"@tidyports/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.dan-fetch-studio/tidyports works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.