English Français العربية

io.github.dan-fetch-studio/tidyports

Official registry Developer tools

See and kill the dev servers your coding agents leave running, and get collision-free ports.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @tidyports/mcp
Claude Code 
claude mcp add tidyports -- npx -y @tidyports/mcp@0.1.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "tidyports": {
            "command": "npx",
            "args": [
                "-y",
                "@tidyports/mcp@0.1.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. TidyPorts integrations
  2. Tools
  3. Install
  4. Licence

TidyPorts integrations

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.

Tools

ToolWhat it does
list_serversListening dev servers: port, process, branch, owner, idle. Read-only.
kill_portStop the server on a given port.
alloc_portA stable, collision-free port for this worktree — the fix for parallel agents fighting over :3000.
free_portA port nothing is listening on right now, to bind immediately.

Install

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
It needs the TidyPorts app

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+.

Licence

The integrations here are MIT (see LICENSE). The TidyPorts app itself is source-available under its own licence.

Frequently asked questions

What is io.github.dan-fetch-studio/tidyports?

See and kill the dev servers your coding agents leave running, and get collision-free ports.

How do I install io.github.dan-fetch-studio/tidyports?

It runs on your machine. In Claude Code: claude mcp add tidyports -- npx -y @tidyports/mcp@0.1.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.dan-fetch-studio/tidyports need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.dan-fetch-studio/tidyports open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.dan-fetch-studio/tidyports?

It is published by dan-fetch-studio. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.