Server data from the Official MCP Registry
See and kill the dev servers your coding agents leave running, and get collision-free ports.
See and kill the dev servers your coding agents leave running, and get collision-free ports.
This MCP server is well-structured with appropriate security controls. It wraps a local CLI tool with typed inputs, proper error handling, and a deliberately withheld deployment tool that includes explicit user confirmation gates. The main permission (local process execution via the tidy-ports CLI) is appropriate for its stated purpose of managing local dev servers. Minor code quality observations exist but do not indicate security vulnerabilities. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
3 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-dan-fetch-studio-tidyports": {
"args": [
"-y",
"@tidyports/mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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). |
claude-code/ | A Claude Code skill, if you'd rather it shelled out to the CLI directly. |
| 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.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.