INDIVIDUAL MCP TOOL
replay_request
Sends one captured request to the inbox's forward address again, exactly as it came, and returns what your server answered and how long it took.
LIVE ENDPOINT
https://webhookjar.com/mcp
Connect to this endpoint to inspect the live schema for replay_request and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.webhookjar]
url = "https://webhookjar.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webhookjar": {
"type": "http",
"url": "https://webhookjar.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webhookjar
Remote MCP URL: https://webhookjar.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"webhookjar": {
"url": "https://webhookjar.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webhookjar": {
"type": "http",
"url": "https://webhookjar.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webhookjar",
"transport": "streamable-http",
"url": "https://webhookjar.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
create_inbox— Makes a kept inbox on your account and returns its post_url (give this to the service that sends webhooks) and view_url (for a person to watch it live).list_inboxes— Every open inbox on your account, busiest first, with its post_url, request count and last request time.get_inbox— One inbox: its URLs, counts, what it answers senders with, and its forwarding.wait_for_request— Holds until a request lands in the inbox, then returns it in full (headers, body, provider, event, signature check).list_requests— An inbox's requests, newest first, without bodies: id, time, method, provider, event, a plain headline and the signature result.send_sample— Delivers a real provider webhook into the inbox, with the provider's own headers, body and signature, so you can test a handler with no provider account.get_request— Everything caught, as it came: method, path, query, headers, the raw body (base64 when not text), sender, event, and whether its signature matched the inbox's signing secret (verified, failed, or null with no secret set), with the checks behind it.set_inbox_answer— Changes what the inbox sends back to senders, to test how a provider handles failures: status (200, 201, 202, 204, 400, 401, 403, 404, 409, 410, 422, 429, 500, 502, 503), body as a string, delay (0, 2, 10, 30 seconds), and challenges (answer Slack, Meta and Twitch verification for you).