gridhra/port-keeper-mcp
by Various
Local ledger for development ports — leases a block per project slot, renders env files, resolves service names to URLs, and serves it all over MCP. No daemon, no listener, no secr
MCP
gridhra/port-keeper-mcp
Added 21 Sept 2026
Overview
Local ledger for development ports. It leases a port block per project slot, renders env files, resolves service names to URLs, and serves the data over MCP. No daemon, no listener, no secrets.
Best for
Best for
Local developers managing port assignments across projects
Use cases
- Lease port blocks for project slots
- Render environment files for services
- Resolve service names to URLs via MCP
How to use
Tools exposed
current_contextresolve_urlresolve_portrender_envslot_newslot_releaselist_all_projects
Tested with
Claude Code, Cursor
Notes
Local ledger for development ports. It leases a port block per project slot, renders env files, resolves service names to URLs, and serves the data over MCP. No daemon, no listener, no secrets.
0 stars on GitHub. Last updated 2026-09-21. Licensed MIT.
Use cases
- Lease port blocks for project slots
- Render environment files for services
- Resolve service names to URLs via MCP
Pros
- No daemon or listener keeps it lightweight
- No secrets stored
- Simple Go binary
Cons
- Zero stars suggests limited community validation
- Local only, no remote coordination
- Requires manual invocation or an MCP client
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- No daemon or listener keeps it lightweight
- No secrets stored
- Simple Go binary
Cons
- Zero stars suggests limited community validation
- Local only, no remote coordination
- Requires manual invocation or an MCP client
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.
