MCP server de webhooks-cc
Commit 15 nov 2026Permite que los agentes de IA gestionen endpoints de webhooks, inspeccionen solicitudes entrantes, reenvíen payloads y compartan sitios locales mediante lenguaje natural.
También conocido como kroqdotdev/webhooks-cc, @webhooks-cc/mcp
- Stars
- 3
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 15 nov 2026
- Licencia
- AGPL-3.0
¿Qué es webhooks-cc MCP?
Permite que los agentes de IA gestionen endpoints de webhooks, inspeccionen solicitudes entrantes, reenvíen payloads y compartan sitios locales mediante lenguaje natural.
Resumen generado a partir del README del proyecto
Acerca del MCP server de webhooks-cc
Gestionar endpoints de webhooks e inspeccionar solicitudes entrantes mediante lenguaje natural es lo que este MCP server permite a los desarrolladores que utilizan agentes de codificación con IA. Al conectarse a herramientas como Claude Code, Cursor o VS Code, un agente puede crear nuevos endpoints, enviar payloads de prueba y reenviar solicitudes capturadas a un servidor local. Proporciona un puente entre tu asistente de IA y la infraestructura de webhooks.cc, permitiendo la depuración en tiempo real sin tener que navegar manualmente por un dashboard.
Los usuarios configuran el servidor proporcionando una API key a través de la variable de entorno WHK_API_KEY. El servidor expone 57 tools que permiten a un agente gestionar el ciclo de vida completo de un webhook, desde su creación inicial hasta compartir un sitio local mediante un enlace público. Esta configuración es especialmente útil para probar integraciones de pagos o hooks de CI/CD donde necesitas ver exactamente los headers, bodies y firmas de proveedores como Stripe o GitHub.
Qué puedes hacer con él
- 1Probar integraciones de pagosUn agente de IA puede crear un endpoint específico para inspeccionar la estructura del payload de un evento de Stripe.
- 2Depurar flujos de trabajo de CI/CDPuedes pedirle a un agente que monitoree exactamente qué datos envía GitHub durante un despliegue o un pull request.
- 3Simular el manejo de erroresUn agente puede configurar un endpoint para que devuelva códigos de error específicos y así probar cómo tu aplicación gestiona los reintentos.
- 4Reenviar solicitudes al desarrollo localPuedes instruir a una IA para que tome un webhook capturado y lo envíe directamente a tu servidor local para realizar pruebas.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar webhooks-cc MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar webhooks-cc MCP en Claude Code
$ claude mcp add webhooks-cc -- npx -y @webhooks-cc/mcpInstalar webhooks-cc MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"webhooks-cc": {
"command": "npx",
"args": [
"-y",
"@webhooks-cc/mcp"
]
}
}
}Instalar webhooks-cc MCP en VS Code
.vscode/mcp.json
{
"servers": {
"webhooks-cc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@webhooks-cc/mcp"
]
}
}
}Instalar webhooks-cc MCP en VS Code CLI
$ code --add-mcp '{"name":"webhooks-cc","type":"stdio","command":"npx","args":["-y","@webhooks-cc/mcp"]}'Instalar webhooks-cc MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"webhooks-cc": {
"command": "npx",
"args": [
"-y",
"@webhooks-cc/mcp"
]
}
}
}Instalar webhooks-cc MCP en Codex
$ codex mcp add webhooks-cc -- npx -y @webhooks-cc/mcpInstalar webhooks-cc MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.webhooks-cc] command = "npx" args = ["-y", "@webhooks-cc/mcp"]
Instalar webhooks-cc MCP en Gemini CLI
$ gemini mcp add -s user webhooks-cc npx -- -y @webhooks-cc/mcpInstalar webhooks-cc MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"webhooks-cc": {
"command": "npx",
"args": [
"-y",
"@webhooks-cc/mcp"
]
}
}
}Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblekroqdotdev/webhooks-cc is public and reachablegithub.com/kroqdotdev/webhooks-cc ↗Aprobado
- El paquete indica este repositorio como su origen@webhooks-cc/mcp names kroqdotdev/webhooks-cc as sourcenpmjs.com/package/@webhooks-cc/mcp ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo verificado
- Licencia de código abierto (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-14github.com/kroqdotdev/webhooks-cc ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @webhooks-cc/mcpAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubwebhooks.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.
Getting Started
- Visit webhooks.cc
- Copy your unique webhook URL
- Send a test request:
curl -X POST https://go.webhooks.cc/w/<slug> -d '{"test": true}' - 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 (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 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, and share a local port from code
- 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 share 3000 # Share localhost:3000 at https://<name>.sharehooks.cc
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 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.
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, 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 MCP server, the Zapier and Make apps, and the Claude Code plugin (
apps/cli-rs/,crates/tunnel/,packages/sdk/,packages/sdk-python/,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.
Preguntas sobre webhooks-cc MCP
¿Cómo agrego webhooks-cc MCP a Claude Code?
Ejecuta claude mcp add webhooks-cc -- npx -y @webhooks-cc/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego webhooks-cc MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué puede hacer el MCP server?
Permite que los agentes de IA gestionen endpoints, inspeccionen webhooks, envíen payloads de prueba, reenvíen solicitudes y compartan sitios locales mediante lenguaje natural.
¿Puedo probar la recepción de correos electrónicos?
Sí, cada endpoint tiene una dirección de correo correspondiente en mailhooks.cc que captura correos con campos analizados y archivos adjuntos.
