Give Claude direct access to port management, service orchestration, and agent coordination through the Model Context Protocol.
MCP (Model Context Protocol) is an open standard that lets AI assistants interact with external tools and data sources. Port Daddy ships a full MCP server that turns 25+ operations into tools Claude can call directly.
Claude calls Port Daddy tools directly instead of shelling out to the CLI. Structured inputs, typed outputs, zero parsing.
Every Claude session gets its own agent identity. Sessions, file claims, pub/sub, and locks all work across parallel agents.
Compatible with Claude Code, Claude Desktop, and any MCP-capable client. One server, every surface.
Add Port Daddy's MCP server to your Claude configuration. The daemon starts automatically on first use.
Add to .claude/settings.json or project settings
// .claude/settings.json
{
"mcpServers": {
"port-daddy": {
"command": "pd",
"args": ["mcp"]
}
}
}
Add to claude_desktop_config.json
// ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"port-daddy": {
"command": "npx",
"args": ["port-daddy", "mcp"]
}
}
}
Every tool accepts structured JSON inputs and returns typed responses. No string parsing, no guessing.
myapp:api:main and returns a guaranteed-free port.The MCP server exposes 5 read-only resources that Claude can inspect at any time. These reflect the live state of your development environment.
With the MCP server connected, Claude understands port management natively. Just describe what you need.
"Claim port 3100 for my-api and start a session to track the work."
"Check if any agents have died and show me their session notes."
"Start a tunnel for my frontend service so I can test on my phone."
"Lock the database-migrations resource while I run migrations."