Webhook Capture MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBHOOK_CAPTURE_HOST | No | Bind address. Default: 127.0.0.1. | 127.0.0.1 |
| WEBHOOK_CAPTURE_PORT | No | Port the capture listener binds to. Default: 4444. | 4444 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_statusA | Show the local webhook capture URL, how many requests have been captured, and how to expose it to the internet. |
| list_requestsA | List captured requests (newest first). Optional filters by method, path substring, and count. |
| get_requestA | Get the full detail (method, path, query, headers, body) of one captured request by id. |
| wait_for_requestA | Block until the NEXT webhook arrives (or timeout). Use this to say 'I'll wait, trigger your webhook now' and then inspect what comes in. |
| replay_requestA | Re-send a previously captured request (same method, headers, and body) to a target URL, and return the response. |
| clear_requestsA | Delete all captured requests from the store. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of webhook capture: status, listing, detail retrieval, waiting for new requests, replaying, and clearing. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun snake_case pattern (capture_status, list_requests, get_request, wait_for_request, replay_request, clear_requests), making the set predictable and easy to navigate.
Six tools is a well-scoped count for a webhook capture server, covering essential operations without unnecessary bloat or gaps.
The set provides a complete lifecycle for captured requests: list, get, wait, replay, and clear. A minor gap is the lack of individual request deletion, but clear_requests covers bulk cleanup and the core workflow is fully supported.