port-keeper-mcp
Related Servers
Alternatives to port-keeper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to coordinate ports and dev servers on a shared Linux machine, reserve ports, start and stop worktree servers, inspect listening services, Tailscale devices and dev worktrees, and clean up safely without collisions.1 npmMIT
- AlicenseNot gradedqualityDmaintenanceSee and control the local dev servers your coding agents leave running. Lists listeners with provenance — which agent, terminal and git worktree started each — kills strays, and allocates collision-free ports so parallel agents stop fighting over :3000.MIT
- AlicenseNot gradedqualityBmaintenanceEnables parallel coding agents to bootstrap isolated development checkouts with copy-on-write dependencies, synchronized environment files, and automatic port shifting.303 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to inspect projects, claim worktrees, and move or start dev servers without changing ports, while coordinating with human-owned locks.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to deterministically discover which localhost ports and env URLs are actually running, resolving declared configs, OS listeners, and service connections into a machine-readable .portmap.json with actionable findings.1 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.158 npmMIT
TDQS
Scored across 6 tools
Each tool has a clear, single responsibility: context, env rendering, port resolution, URL resolution, slot creation, and status. No two tools overlap; even resolve_port and resolve_url are distinguished by use case.
Most tools follow verb_noun (render_env, resolve_port, resolve_url, slot_new) but current_context and status are noun phrases. The snake_case style is consistent, but the grammatical pattern is mixed.
With 6 tools, the set is well-scoped for a port/slot management server. Each tool serves a distinct need without bloat.
The core lifecycle (create slot, resolve ports, render env, check status) is covered, but there is no explicit 'delete slot' or 'release ports' tool, which might be a minor gap for full lifecycle management.