Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.
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 …”.
Works in Claude on the web, desktop and mobile:
https://mcp.pipehero.app/mcpRun this in your terminal
claude mcp add --transport http pipehero https://mcp.pipehero.app/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pipehero": {
"url": "https://mcp.pipehero.app/mcp"
}
}
}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": {
"pipehero": {
"type": "http",
"url": "https://mcp.pipehero.app/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://mcp.pipehero.app/mcpMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 7, 2026
The registry name was verified with the GitHub account pipehero, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
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.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
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.
Pipehero tunnels your localhost to a public URL and captures every webhook, so you can inspect, replay, and debug them — including from your AI agent via MCP.
This repo is auto-published from Pipehero's source. It holds the public MCP manifest
and the agent skill. Issues/PRs welcome.
Let an agent (Claude Code, Cursor, Copilot, Windsurf, Zed, …) list your tunnels, read captured webhooks, and replay them to localhost.
claude mcp add --transport http pipehero https://mcp.pipehero.app/mcp
Your client opens the browser to sign in and approve — no token to paste.
For CI/headless, pass a token from https://pipehero.app/dashboard/settings:
claude mcp add --transport http pipehero https://mcp.pipehero.app/mcp \
--header "Authorization: Bearer "
curl -fsSL https://pipehero.app/install | sh
pipehero login claude mcp add pipehero -- pipehero mcp
Any MCP client works — add it to .cursor/mcp.json, claude_desktop_config.json, etc.:
{ "mcpServers": { "pipehero": { "command": "pipehero", "args": ["mcp"] } } }
| Tool | What it does |
|---|---|
list_tunnels | Your tunnels and whether each is online. |
list_requests(subdomain) | Recent captured webhooks for a tunnel. |
get_request(subdomain, id) | Full request + response (headers + body). |
replay_request(subdomain, id) | Replay a webhook to your localhost. |
start_tunnel(name, port) | Expose a local port on a public URL (local MCP only). |
stop_tunnel(name) | Stop a tunnel started with start_tunnel (local MCP only). |
list_api_collections, get_api_collection(collection_id) | Your saved API docs: folders, endpoints, environments (remote MCP, and local from 0.1.14). |
get_api_endpoint(collection_id, method + path) | One endpoint in full, with its version and response examples. |
upsert_api_endpoint(collection_id, method, path, …) | Create or update an endpoint by route, so docs follow your code. |
add_api_example(collection_id, method + path, name, status, …) | Save a response example. |
delete_api_endpoint(collection_id, method + path) | Remove an endpoint whose route is gone. |
import_api_spec(format, content) / export_api_collection(collection_id) | OpenAPI, Postman and curl, both ways. |
run_api_endpoint(collection_id, method + path, environment) | Send it and read the real response. |
save_captured_request(collection_id, tunnel, request_id) | Turn a real captured request into docs, without credentials. |
check_api_drift(collection_id, tunnel) | Compare the docs with real traffic (Pro/Team). |
list_api_monitors(collection_id) | Which endpoints are monitored and which are failing, with the last error (Pro/Team). |
list_api_proposals | What happened to your proposed changes, on workspaces that review AI changes. |
get_api_share_link(collection_id, method + path) | The endpoint's shareable link: a read-only page with its docs, examples and latest run. |
share_api_endpoint(collection_id, method + path, …) | Create that link (workspace-only by default), open it to anyone with the link, or invite people by email. |
share_api_collection(collection_id, …) | The same for a whole collection: every endpoint, read-only, never its environments. |
Because your agent has both the captured webhook and your codebase, it can explain *why* a handler failed — then fix it and replay to confirm.
Install the skill so your agent knows *when and how* to use Pipehero:
pipehero skill install
or copy SKILL.md into ~/.claude/skills/pipehero/SKILL.md.
MIT