Overview
Features
Webhook notification on MCP invocation
Sends a webhook payload to the configured WEBHOOK_URL every time the MCP server is called, enabling real-time notifications.
Configurable endpoint via WEBHOOK_URL
Uses the WEBHOOK_URL environment variable to specify the destination webhook.
Optional payload customization
Supports optional parameters 'message' and 'url'; 'url' is exposed as externalLink in the payload.
Multiple installation and integration options
Configured via NPM, Docker, or VS Code settings, with examples provided in the README.
Supports Echobell and other webhook services
Designed to work with Echobell or similar services for task-completion notifications.
Who Is This For?
- AI developers:Configure MCP webhook server to notify on task completion via webhook (e.g., Echobell) and integrate with prompt-driven workflows.
- Prompt engineers:Incorporate prompts that request a notification when tasks finish, using the 'send me a notification when it's done' pattern.
- MCP users integrating with Claude Desktop, Cursor, Windsurf:Set up and configure MCP server across different environments (NPM, Docker, VS Code) to receive webhook-based updates.




