PortPeek icon PortPeek

Stop your agents from fighting over ports.

A Mac menu bar app with a built-in MCP server. AI agents safely claim dev ports — no conflicts.

Coming soon to the Mac App Store

Works with Claude · Cursor · Copilot · Cline · Windsurf · any MCP-compatible agent

Want just the MCP?
portpeek-mcp

No app. Just the server.

Two steps. Works with every major AI coding tool.

Install & start

Downloads a shell script — macOS will prompt for approval in System Settings → Privacy & Security before it runs

or install manually
brew install adamorad/tap/portpeek-mcp && portpeek-mcp --install-launch-agent

Add to your agent config

{"mcpServers":{"portpeek":{"url":"http://localhost:27182"}}}

Your agent calls these automatically

list_active_ports get_available_port reserve_port release_port

Want port visibility in your menu bar? Get PortPeek App

Built by Adam Morad
How does it compare?
Port management for AI agents

Three ways to manage ports.
One clear winner.

How do your agents coordinate dev ports when they all run at once?

🖥️
Shell Commands
lsof · ss · netstat
  • Agent awarenessNone — agent can't see ports
  • Who calls itYou, manually
  • Port reservationNo — race conditions
  • Multi-agent safeNo — agents conflict
  • Works across toolsNo
⚡
Claude Code Skills
session-scoped · one agent
  • Agent awarenessThis session only
  • Who calls itAgent, via skill
  • Port reservationNo shared state
  • Multi-agent safeNo — one session
  • Works across toolsClaude Code only
Recommended
🔌
PortPeek MCP
portpeek-mcp · shared daemon
  • Agent awarenessAll agents, machine-wide
  • Who calls itAny agent, via MCP
  • Port reservationAtomic — no race conditions
  • Multi-agent safeYes — Claude + Cursor + Copilot
  • Works across toolsAny MCP-compatible agent

Shell commands and skills give one agent port visibility for one moment. PortPeek gives every agent a shared coordination layer — Agent A reserves :3000, Agent B automatically gets a different port. No conflicts. No manual work.

← Get the MCP server