korb
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KORB_TOKEN | No | API token created in the dashboard (Settings → API tokens). If omitted, the MCP server uses the saved korb login credentials. | |
| KORB_API_BASE | No | Override the default korb API endpoint (default is https://korb.sh). |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_failedA | List webhook events whose deliveries failed or partially failed, newest first. Use this first when a webhook consumer is misbehaving; follow up with get_payload to inspect what was sent and replay to redeliver once fixed. |
| get_payloadA | Fetch one stored webhook event: headers and full body exactly as received. The id comes from list_failed (or the dashboard inbox). |
| replayA | Redeliver one stored event to its routed destinations (same event id, korb-replay header set, receivers' own dedupe applies). Requires a read+write token. |
| send_testA | Fire a preset's test event through a source (e.g. a Stripe checkout.session.completed) — a REAL event in the REAL lane, useful to verify a fix end-to-end. Requires a read+write token. |
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 4 tools
Each tool occupies a distinct stage of the webhook debugging workflow: list_failed discovers problems, get_payload inspects a specific event, replay redelivers one, and send_test generates a new test event. There is no overlap — an agent can unambiguously pick the right tool for each intent.
All names use lowercase snake_case, and three follow a verb_noun pattern (list_failed, get_payload, send_test). 'replay' is a bare verb with no noun, a minor deviation, but the style remains readable and predictable overall.
Four tools is reasonable for a focused webhook troubleshooting server, and each one clearly earns its place in the detect-inspect-fix-verify loop. It sits at the lean end of the ideal 3-15 range, but not awkwardly so.
The surface covers a full debugging lifecycle (list failures, inspect payload, replay, send a verification test), which is coherent and complete for the stated purpose. Minor gaps exist — no tool to list successful/all events or search/filter beyond failed deliveries — though the dashboard inbox mentioned in descriptions partly offsets this.