Pipehero — Webhook tunnels and an API workspace, debugged by
Pipehero
Expose localhost and debug every webhook, then document, test and monitor your API from real traffic, with an AI agent that keeps the docs current (MCP).
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.pipehero.app
22tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.pipehero.app/mcp
Skill page: https://www.mcpbundles.com/skills/pipehero-mcp-d247a36a3b
Explore capabilities (22)
read 11
write 11
List
6
Get
3
Set
2
Other capabilities
11
List Tunnels
read
list_tunnels
List the user's Pipehero tunnels and whether each is currently online.
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, or pass a custom JSON `body`. Pro plan required.
Set 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-second default.
Set 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 plan.
List 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.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
What is the Pipehero — Webhook tunnels and an API workspace, debugged by MCP server?
Expose localhost and debug every webhook, then document, test and monitor your API from real traffic, with an AI agent that keeps the docs current (MCP).
How do I connect Pipehero — Webhook tunnels and an API workspace, debugged by to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate this server?
Request removal if you do not want Pipehero — Webhook tunnels and an API workspace, debugged by listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Pipehero — Webhook tunnels and an API workspace, debugged by?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
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 variables. `folder` is created by name if missing. Send `version` (from get_api_endpoint) to avoid overwriting a teammate's edit; a stale version is rejected.
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 variables). Convert YAML to JSON before sending.
Export 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 Pipehero's cloud (Pro/Team) to public addresses only. Sending to a `prod` environment with a write method needs confirm_write_to_prod: true, which you should only pass after the user agrees. Use it to check that the code you wrote behaves as documented.
Save 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 signatures are replaced by {{variables}} and only JSON bodies are kept. A response already saved as an example is not duplicated. Use it to document webhooks and calls you have only seen in traffic.
List 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 failing. Use it to find out what is broken in staging or production, then read the endpoint and its code. Read-only: people decide what to monitor.
List 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, approved, rejected with the reviewer's reason, or failed with why) so you can tell whether a change went through.
Check 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 query parameters, and documented fields that never appear. Each finding includes `request_id` of the newest request that shows it: pass it to save_captured_request to add it to the docs, or fix the docs with upsert_api_endpoint and add_api_example. Use it to find o
List 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.
How many tools does Pipehero — Webhook tunnels and an API workspace, debugged by provide?
MCPBundles probed 22 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Pipehero — Webhook tunnels and an API workspace, debugged by require?
Pipehero — Webhook tunnels and an API workspace, debugged by may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.