webhooks-cc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHK_API_KEY | No | Optional webhooks.cc API key (starts with whcc_). Without it the server starts in agent sandbox mode and can connect to an account later. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_endpointA | Create a temporary webhook capture endpoint in the agent sandbox (no account needed): up to 3 endpoints at a time, 25 captured requests each and 100 in all, deleted 24 hours after the sandbox was created. The first call registers the sandbox, which takes a few seconds of proof of work. Mock responses, notifications and signature verification need an account: see connect_account. |
| list_endpointsA | List this agent's sandbox endpoints. Empty until create_endpoint starts the sandbox. |
| get_endpointB | Get one of this agent's sandbox endpoints by slug, with its sandbox limits and usage. |
| delete_endpointA | Delete one of this agent's sandbox endpoints and its captured requests. Frees a slot; the sandbox's request budget is not refunded. |
| list_requestsB | List recent requests captured by a sandbox endpoint, newest first. |
| get_requestB | Get full details for a request captured by a sandbox endpoint. |
| wait_for_requestC | Wait for a request to arrive at a sandbox endpoint. |
| generate_payload_schemaA | Generate TypeScript interfaces, Zod schemas, Pydantic models, or JSON Schema from the bodies of requests captured by a sandbox endpoint. Several requests of one event teach which fields are optional or nullable. |
| connect_accountA | Connect this agent to a human's webhooks.cc account, for the full tool set (mock responses, signatures, email, teams) and to keep the sandbox endpoints. Returns a link and a 6-digit code: show both to the human, who signs in or signs up with that email and enters the code. Then call wait_for_connection. Calling again gives a new code. |
| wait_for_connectionA | Wait for the human to enter the code from connect_account. On success the full webhooks.cc tools for their account replace these sandbox tools. Returns after timeoutSeconds (default 45) if they have not finished yet; call it again to keep waiting. |
| about_sandboxA | Explain what this agent can do without a webhooks.cc account, the sandbox limits, and how to connect an account. No network call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| debug_webhook_delivery | Guide an agent through diagnosing why webhook delivery is failing or missing. |
| setup_provider_testing | Guide an agent through setting up webhook testing for a provider. |
| compare_webhook_attempts | Guide an agent through comparing two webhook deliveries or retries. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool maps to a distinct resource and action: endpoint CRUD, request retrieval, and account connection are cleanly separated. The two wait tools (wait_for_connection vs wait_for_request) and the account/sandbox split could momentarily confuse, but descriptions make the boundaries explicit.
Nearly all tools follow a clear verb_noun pattern (create_endpoint, list_requests, get_request, delete_endpoint, generate_payload_schema). The lone exception is about_sandbox, which is a noun-style informational tool rather than verb_noun.
Eleven tools is well-scoped for a webhook capture service: sandbox lifecycle, request inspection, schema generation, and account onboarding each have dedicated tools. about_sandbox is arguably redundant with descriptions but is harmless and explicitly offline.
Endpoint lifecycle (create/list/get/delete) and request inspection (list/get/wait) are fully covered, plus schema generation and an account upgrade path. Minor gaps: no per-request deletion or endpoint update/config tools within the sandbox surface, though those appear to require an account.