mcpField
T
tidyports

tidyports

Local
github.com/dan-fetch-studioDeveloper Tools0Updated 13w ago
Repository

About tidyports

tidyports integrations let coding agents inspect and manage local development servers, particularly across parallel git worktrees. They can also assign stable ports per worktree and identify the process behind a port conflict.

Key features

  1. 01Lists dev servers, ports, and owning processes
  2. 02Stops the server on a specified port
  3. 03Allocates stable ports per worktree
  4. 04Finds a currently unused port
  5. 05Guard identifies the process holding a port

Use cases

  1. 01Diagnose port collisions across parallel worktrees
  2. 02Inspect dev servers started by coding agents
  3. 03Free a port occupied by a server

MCP support

The MCP server exposes list_servers, kill_port, alloc_port, and free_port tools for inspecting servers and managing ports. The integrations depend on the tidy-ports CLI included with the TidyPorts app.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "dan-fetch-studio-tidyports": {
      "command": "npx",
      "args": [
        "-y",
        "@tidyports/mcp"
      ]
    }
  }
}
Run commandnpx -y @tidyports/mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@tidyports/mcp0.1.2

Tools

4

Saved tool list · updated 3w ago

This tool takes no parameters.

Details

From the project README

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.