Skip to main content
Glama
gridhra

port-keeper-mcp

by gridhra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to port-keeper-mcp

No user-submitted related servers found.

    Related Servers

    • tidyports

      dan-fetch-studio
      A
      license
      Not graded
      quality
      B
      maintenance
      See 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

    • worktree-switcher

      pioootrek
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to inspect projects, claim worktrees, and move or start dev servers without changing ports, while coordinating with human-owned locks.
      MIT

    • portmap

      paladini
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      6 npm
      MIT

    • Harbor MCP Server

      luke-fairbanks
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      232 npm
      MIT

    • MCP Port Manager

      sooth
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for managing port registrations on your computer. Keep track of which applications are using which ports, find free ports, and maintain a central registry of port allocations.
      5
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a port/slot management server. Each tool serves a distinct need without bloat.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources