Skip to main content
Glama
dan-fetch-studio

tidyports

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

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.

Related MCP server: Harbor MCP Server

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

No tool schema history has been recorded yet.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Inspect, manage, and kill local dev servers via MCP. Stop guessing what's on :3000. Five tools: list servers with framework detection, inspect ports, find zombies, diagnose conflicts, safe-kill with dry-run default. Local, no cloud, no telemetry.
    5
    10
    3
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to discover, configure, and manage local development servers. Provides tools for app registration, port allocation, lifecycle control, and log access without manual config editing.
    254
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    MCP server for managing local dev ports on macOS. It enables AI agents to inspect listening ports, identify owning processes and parent chains, kill processes safely, wait for ports, and report LAN exposure.
    6
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dan-fetch-studio/tidyports-integrations'

If you have feedback or need assistance with the MCP directory API, please join our Discord server