Connect-MCP

io.github.pipehero/pipehero

io.github.pipehero/pipehero · v0.1.0

Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.

MCPremoteno credentialsDocuments & PDF

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 25 tools, protocol 2024-11-05 · checked 2026-10-17

Test & rating

B 81/100

What it does: 25 tools · 12 read, 13 write (incl. delete/pay) · Developer tools, Documents & PDF

Test call list_tunnels: needs a key: rpc error: authorization required (1,013 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +3
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://mcp.pipehero.app/mcp

Tools

25 tools listed at last check
  • 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.
  • 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 `ver
  • 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 `
  • 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
  • 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
  • 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)
  • 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 f
  • get_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 never changes; `shared: false` means it has none yet (see share
  • share_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 outside the workspace: set `link_access` to `viewer` (anyone with t
  • share_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 never changes. With no other arguments it stays restricted to
  • 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.

Badge

Connect-MCP badge for io.github.pipehero/pipehero

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.pipehero/pipehero.svg)](https://clawy.uk/mcp/s/io.github.pipehero/pipehero)

Repository · Website