hookray-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOOKRAY_API_KEY | No | Required for persistent inboxes. Get one at hookray.com/app/settings/api-keys. | |
| HOOKRAY_BASE_URL | No | Override for self-hosting or local dev. | https://hookray.com |
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 |
|---|---|
| create_webhook_inboxA | Create a new HookRay webhook inbox and return its public capture URL. |
| list_requestsB | List webhook requests captured by a HookRay inbox. |
| inspect_requestB | Inspect the full headers, body, query params, and metadata for a captured request. |
| wait_for_requestB | Block until a new webhook arrives at an inbox, or return a timeout result. |
| replay_requestB | Replay a captured HookRay request to any destination reachable from this machine. |
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 5 tools
Each tool has a clearly distinct purpose: creating an inbox, listing requests, inspecting a request, replaying a request, and waiting for new requests. No ambiguity between them.
All tools follow a consistent verb_noun pattern (e.g., create_webhook_inbox, list_requests). No mixing of conventions.
With 5 tools, the set is well-scoped for a webhook debugging server. Not too few or too many.
Core operations are covered (create, list, inspect, replay, wait). Missing delete functionality for inboxes or requests, but the agent can work around this minor gap.