Webhook

Sends webhook notifications to a configured URL when invoked, enabling external task updates.

javascript

1

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months 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": {
    "noobnooc-webhook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "webhook-mcp"
      ],
      "env": {
        "WEBHOOK_URL": "YOUR_WEBHOOK_URL_HERE"
      }
    }
  }
}

You run a Webhook MCP Server that sends webhook notifications to a configured URL whenever it is invoked. This lets you alert external services (like Echobell or other webhook receivers) when long-running tasks finish, making it easy to automate follow‑ups and updates in your workflow.

How to use

Configure the server in your preferred client to point at your webhook URL. When you prompt your AI assistant to send a notification, the MCP server will post to the URL you provide with an optional message and an external link. This enables you to receive real-time updates on task progress or completion without leaving your current workflow.

How to install

Prerequisites you should have installed before starting:

Install the Webhook MCP Server runtime using the following command to enable Claude Desktop auto‑installation via Smithery:

npx -y @smithery/cli install @noobnooc/webhook-mcp --client claude

Configuration and usage notes

You configure the MCP server by specifying the environment variable WEBHOOK_URL. This URL is where webhook notifications will be sent. You can also pass optional parameters to customize the payload.

Security and maintenance

Keep WEBHOOK_URL private and only share the endpoint with trusted automation. Rotate the webhook URL if you suspect it has been exposed. Regularly update the MCP server to incorporate security fixes and feature enhancements.

Examples and troubleshooting

If you encounter connection issues, verify that WEBHOOK_URL is reachable from your execution environment and that any network policies or firewalls allow outbound requests to that URL. Check that the payload size and rate limits conform to your webhook receiver’s expectations.

Available tools

notifyWebhook

Sends a payload to the configured WEBHOOK_URL when invoked, optionally including a custom message and an external URL.