MCP Webhook Server

mcp webhook

javascript

25

GitHub Stars

javascript

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "kevinwatt-mcp-webhook": {
      "command": "npx",
      "args": [
        "-y",
        "@kevinwatt/mcp-webhook"
      ],
      "env": {
        "WEBHOOK_URL": "your-webhook-url"
      }
    }
  }
}

You can send messages to any webhook endpoint from MCP-compatible AI agents using the MCP Webhook Server. It lets you route content from Claude, Dive, and other MCP-enabled systems to services like Discord, Slack, or custom HTTP endpoints, making notifications, alerts, and automated messaging straightforward.

How to use

You run the MCP Webhook Server as a local process and configure your MCP client to point at it. The server exposes a simple action to send a message to the configured webhook URL. You can optionally customize the displayed username and avatar for each message.

How to install

Prerequisites: you need Node.js installed on your system. You can verify by running node -v and npm -v.

Install the MCP Webhook package globally and run it via npx to keep things lightweight.

npm install -g @kevinwatt/mcp-webhook

Configuration

Configure your MCP client to include a webhook server named webhook with the following details. Replace your-webhook-url with the actual endpoint you want to receive messages.

{
  "mcpServers": {
    "webhook": {
      "command": "npx",
      "args": ["-y", "@kevinwatt/mcp-webhook"],
      "env": {
        "WEBHOOK_URL": "your-webhook-url"
      }
    }
  }
}

Security and best practices

Only point the webhook at trusted endpoints. Keep the WEBHOOK_URL confidential and use environment variables to manage it in your MCP client configuration. The server does not track analytics or collect usage data.

Examples

Basic send to a webhook with default settings to notify on events.

Customize the sender name or avatar when desired by extending the payload in your webhook endpoint.

Troubleshooting

If messages fail to arrive, verify the WEBHOOK_URL is correct and reachable from your running MCP Webhook process. Check network access and any firewall rules that might block outbound HTTP requests.

Available tools

send_message

Send a message to the configured webhook endpoint with optional customization for username and avatar. Returns a success/failure status.