pipehero
Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: automate business workflows.Similar tools
Listed for the same task: automate business workflowsReviews
No review yet. Used pipehero? Be the first to help others choose.What it does
pipehero is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to 2 capabilities: api integration and debugging. That makes it a candidate for tasks such as automate business workflows or build an internal tool.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 6h ago (live check)Hosted endpoint
https://mcp.pipehero.app/mcpstreamable-http
In Claude Code: claude mcp add --transport http pipehero https://mcp.pipehero.app/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"pipehero": {
"url": "https://mcp.pipehero.app/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 6h agoONLINE pipehero answered an MCP connection on 16 Nov 2026 and introduced itself as pipehero 0.1.18 (MCP protocol 2025-06-18).
25 tools offered to AI assistants
list_tunnels· List the user's Pipehero tunnels and whether each is currently online.list_requests· List recent webhooks/requests captured for a tunnel. Returns id, method, path, status and bodies.get_request· Get the full request and response (headers + body) of one captured webhook by id.replay_request· Replay a captured webhook to the user's localhost (the tunnel CLI must be running).send_test_webhook· Send a generated test webhook to the user's localhost (the tunnel CLI must be running). Provide a `provider` (stripe, github, shopify, clerk, slack, resend, paddle, polar, lemonsqueezy) and optional `event` for a realistic sample payload, oset_long_requests· Opt a tunnel into a 120-second ingress timeout instead of the 30-second default — for tool calls that legitimately run long, e.g. an MCP server exposed through the tunnel. Persists on the tunnel; pass enabled: false to revert to the 30-secoset_ws_passthrough· Opt a tunnel into WebSocket passthrough, so an application-level WebSocket connection (e.g. a mobile/web app's own realtime feature) can be relayed to your localhost. Pro/Team plan required to enable; pass enabled: false to disable on any plist_api_collections· List the workspace's API collections (saved endpoints with examples and environments). Start here to find a collection_id.get_api_collection· Get one collection's folders, endpoints (id, method, path, name, version, example count) and environments (with their variables).get_api_endpoint· Get one endpoint in full: description, parameters, headers, request body, saved response examples and its current `version`. Identify it by endpoint_id or by method + path.create_api_collection· Create an empty API collection. Prefer import_api_spec when there is an OpenAPI file, and upsert_api_endpoint to fill it from the code.upsert_api_endpoint· Document an endpoint: creates it, or updates the existing one for the same method + path. Use it whenever you add or change a route in the code, so the docs stay true. Only the fields you send change. `path` may use :id, {id} or {{id}} for
Show 13 more
add_api_example· Save a response example on an endpoint (for instance the 402 your handler returns for a declined card). Replaces the example with the same name, so it is safe to repeat.delete_api_endpoint· Delete an endpoint and its examples. Use when the route no longer exists in the code. Cannot be undone.import_api_spec· Import an OpenAPI 3.x document (as JSON), a Postman v2.x collection (JSON) or a curl command into a new collection, or into `collection_id`. All or nothing, and plan limits are checked first. Credentials are never imported (they become variexport_api_collection· Export a collection as an OpenAPI 3.1 or Postman 2.1 document. Handy to read the whole API at once.run_api_endpoint· Send an endpoint against an environment and return the real response (status, headers, body up to 20 KB). A `local` environment goes through the user's tunnel to their localhost (the CLI must be running); staging/prod are sent from Pipeherosave_captured_request· Document a real request captured by a tunnel (get its id from list_requests). If an endpoint already covers the route, the response is added to it as an example; otherwise an endpoint is created from the request. Credentials, cookies and silist_api_monitors· See which endpoints of a collection are checked on a schedule (Pro/Team monitors) and how they are doing: state (healthy, failing, blip, paused, waiting), the last check with its status, latency and error, and since when it has been failinglist_api_proposals· See what happened to the changes you proposed. Some workspaces review AI changes: your write tools then answer `pending_review` and change nothing until a teammate approves. This lists the latest proposals with their status (pending, approvcheck_api_drift· Compare a collection's docs with the real traffic a tunnel captured (Pro/Team). Returns routes nobody documented, status codes with no example, response or request fields missing from every example (or with another type), undocumented queryget_api_share_link· Get the shareable link of an endpoint (a read-only page with its docs, examples and latest run, secrets hidden), who can open it and who was invited. Use it to put the link in a PR, an issue or a message. Each endpoint has one link that nevshare_api_endpoint· Create an endpoint's shareable link and return it. With no other arguments the link stays restricted: workspace members can open it (they sign in), which is enough for a PR or an internal message. Only when the user asks to share it outsideshare_api_collection· Share a whole collection: every endpoint in it (including ones added later), with its examples and latest run, read-only and with secrets hidden. Environments are never shown and it can't be exported. Returns the collection's link, which nelist_api_runs· Recent runs of an endpoint (newest first, default 5): who/what was sent and what came back. Use to see what happened the last time it was run.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.pipehero.app/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://pipehero.app | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/pipehero/pipehero-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 0.1.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is pipehero still online?
Free alerts · no account▲ 0Do you run pipehero? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about pipehero
How do I connect pipehero?
Use the hosted endpoint https://mcp.pipehero.app/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does pipehero offer?
When Electra Index connected on 16 Nov 2026, it listed 25 tools: list_tunnels, list_requests, get_request, replay_request, send_test_webhook, set_long_requests, set_ws_passthrough, list_api_collections and more. The full list is in "Live check" above.
Is pipehero online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 6h ago.
What can I use pipehero for?
Based on its description, it is most relevant to: automate business workflows, build an internal tool, fix bugs in a codebase, integrate two APIs.