Capture webhooks and email, forward them to localhost, and put the site on your machine at a public link. A hosted service with an open source CLI (whk), SDKs for TypeScript, Python and Go, and an MCP server for AI coding agents.
No account needed to try it: open webhooks.cc for a capture URL, send it a request, and watch it arrive.
If webhooks.cc saves you time, a star on this repository helps other developers find it.
Pick where you work.
In the terminal. Install whk, sign in once, and forward a capture URL to your app, or share the app itself:
curl -fsSL https://webhooks.cc/install.sh | sh # or: brew install kroqdotdev/tap/whk
whk auth login
whk tunnel 3000 # a webhook URL whose requests reach localhost:3000
whk share 3000 # https://<name>.sharehooks.cc, served from localhost:3000In your coding agent. Add the remote MCP server; you approve the connection once in your browser, with no key to paste:
claude mcp add -s user --transport http webhooks-cc https://webhooks.cc/mcpIn your tests. Wait for the webhook or email your code sends, then assert on it:
npm install @webhooks-cc/sdk # TypeScript
pip install pytest-webhooks-cc # pytest fixtures, on the Python SDK
go get webhooks.cc/go # GoIn the browser. Visit webhooks.cc, copy your URL, and send it a request:
curl -X POST https://go.webhooks.cc/w/<slug> -d '{"test": true}'- Capture requests: store incoming webhooks with headers, body, query parameters and metadata
- Capture email: every endpoint receives mail at
{slug}@mailhooks.cc, with parsed fields, attachments and authentication results - Inspect in real time: see requests the moment they arrive
- Configure responses: return custom status codes, headers and bodies, chosen by rules, to test error paths
- Verify signatures: check provider signatures (Stripe, GitHub, Shopify and more) on captured requests
- Forward: tunnel webhooks to localhost during development (with
--live, the sender gets your local app's answer), or forward them to other URLs, chat and file drops - Share localhost: put the site on your machine at a public link on sharehooks.cc with
whk share - CLI for people and agents: manage endpoints, tunnel, stream and wait for requests from your terminal, with JSON output and stable exit codes for scripts and coding agents
- SDKs for TypeScript, Python and Go: wait for and assert on webhooks in tests and CI, and share a local port from code
- pytest plugin:
pip install pytest-webhooks-ccgives every test a capture URL and an email address as fixtures - GitHub Action:
setup-whkinstalls the CLI in a workflow - MCP server: connect AI coding agents (Claude Code, Cursor, VS Code, Codex) to your webhooks
Testing payment integrations: point Stripe's test webhooks at your endpoint. Inspect the payload structure before writing handlers.
Debugging CI/CD hooks: see exactly what GitHub sends when a push, PR, or deployment occurs.
Developing locally: forward production-like webhooks to localhost without exposing your machine to the internet.
Showing work in progress: send a teammate or client a link to the app running on your laptop.
Mocking failure scenarios: configure your endpoint to return 500 errors and test your retry logic.
curl -fsSL https://webhooks.cc/install.sh | sh
# or
brew install kroqdotdev/tap/whk
# without root: any directory you can write to (created when missing)
curl -fsSL https://webhooks.cc/install.sh | WHK_INSTALL_DIR="$HOME/.local/bin" shWith WHK_INSTALL_DIR, put that directory on your PATH (the installer prints the line to add) before running whk.
npm install @webhooks-cc/sdk# Claude Code, remote (sign in once in the browser)
claude mcp add -s user --transport http webhooks-cc https://webhooks.cc/mcp
# Claude Code, local, with an API key
claude mcp add -s user webhooks-cc -e WHK_API_KEY=whcc_... -- npx -y @webhooks-cc/mcp
# Cursor, VS Code, Devin Desktop (formerly Windsurf), Claude Desktop
npx @webhooks-cc/mcp setup cursor --api-key whcc_...See webhooks.cc/installation for all install methods, one-click buttons, and setup guides.
whk tunnel 8080 # Forward webhooks to localhost:8080
whk share 3000 # Share localhost:3000 at https://<name>.sharehooks.cc
whk listen <slug> # Stream incoming requests, one line each
whk wait <slug> --json # Block until the next request arrives, print it, exit
whk create my-endpoint # Create a new endpoint
whk list # List your endpoints
whk replay <request-id> --to :3000 # Replay a captured request
whk api endpoints/<slug>/destinations # Call any API route with your credentialsEvery command takes --json (the API's own answers, NDJSON for streams, failures as {"error": {...}} on stderr) and exits with a stable status that says what went wrong; see whk --help. Nothing waits for input without a terminal: destructive commands need --yes there.
import { WebhooksCC, matchMethod, matchHeader, matchAll } from "@webhooks-cc/sdk";
const client = new WebhooksCC({ apiKey: "whcc_..." });
const endpoint = await client.endpoints.create({ name: "my-webhook" });
console.log(endpoint.url);
// Wait for a matching request with human-readable timeout
const req = await client.requests.waitFor(endpoint.slug, {
timeout: "30s",
match: matchAll(matchMethod("POST"), matchHeader("stripe-signature")),
});
// Replay captured requests to your local server
await client.requests.replay(req.id, "http://localhost:3000/webhooks");The @webhooks-cc/mcp package exposes 57 tools (54 on the remote server) that let AI agents manage endpoints, inspect webhooks, send test payloads, replay requests, and share a local site at a public link through natural language.
You: "Create a webhook endpoint for testing Stripe"
Agent: Created endpoint "stripe-test" at https://go.webhooks.cc/w/abc123
You: "Send a test checkout.session.completed event"
Agent: Sent POST to stripe-test
You: "Replay that to my local server"
Agent: Replayed to http://localhost:3000/webhooks: 200 OK
See packages/mcp/README.md for full setup and tool reference.
The free plan has 50 requests a day and 7 days of history, which is enough for development and testing. Pro ($8/month) and Business ($29/month) raise the limits, and teams share endpoints under a per-seat subscription. See pricing and plans and limits.
webhooks.cc holds other people's webhooks and email, so the code that handles them should be open to inspection. You can read exactly how a request is captured, stored, forwarded and deleted, and check that the service does what it says. The repository is also where security scanning, dependency updates and bug reports happen in the open.
webhooks.cc is built and run by one developer. The hosted service at webhooks.cc is the product; the repository is not a community project.
- Bugs and feature requests are welcome as issues.
- Questions about your account, billing or data go to webhooks.cc/support, never to a public issue.
- Security vulnerabilities are reported privately, see SECURITY.md.
- Pull requests are accepted only from people who have signed the Contributor License Agreement. Open an issue first: most changes are made in-house, and a pull request may be closed or reimplemented. See CONTRIBUTING.md.
This project uses a split license:
- AGPL-3.0: the web app, receiver, email-capture SMTP host, tunnel edge, attachment parser and database schema (
apps/web/,apps/receiver-rs/,apps/mx-rs/,apps/edge-rs/,apps/parser-rs/,supabase/). See LICENSE. - MIT: the CLI and its tunnel protocol crate, the TypeScript, Python and Go SDKs, the pytest plugin, the MCP server, the Zapier and Make apps, and the Claude Code plugin (
apps/cli-rs/,crates/tunnel/,packages/sdk/,packages/sdk-python/,packages/pytest-webhooks-cc/,packages/sdk-go/,packages/mcp/,packages/zapier-app/,packages/make-app/,plugins/). See theLICENSEfile in each directory.
The CLI, SDKs and MCP server are MIT so you can use them freely in your own projects, open or closed.