pipehero
Debug webhooks from your AI agent: inspect and replay captured webhooks on localhost.
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"pipehero": {
"url": "https://mcp.pipehero.app/mcp"
}
}
}Puntos de conexión remotos
https://mcp.pipehero.app/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (25)
🟢list_tunnels
List the user's Pipehero tunnels and whether each is currently online.
Esquema de entrada
{
"type": "object",
"properties": {}
}🟢list_requests(subdomain)
List recent webhooks/requests captured for a tunnel. Returns id, method, path, status and bodies.
Esquema de entrada
{
"type": "object",
"properties": {
"subdomain": {
"description": "Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.",
"type": "string"
}
},
"required": [
"subdomain"
]
}🟢get_request(id, subdomain)
Get the full request and response (headers + body) of one captured webhook by id.
Esquema de entrada
{
"type": "object",
"properties": {
"id": {
"description": "Id of the captured request, from list_requests.",
"type": "string"
},
"subdomain": {
"description": "Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.",
"type": "string"
}
},
"required": [
"subdomain",
"id"
]
}🔴replay_request(id, subdomain)
Replay a captured webhook to the user's localhost (the tunnel CLI must be running).
Esquema de entrada
{
"type": "object",
"properties": {
"id": {
"description": "Id of the captured request, from list_requests.",
"type": "string"
},
"subdomain": {
"description": "Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.",
"type": "string"
}
},
"required": [
"subdomain",
"id"
]
}🔴send_test_webhook(body, event, provider, subdomain)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"body": {
"description": "Custom JSON body (overrides the template)",
"type": "string"
},
"event": {
"description": "Provider event type, e.g. payment_intent.succeeded for stripe or push for github. Omit for the provider's default event.",
"type": "string"
},
"provider": {
"description": "Provider whose sample payload and signature to use: stripe, github, shopify, clerk, slack, resend, paddle, polar or lemonsqueezy.",
"type": "string"
},
"subdomain": {
"description": "Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.",
"type": "string"
}
},
"required": [
"subdomain",
"provider"
]
}🟡set_long_requests(enabled, subdomain)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"enabled": {
"description": "true for the 120-second timeout, false to go back to the 30-second default.",
"type": "boolean"
},
"subdomain": {
"description": "Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.",
"type": "string"
}
},
"required": [
"subdomain",
"enabled"
]
}🟡set_ws_passthrough(enabled, subdomain)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"enabled": {
"description": "true to relay WebSocket connections to localhost (Pro/Team), false to turn it off.",
"type": "boolean"
},
"subdomain": {
"description": "Tunnel subdomain, from list_tunnels, e.g. myapp for https://myapp.t.pipehero.app.",
"type": "string"
}
},
"required": [
"subdomain",
"enabled"
]
}🟢list_api_collections
List the workspace's API collections (saved endpoints with examples and environments). Start here to find a collection_id.
Esquema de entrada
{
"type": "object",
"properties": {}
}🟢get_api_collection(collection_id)
Get one collection's folders, endpoints (id, method, path, name, version, example count) and environments (with their variables).
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
}
},
"required": [
"collection_id"
]
}🟢get_api_endpoint(collection_id, endpoint_id, method, path)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"endpoint_id": {
"description": "Id of the endpoint. Alternative to method + path.",
"type": "string"
},
"method": {
"description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id.",
"type": "string"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
}
},
"required": [
"collection_id"
]
}🟡create_api_collection(description, name)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"description": {
"description": "What the API is for.",
"type": "string"
},
"name": {
"description": "Collection name, e.g. Payments API.",
"type": "string"
}
},
"required": [
"name"
]
}🟡upsert_api_endpoint(body, collection_id, description, folder, headers, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"body": {
"description": "Example request body, any JSON, e.g. {\"amount\": 1000}. null clears it.",
"type": [
"object",
"array",
"string",
"number",
"boolean",
"null"
]
},
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"description": {
"description": "What the endpoint does and when to call it.",
"type": "string"
},
"folder": {
"description": "Folder name, e.g. Charges.",
"type": "string"
},
"headers": {
"description": "Request headers to send, e.g. [{\"name\": \"Authorization\", \"value\": \"Bearer {{token}}\"}].",
"items": {
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
],
"type": "object"
},
"type": "array"
},
"kind": {
"description": "`event` for a webhook your app sends.",
"enum": [
"http",
"event"
],
"type": "string"
},
"method": {
"description": "HTTP method, e.g. POST. For an `event`, the method it is delivered with.",
"type": "string"
},
"name": {
"description": "Short title, e.g. Create a charge. Defaults to METHOD /path.",
"type": "string"
},
"params": {
"description": "Documented fields.",
"items": {
"properties": {
"description": {
"type": "string"
},
"in": {
"enum": [
"path",
"query",
"header",
"body"
],
"type": "string"
},
"name": {
"type": "string"
},
"required": {
"type": "boolean"
},
"type": {
"type": "string"
}
},
"required": [
"name"
],
"type": "object"
},
"type": "array"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
},
"version": {
"description": "The endpoint's `version` from get_api_endpoint. Omit for a new endpoint.",
"type": "integer"
}
},
"required": [
"collection_id",
"method",
"path"
]
}🟡add_api_example(body, collection_id, endpoint_id, headers, method, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"body": {
"description": "Example response body, any JSON, e.g. {\"error\": \"card_declined\"}.",
"type": [
"object",
"array",
"string",
"number",
"boolean",
"null"
]
},
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"endpoint_id": {
"description": "Id of the endpoint. Alternative to method + path.",
"type": "string"
},
"headers": {
"description": "Response headers of the example, e.g. [{\"name\": \"Content-Type\", \"value\": \"application/json\"}].",
"items": {
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
],
"type": "object"
},
"type": "array"
},
"method": {
"description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id.",
"type": "string"
},
"name": {
"description": "e.g. Card declined.",
"type": "string"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
},
"status": {
"description": "HTTP status code of the response, e.g. 402.",
"type": "integer"
},
"status_text": {
"description": "Reason phrase, e.g. Payment Required.",
"type": "string"
}
},
"required": [
"collection_id",
"name",
"status"
]
}🔴delete_api_endpoint(collection_id, endpoint_id, method, path)
Delete an endpoint and its examples. Use when the route no longer exists in the code. Cannot be undone.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"endpoint_id": {
"description": "Id of the endpoint. Alternative to method + path.",
"type": "string"
},
"method": {
"description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id.",
"type": "string"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
}
},
"required": [
"collection_id"
]
}⚪import_api_spec(collection_id, content, format, name)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Add to this collection instead of creating one.",
"type": "string"
},
"content": {
"description": "The document (object or JSON string), or the curl command, e.g. curl -X POST https://api.example.com/v1/charges.",
"type": [
"object",
"string"
]
},
"format": {
"description": "What `content` is: an OpenAPI 3.x document, a Postman v2.x collection, a HAR file or a curl command.",
"enum": [
"openapi",
"postman",
"har",
"curl"
],
"type": "string"
},
"name": {
"description": "Name for the new collection.",
"type": "string"
}
},
"required": [
"format",
"content"
]
}🟢export_api_collection(collection_id, format)
Export a collection as an OpenAPI 3.1 or Postman 2.1 document. Handy to read the whole API at once.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"format": {
"description": "openapi (OpenAPI 3.1, the default) or postman (Postman 2.1).",
"enum": [
"openapi",
"postman"
],
"type": "string"
}
},
"required": [
"collection_id"
]
}🔴run_api_endpoint(collection_id, confirm_write_to_prod, endpoint_id, environment, method, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"confirm_write_to_prod": {
"description": "Needed to send a write method (POST, PUT, PATCH, DELETE) to a prod environment. Only pass true after the user agrees.",
"type": "boolean"
},
"endpoint_id": {
"description": "Id of the endpoint. Alternative to method + path.",
"type": "string"
},
"environment": {
"description": "Environment name or id, e.g. local.",
"type": "string"
},
"method": {
"description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id.",
"type": "string"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
},
"variables": {
"additionalProperties": {
"type": "string"
},
"description": "Values for {{variables}} the environment doesn't define, e.g. {\"id\": \"ch_123\"}.",
"type": "object"
}
},
"required": [
"collection_id",
"environment"
]
}🟡save_captured_request(collection_id, endpoint_id, folder, method, path, ...)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"endpoint_id": {
"description": "Add the example to this endpoint instead of matching by route. Alternative to method + path.",
"type": "string"
},
"folder": {
"description": "Folder for a newly created endpoint, created by name if missing.",
"type": "string"
},
"method": {
"description": "With path: the endpoint that should receive the example.",
"type": "string"
},
"path": {
"description": "With method: route path of the endpoint, e.g. /v1/charges/:id.",
"type": "string"
},
"request_id": {
"description": "Id of the captured request, from list_requests.",
"type": "string"
},
"tunnel": {
"description": "Subdomain of the tunnel that captured the request.",
"type": "string"
}
},
"required": [
"collection_id",
"tunnel",
"request_id"
]
}🟢list_api_monitors(collection_id)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
}
},
"required": [
"collection_id"
]
}🟢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.
Esquema de entrada
{
"type": "object",
"properties": {}
}🟢check_api_drift(collection_id, limit, tunnel)
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 out what drifted after a code change.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"limit": {
"description": "How many recent requests to compare (default 200, max 500).",
"type": "integer"
},
"tunnel": {
"description": "Subdomain of the tunnel whose traffic to compare.",
"type": "string"
}
},
"required": [
"collection_id",
"tunnel"
]
}🟢get_api_share_link(collection_id, endpoint_id, method, path)
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_api_endpoint).
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"endpoint_id": {
"description": "Id of the endpoint. Alternative to method + path.",
"type": "string"
},
"method": {
"description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id.",
"type": "string"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
}
},
"required": [
"collection_id"
]
}🟡share_api_endpoint(collection_id, endpoint_id, invite, link_access, method, ...)
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 the link can read) or `commenter` (Team plan; commenting asks for sign-in), or `invite` people by email (they get an email and sign in with that address). `restricted` turns the public link off; the URL stays the same. The page is read-only and always hides credentials and secrets.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"endpoint_id": {
"description": "Id of the endpoint. Alternative to method + path.",
"type": "string"
},
"invite": {
"description": "People to invite by email (at most 10). Each gets an email.",
"items": {
"properties": {
"email": {
"type": "string"
},
"role": {
"enum": [
"viewer",
"commenter"
],
"type": "string"
}
},
"required": [
"email"
],
"type": "object"
},
"type": "array"
},
"link_access": {
"description": "Who can open it with just the link. Omit to keep the current setting (restricted for a new share).",
"enum": [
"restricted",
"viewer",
"commenter"
],
"type": "string"
},
"method": {
"description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id.",
"type": "string"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
}
},
"required": [
"collection_id"
]
}🟡share_api_collection(collection_id, invite, link_access)
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 the workspace; set `link_access` or `invite` people only when the user asks to share it outside the team. get_api_collection returns the link as `share` once it exists.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"invite": {
"description": "People to invite by email (at most 10). Each gets an email.",
"items": {
"properties": {
"email": {
"type": "string"
},
"role": {
"enum": [
"viewer",
"commenter"
],
"type": "string"
}
},
"required": [
"email"
],
"type": "object"
},
"type": "array"
},
"link_access": {
"description": "Who can open it with just the link. Omit to keep the current setting (restricted for a new share).",
"enum": [
"restricted",
"viewer",
"commenter"
],
"type": "string"
}
},
"required": [
"collection_id"
]
}🟢list_api_runs(collection_id, endpoint_id, limit, method, path)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"collection_id": {
"description": "Id from list_api_collections.",
"type": "string"
},
"endpoint_id": {
"description": "Id of the endpoint. Alternative to method + path.",
"type": "string"
},
"limit": {
"description": "How many runs to return, 1 to 20 (default 5).",
"type": "integer"
},
"method": {
"description": "HTTP method of the route, e.g. POST. Use with path instead of endpoint_id.",
"type": "string"
},
"path": {
"description": "Route path as written in the code, e.g. /v1/charges/:id or /v1/charges/{id}.",
"type": "string"
}
},
"required": [
"collection_id"
]
}Prompts recomendados
list_tunnelsget_requestget_requestlist_tunnelsget_requestlist_tunnelsComunidad
Evidencia