HasanJahidul/localhost-mcp

Overview

MCP server that inspects, manages, and kills local development servers. It identifies which process is running on a given port, allowing developers to stop guessing and take action directly from their MCP-compatible tools.

Best for

Best for
Developers who frequently run multiple local servers and want a quick MCP-based way to inspect and manage them.

Use cases

• Identify which process is using a specific port like :3000
• Kill a local dev server that is stuck or no longer needed
• List all running local servers and their ports

Notes

MCP server that inspects, manages, and kills local development servers. It identifies which process is running on a given port, allowing developers to stop guessing and take action directly from their MCP-compatible tools.

1 stars on GitHub. Last updated 2026-05-11. Licensed MIT.

Use cases

• Identify which process is using a specific port like :3000
• Kill a local dev server that is stuck or no longer needed
• List all running local servers and their ports

Pros

• Simple, focused tool for a common developer pain point
• Integrates with MCP ecosystem for seamless use in editors and IDEs
• Written in TypeScript, easy to extend or contribute to

Cons

• Very early stage with only 1 star, limited community and testing
• May not handle all edge cases like multiple processes on same port or non-standard setups
• Requires MCP-compatible client to be useful, not a standalone tool

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.