MCP server: inspect, manage, kill local dev servers. Stop guessing what's on :3000.
MCP server: inspect, manage, kill local dev servers. Stop guessing what's on :3000. The localhost mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
list_dev_servers — All listening dev servers w/ port, pid, framework, project, uptime, mem, cpuport_info — Inspect single port — who holds itkill_server — Kill by pid or port. Dry-run by default; pass confirm=true to executefind_zombies — Detect long-running, idle, memory-heavy dev serversport_conflict — Why is port X busy + 5 free alternatives nearbylocalhost-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Localhost MCP's toolset — list_dev_servers, port_info, kill_server and 2 more — is a fair guide to whether it matches your workflow. It is maintained by HasanJahidul; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_dev_servers | All listening dev servers w/ port, pid, framework, project, uptime, mem, cpu |
| port_info | Inspect single port — who holds it |
| kill_server | Kill by pid or port. Dry-run by default; pass confirm=true to execute |
| find_zombies | Detect long-running, idle, memory-heavy dev servers |
| port_conflict | Why is port X busy + 5 free alternatives nearby |
{
"mcpServers": {
"localhost": {
"command": "npx",
"args": ["-y", "localhost-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.