Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Start, stop and read logs of your local dev servers from Claude Code, Cursor and Codex.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"localhost": {
"command": "npx",
"args": [
"-y",
"@getlocalhost/cli",
"mcp",
"serve"
]
}
}
}Run this in your terminal
claude mcp add localhost -- npx -y @getlocalhost/cli mcp servePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"localhost": {
"command": "npx",
"args": [
"-y",
"@getlocalhost/cli",
"mcp",
"serve"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"localhost": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@getlocalhost/cli",
"mcp",
"serve"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account marcellosso, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connects your coding agents to localhost mcp, the MCP server of localhost app, from a terminal:
npx @getlocalhost/cli mcp install
It adds a server named localhost to Claude Code, Claude Desktop, Cursor and Codex, whichever are on this computer, and installs the localhost-mcp skill where each agent reads skills. The server runs the localhost command that comes with the app, so the app must be installed: without it, this prints how to install it for your OS and changes nothing.
It writes what Settings → Agents in the app writes, and the app shows these agents as connected:
| Agent | MCP server added to | Skill installed in |
|---|---|---|
| Claude Code | ~/.claude.json, through claude mcp add-json --scope user when claude is installed | ~/.claude/skills/localhost-mcp/ |
| Claude Desktop (macOS, Windows) | claude_desktop_config.json in Claude's folder (~/Library/Application Support/Claude, %APPDATA%\Claude) | none: it has no skills folder |
| Cursor | ~/.cursor/mcp.json | ~/.cursor/skills/localhost-mcp/, unless Claude Code's or Codex's folder has it: Cursor reads those too |
| Codex | ~/.codex/config.toml | ~/.agents/skills/localhost-mcp/ |
agent-backups folder of localhost's data folder, before it first changes a file.npx @getlocalhost/cli mcp install # add the server and the skill
npx @getlocalhost/cli mcp uninstall # remove them, and nothing else npx @getlocalhost/cli mcp status # where each agent stands npx @getlocalhost/cli mcp serve # run the server, for an MCP client's configuration
| Option | |
|---|---|
--client | claude-code, claude-desktop, cursor or codex; claude for both Claude apps. Repeat it, or separate with commas, for more than one. Without it: every agent found on this computer. |
--read-only | For mcp install and mcp serve. The server runs localhost mcp --read-only, without the tools that add, edit or remove Projects and Services. Needs a localhost app that has it (0.4.0 or later). Installing again without it keeps a read-only server read-only. |
--dry-run | Prints what would change, as a diff, and changes nothing. |
Then start a new Claude Code session, quit and reopen Claude Desktop, check Cursor Settings → MCP, or restart Codex.
mcp serve is the server itself, for any client that starts MCP servers over stdio:
{
"mcpServers": { "localhost": { "command": "npx", "args": ["-y", "@getlocalhost/cli", "mcp", "serve"] } } }
It finds the app's localhost command as mcp install does and runs localhost mcp with the client's stdin and stdout, passing on Ctrl-C and other signals and exiting as the server does. mcp serve --read-only runs localhost mcp --read-only. It writes nothing to stdout itself, since that is the client's channel: without the app, or with an app whose command doesn't run, it says why on stderr and exits with 1. claude mcp add --scope user localhost -- npx -y @getlocalhost/cli mcp serve and codex mcp add localhost -- npx -y @getlocalhost/cli mcp serve add it from a terminal.
More in the MCP docs. Node 18 or later; no dependencies.
cd packages/cli
npm test node bin/getlocalhost.js mcp status
The JSON and TOML editors are the same as the core's (core/localhost-core/src/agents/), and their tests too: change both together. npm pack copies the skill from skills/localhost-mcp into the package.