webhooks.cc

Name: webhooks.cc
Author: kroqdotdev

by kroqdotdevversion 1.17.0i★ –iComputer or cloud

Registry nameio.github.kroqdotdev/webhooks-cc

Install

Overview

Description from the maker (original English)

Capture, inspect, send and assert on webhooks and inbound email from your coding agent.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Chat & email
You need to fill in: WHK_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: WHK_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://webhooks.cc/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "webhooks-cc": {
      "command": "npx",
      "args": [
        "-y",
        "@webhooks-cc/mcp"
      ],
      "env": {
        "WHK_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http webhooks-cc https://webhooks.cc/mcp

Or run it on your computer

claude mcp add webhooks-cc --env WHK_API_KEY=your-value -- npx -y @webhooks-cc/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "webhooks-cc": {
      "url": "https://webhooks.cc/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "webhooks-cc": {
      "command": "npx",
      "args": [
        "-y",
        "@webhooks-cc/mcp"
      ],
      "env": {
        "WHK_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "webhooks-cc": {
      "type": "http",
      "url": "https://webhooks.cc/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "webhooks-cc": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@webhooks-cc/mcp"
      ],
      "env": {
        "WHK_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://webhooks.cc/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

WHK_API_KEY secret env
webhooks.cc API key (whcc_...). Without one, the server starts connected to the account the agent was connected to before, or in the keyless agent sandbox.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account kroqdotdev, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

More stars than 0% of the other 1762 servers in this category
Published to the registry more recently than 87% of the other 1762 servers in this category
Basic checks equal to or better than 100% of the other 1762 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is webhooks.cc safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: WHK_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.17.0) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 30 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@webhooks-cc/mcp

MCP server for webhooks.cc. It gives coding agents direct access to webhook testing workflows: create endpoints, send signed test webhooks, inspect captures, compare attempts, verify signatures, and read recent webhook context through MCP resources.

The easiest way in is the remote server at https://webhooks.cc/mcp, for any client that can add a remote MCP server (Claude Code, Cursor, VS Code, Codex, claude.ai, ChatGPT): you approve it once in your browser, with no key and nothing to install. This package is the local server, for sends to a handler on your machine, its prompts and resources, a keyless sandbox, and CI. It works with Claude Code, Cursor, VS Code, Codex, Devin Desktop (formerly Windsurf), and Claude Desktop.

Install

No API key is needed. Without one, the server starts with the full tools for the account a human connected the agent to before, or else in the keyless agent sandbox. It reads:

WHK_API_KEY (optional) for an API key, which always wins over a saved connection
WHK_AGENT_FILE for where the sandbox and the connection are saved (default ~/.config/whk/agent.json, see the agent credential file)
WHK_BASE_URL for a custom API base URL
WHK_WEBHOOK_URL for a custom receiver base URL

Claude Code plugin

The plugin installs the server together with a webhook testing skill that tells Claude when to use it:

/plugin install webhooks-cc --marketplace kroqdotdev/webhooks-cc

For other agents, npx skills add kroqdotdev/webhooks-cc installs the same skill. See Agent skill.

Remote server

https://webhooks.cc/mcp serves the same tools over streamable HTTP, with nothing to install. The client opens webhooks.cc in the browser once; the human signs in and clicks Connect (OAuth 2.1 with PKCE, no code to type), and can disconnect it later under Account, Connected agents.

Claude Code: claude mcp add -s user --transport http webhooks-cc https://webhooks.cc/mcp, then /mcp in Claude Code to sign in
Codex: codex mcp add webhooks-cc --url https://webhooks.cc/mcp (it opens the browser to sign in; if it does not, codex mcp login webhooks-cc)
Cursor (.cursor/mcp.json): { "mcpServers": { "webhooks-cc": { "url": "https://webhooks.cc/mcp" } } }
VS Code (.vscode/mcp.json): { "servers": { "webhooks-cc": { "type": "http", "url": "https://webhooks.cc/mcp" } } }
claude.ai and Claude Desktop: Settings, Connectors, add a custom connector with the URL https://webhooks.cc/mcp
ChatGPT: add it as a custom connector (developer mode)

A client that can send headers may use an API key instead: Authorization: Bearer whcc_.... The remote server has 46 tools: send_to and replay_request are left out and targetUrl is refused, because a hosted server cannot reach your machine, and waits are capped at 50 seconds. It needs an account (no sandbox), and serves tools only, without prompts or resources.

One-click

Cursor: Add to Cursor
VS Code: Add to VS Code

Both links set WHK_API_KEY; to start without a key, use the commands below.

CLI

# Claude Code

claude mcp add -s user --transport stdio webhooks-cc -- npx -y @webhooks-cc/mcp

OpenAI Codex

codex mcp add webhooks-cc -- npx -y @webhooks-cc/mcp

Or let setup write the config

npx @webhooks-cc/mcp setup claude-code npx @webhooks-cc/mcp setup cursor npx @webhooks-cc/mcp setup vscode npx @webhooks-cc/mcp setup codex npx @webhooks-cc/mcp setup devin # Devin Desktop, formerly Windsurf ("windsurf" works too) npx @webhooks-cc/mcp setup claude-desktop

To start with an API key, add -e WHK_API_KEY=whcc_... to the mcp add commands, or --api-key whcc_... to setup.

Manual config

"mcpServers": { "webhooks-cc": { "command": "npx", "args": ["-y", "@webhooks-cc/mcp"], "env": { "WHK_API_KEY": "whcc_..." } } } }

Leave out env to start without a key. Get your API key at webhooks.cc/account/api-keys.

What it exposes

The server exposes 48 tools, 3 prompts, and 3 resource surfaces with an API key, the same 48 tools and the prompts with a saved connection, and 11 sandbox tools otherwise. The remote server exposes 46 tools.

Endpoint tools

create_endpoint
list_endpoints
get_endpoint
favorite_endpoint (mark or unmark one of your favourites; list_endpoints and get_endpoint show favorite)
update_endpoint
preview_response
delete_endpoint
create_endpoints
delete_endpoints

Request tools

list_requests
search_requests
count_requests
get_request
wait_for_request
wait_for_requests
replay_request
compare_requests
generate_payload_schema (TypeScript, Zod, Pydantic, or JSON Schema from captured bodies)
extract_from_request
verify_signature
clear_requests

Email tools

Every endpoint on an account receives email at {slug}@mailhooks.cc (and {slug}+{tag}@mailhooks.cc). These tools read it, with the one-time code and main link already picked out, unless the endpoint's owner turned that off:

list_emails
get_email
wait_for_email
send_test_email
render_email (an email in Postmark, SendGrid, Mailgun or CloudMailin shape, optionally posted to your local inbound handler)

The request tools and resources return emails too (filter with kind), without the raw message or the HTML part and with the text cut at 8,000 characters; get_email returns the HTML.

Forwarding tools

Send captured HTTP requests and emails to up to 10 destinations (your servers, Slack or Discord channels, Zapier or n8n), each with its own kinds, conditions, format (as received, signed JSON, a JSON body you shape with placeholders, or a chat message), throttle, delay and signing secret, retried and logged (owner only):

list_destinations, add_destination, update_destination, remove_destination
preview_destination (dry run: does the filter pass, and the exact request it would send)
configure_forwarding (the primary destination: URL, on/off, kinds, format, your headers, path, retries, order, sent time field)
get_forwarding_secret (returns a destination's whsec_ secret; with rotate: true, replaces it)
test_forwarding (sends one request to a destination and reports the answer)
list_deliveries (the delivery log with its counts, by destination, or every try of one request)
redeliver (one request, to one destination or all, or every failed delivery of an endpoint)

Send and test tools

send_webhook
send_to
preview_webhook
test_webhook_flow

Team tools

list_teams
list_team_members
share_endpoint
unshare_endpoint

Endpoints shared with you already appear in list_endpoints (with fromTeam) and work with every request tool except clear_requests, which stays with the owner. Invites are not exposed: accepting one claims a paid seat.

Discovery and account tools

list_provider_templates
get_usage (personal plan plus each subscribed team's pool)
describe

Without an API key: the agent sandbox

Started without WHK_API_KEY, the server starts with the full tools when the agent credential file holds a live connection to a human's account. Otherwise it registers sandbox tools instead (auth.md):

create_endpoint, list_endpoints, get_endpoint, delete_endpoint, list_requests, get_request, wait_for_request, generate_payload_schema: the same names and arguments as the full tools, in a sandbox of up to 3 endpoints, 25 captured requests each and 100 in all, for 24 hours. The first create_endpoint registers it (a few seconds of proof of work).
connect_account: returns a link and a 6-digit code for a human to connect the agent to their account. Pass the email they sign in to webhooks.cc with.
wait_for_connection: waits for the human, then replaces the sandbox tools with the full tools for that account (notifications/tools/list_changed) and saves the connection.
about_sandbox: the limits and how to connect, without a network call.

The human approves the agent once: later sessions start connected, for 90 days. When they disconnect the agent under Account, Connected agents, the sandbox tools come back. A sandbox made in an earlier session cannot move into the account, because only the process that registered holds the claim token; connect_account then connects through a new registration and says so, and the old endpoints stay in the sandbox until they expire.

The agent credential file

The sandbox and the connection are saved in ~/.config/whk/agent.json ($XDG_CONFIG_HOME/whk/agent.json when set; ~/Library/Application Support/whk/agent.json on macOS; %APPDATA%\whk\agent.json on Windows), or wherever WHK_AGENT_FILE points. The TypeScript, Python and Go SDKs and the whk CLI share it, so a connection made in one works in all of them. It is written atomically with mode 0600, holds identity assertions and short-lived tokens (never the claim token), and an API key always wins over it. The format is described in AI agents and specified in agent-credentials.md.

Prompts

The server exposes MCP prompts for common workflows:

debug_webhook_delivery
setup_provider_testing
compare_webhook_attempts

These prompts do not execute anything on their own. They give the client a structured starting point for multi-step agent work.

Resources

The server exposes MCP resources for recent webhook context:

webhooks://endpoints
webhooks://endpoint/{slug}/recent
webhooks://request/{id}

These are useful when the client supports resource browsing or prompt/resource attachment.

Provider support

Provider template and signing support includes:

stripe
github
shopify
twilio
slack
paddle
linear
sendgrid
clerk
discord
vercel
gitlab
typeform
standard-webhooks
meta
lemonsqueezy
coinbase-commerce
razorpay
cal
intercom
telegram
square
hubspot
mailgun
calendly
mux
sentry
bitbucket
docusign
adyen
paypal
plaid
resend
workos

Signature verification also supports:

all template providers except sendgrid (IP allowlisting) and plaid (JWT/JWK verification requires Plaid API credentials)

Use list_provider_templates to inspect templates, default events, signature headers, and signing requirements from the agent.

Example workflows

Typical agent flows:

Create an ephemeral endpoint, send a provider-signed webhook, and wait for capture
Search retained requests across endpoints with full-text filters
Compare two webhook attempts and extract only the JSON fields you care about
Verify a captured signa

Only the beginning is shown; read the rest in the repo

webhooks.cc

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

@webhooks-cc/mcp

Install

Claude Code plugin

Remote server

One-click

CLI

OpenAI Codex

Or let setup write the config

Manual config

What it exposes

Endpoint tools

Request tools

Email tools

Forwarding tools

Send and test tools

Team tools

Discovery and account tools

Without an API key: the agent sandbox

The agent credential file

Prompts

Resources

Provider support

Example workflows