Skip to main content
Glama
Sign In
localhost-mcp

localhost-mcp

by HasanJahidul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to localhost-mcp

  • Terminal History MCP

    HasanJahidul
    A
    license
    A
    quality
    C
    maintenance
    Developers: Search your zsh, bash, or fish shell history from Claude Code, Cline, Cursor, Zed, or any MCP client using tools like search_history (full-text with timestamp/CWD/exit code), recent_in_dir, failed_commands, and command_chains for multi-step sequences. Reindex after new activity. Local-only SQLite FTS5 with secrets redacted before storage.
    7
    149 npm
    5
    MIT

Related Servers

  • wharfy

    egebilge
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for managing local dev ports on macOS. It enables AI agents to inspect listening ports, identify owning processes and parent chains, kill processes safely, wait for ports, and report LAN exposure.
    8 npm
    1
    MIT

  • portcheck

    roystondwork-dev
    A
    license
    A
    quality
    B
    maintenance
    See which process holds a local port and who started it, find free ports, wait for services, and stop a dev server safely. Fixes "port already in use" (EADDRINUSE) for AI coding assistants. Never stops system processes; Docker and WSL ports get the right stop command. Run with: npx -y portcheck-cli mcp
    5
    1
    MIT

  • tidyports

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

  • port-doctor-mcp

    GrantKnoche
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables developers to inspect port occupancy with process details, scan common development ports, and terminate processes blocking a specified port via MCP tools.
    MIT

  • localhost

    danilolekovic
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP-capable coding agents to discover local development servers, inspect them by port or PID, and safely terminate verified listeners with confirmation and fresh discovery before signaling.
    7 npm
    MIT

  • Paddock

    igbaryya
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables an AI agent to manage local development environments over MCP by starting, stopping, and restarting applications and processes, reading logs with cursors, and inspecting or freeing listening ports. Exposes a fixed set of id- and port-based tools, so the agent can operate registered processes without running arbitrary commands.
    4 npm
    MIT
Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing servers, inspecting a single port, finding zombies, killing servers, and diagnosing port conflicts. There is no functional overlap.

Naming Consistency4/5

Tool names use snake_case, and most follow a verb_noun pattern (find_zombies, kill_server, list_dev_servers). However, port_conflict and port_info are noun-first, which is a minor inconsistency.

Tool Count5/5

With 5 tools, the set is well-scoped for managing local dev servers: query, inspect, cleanup, and conflict resolution. No tool feels superfluous or missing.

Completeness4/5

The tools cover listing, inspecting, zombie identification, killing, and conflict diagnosis. There is a minor gap in that bulk operations (e.g., kill all zombies) are not directly supported, but the intended workflow is clear.

Maintenance

ActivityInactive
ResponsivenessLimited data

Resources