MCP Webhook Server

The MCP Webhook Server enables you to send data to webhooks via HTTP POST, designed to run on Claude Code with local or remote access for collaboration and automation.

How to use

You can run the local STDIO version on a single machine to trigger webhook deliveries directly from your development environment. For team collaboration, run the HTTP version on a server to expose an MCP endpoint that teammates can reach from anywhere.

How to install

Prerequisites: ensure you have Node.js and npm installed on your system.

cd MCP
npm install
npm run build

Configuration and usage notes

Two primary MCP server configurations are available: a remote HTTP endpoint for team access and a local STDIO setup for single-user development. The HTTP configuration exposes an endpoint at a specific URL and can be started with port customization. The STDIO configuration runs locally by invoking a Node script directly to handle MCP tasks.

# Example: Quick start for HTTP (remote server)
# On your server or VPS:
npm run start:http

# Or with a custom port:
node dist/index.js --http --port 8080

# Or with an environment variable:
PORT=8080 node dist/index.js --http

Example usage patterns

• Start a shared HTTP MCP endpoint so your team can submit events to a unified webhook target.

• Run a local STDIO Brabant-style workflow where your IDE or command line can push events to a configured webhook sender.

Available tools

startHttp

Launch the HTTP MCP server to expose the /mcp endpoint for remote clients.

startStdio

Run the local STDIO MCP server to enable in-process webhook sending from a single machine.

healthCheck

Provide the /health endpoint to verify server readiness.

sendWebhook

Deliver payloads to configured webhook destinations via the MCP sender tool.