SkillAgentSearch skills...

webhooks-cc

Webhook and email testing: capture, inspect, forward and replay. Open source.

Install / Use

claude mcp add kroqdotdev -- npx -y github:kroqdotdev/webhooks-cc

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

71/100

Supported Platforms

Claude Code
Claude Desktop
Cursor

Our assessment of webhooks-cc

webhooks-cc scores 71/100 on our quality scale, 376th of 394 Communication skills we index.

Its MCP Server is 6.9 KB long, well organised into 19 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
29/30
Structure
20/20
Description
12/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so webhooks-cc is actively maintained.
  • It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
  • Its trust signals score 87/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

webhooks-cc compared with similar skills

All 4 of these similar skills score higher than webhooks-cc; compare them before choosing.

SkillScoreStarsUpdatedFormat
webhooks-cc (this skill)by kroqdotdev713todayMCP Server
Agent-Reachby Panniantong100110.4k1d agoCLAUDE.md
rufloby ruvnet10081.3ktodayCLAUDE.md
headroomby headroomlabs-ai10079.2k1d agoCLAUDE.md
CowAgentby zhayujie10047.8ktodayCLAUDE.md

Frequently asked questions

How do I install webhooks-cc?
Run claude mcp add kroqdotdev -- npx -y github:kroqdotdev/webhooks-cc. The install tabs above show the steps for each supported agent.
Which AI agents does webhooks-cc work with?
It is written for Claude Code, Claude Desktop and Cursor, as a MCP Server file. Other agents that read the same format can often use it too.
Is webhooks-cc safe to use?
It is AGPL-3.0-licensed and scores 87/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is webhooks-cc still maintained?
The repository was last updated today, so webhooks-cc is actively maintained.

webhooks.cc

Inspect and debug webhooks and email without deploying to production.

Get a unique URL, point your webhook there, and see every request in real time. No signup required. Every endpoint also has an email address at mailhooks.cc that captures mail the same way.

Try it now →

Getting Started

  1. Visit webhooks.cc
  2. Copy your unique webhook URL
  3. Send a test request: curl -X POST https://go.webhooks.cc/w/<slug> -d '{"test": true}'
  4. Watch it appear in the dashboard

Features

  • 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, or forward them to other URLs, chat and file drops
  • CLI with interactive TUI: manage endpoints, tunnel and stream requests from your terminal
  • SDKs for TypeScript, Python and Go: wait for and assert on webhooks in tests and CI
  • MCP server: connect AI coding agents (Claude Code, Cursor, VS Code, Codex) to your webhooks

Use Cases

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.

Mocking failure scenarios: configure your endpoint to return 500 errors and test your retry logic.

Pricing

Free: 50 requests a day, 7-day retention. Enough for development and testing.

Pro ($8/month): 100,000 requests a month, 31-day retention.

Business ($29/month): 250,000 requests a month, 90-day retention, attachment parsing, custom inbound domains and file drops.

Teams share endpoints under a per-seat subscription. See plans and limits for details.

Install

CLI

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" sh

With WHK_INSTALL_DIR, put that directory on your PATH (the installer prints the line to add) before running whk.

Then launch interactive terminal:

whk

SDK

npm install @webhooks-cc/sdk

MCP server

# Claude Code
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.

CLI

Run whk to launch the interactive TUI:

$ whk

  webhooks.cc

  ● Logged in as you@example.com

  ▸ Tunnel    Forward webhooks to localhost
    Listen    Stream incoming requests
    Create    Create a new endpoint
    Endpoints Manage your endpoints
    Auth      Login / logout
    Update    Check for updates

All commands also work directly from the command line:

whk tunnel 8080                       # Forward webhooks to localhost:8080
whk listen <slug>                     # Stream incoming requests
whk create my-endpoint                # Create a new endpoint
whk list                              # List your endpoints
whk replay <request-id> --to :3000    # Replay a captured request

Pass --nogui or set WHK_NOGUI=1 to skip the TUI and print help.

SDK

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");

MCP server

The @webhooks-cc/mcp package exposes 48 tools that let AI agents manage endpoints, inspect webhooks, send test payloads, and replay requests 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.

Why the code is public

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.

Issues and contributions

  • 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.

License

This project uses a split license:

  • AGPL-3.0: the web app, receiver, email-capture SMTP host, attachment parser and database schema (apps/web/, apps/receiver-rs/, apps/mx-rs/, apps/parser-rs/, supabase/). See LICENSE.
  • MIT: the CLI, the TypeScript, Python and Go SDKs, the MCP server, the Zapier and Make apps, and the Claude Code plugin (apps/cli-rs/, packages/sdk/, packages/sdk-python/, packages/sdk-go/, packages/mcp/, packages/zapier-app/, packages/make-app/, plugins/). See the LICENSE file in each directory.

The CLI, SDKs and MCP server are MIT so you can use them freely in your own projects, open or closed.

Related Skills

View on GitHub
GitHub Stars3
CategoryCommunication
Updated10h ago
Forks0

Languages

TypeScript

Trust signals

87/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 low