Webhooks▌
by kevinwatt
Webhooks enable automated notifications and workflow automation software integration by sending customizable messages to
Enables sending customizable messages to external webhook endpoints, facilitating automated notifications and workflow integrations.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / AI agents sending alerts to team chat channels
- / Automated notifications from Claude conversations
- / Integrating AI workflows with external systems
- / Building chatbots that post to multiple platforms
capabilities
- / Send messages to Discord webhooks
- / Post to Slack webhook endpoints
- / Send custom JSON payloads to any webhook URL
- / Set custom usernames and avatars for messages
- / Trigger notifications from AI conversations
- / Integrate with Mattermost and other webhook services
what it does
Sends customizable HTTP POST messages to webhook endpoints like Discord, Slack, or any webhook URL. Enables AI agents to trigger notifications and integrate with external systems.
about
Webhooks is a community-built MCP server published by kevinwatt that provides AI assistants with tools and capabilities via the Model Context Protocol. Webhooks enable automated notifications and workflow automation software integration by sending customizable messages to It is categorized under communication, developer tools.
how to install
You can install Webhooks in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Webhooks is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
🪝 mcp-webhook
<div align="center">A powerful MCP server that enables webhook messaging capabilities for your AI agents
Send messages to any webhook endpoint through Claude, Dive, and other MCP-compatible AI systems. Perfect for notifications, alerts, and automated messaging.
Features • Installation • Tools • Usage • Configuration
</div>✨ Features
<table> <tr> <td width="50%">🌐 Generic Webhook Support
- Works with any webhook endpoint
- Compatible with Discord, Slack, Mattermost
- Custom HTTP POST requests
- JSON payload formatting
🎨 Customization
- Custom display name (username)
- Avatar URL support
- Flexible message content
- Easy integration with any platform
🔌 MCP Integration
- Works with Dive Desktop
- Claude Desktop compatible
- Cursor, VS Code support
- Any MCP-compatible LLM
🛡️ Simple & Secure
- Minimal configuration
- Environment variable support
- No tracking or analytics
- MIT licensed
<a href="https://glama.ai/mcp/servers/ijmd1ia5zg"><img width="380" height="200" src="https://glama.ai/mcp/servers/ijmd1ia5zg/badge" alt="Webhook Server MCP server" /></a>
🚀 Installation
Getting Started
Add the following config to your MCP client:
{
"mcpServers": {
"webhook": {
"command": "npx",
"args": ["-y", "@kevinwatt/mcp-webhook"],
"env": {
"WEBHOOK_URL": "your-webhook-url"
}
}
}
}
MCP Client Configuration
<details open> <summary><strong>Dive</strong></summary>- Open Dive Desktop
- Click "+ Add MCP Server"
- Paste the config provided above
- Click "Save" and you're ready!
Use the Claude Code CLI to add the webhook MCP server (guide):
claude mcp add webhook -- npx @kevinwatt/mcp-webhook
Then set the webhook URL in your environment or config.
</details> <details> <summary><strong>Claude Desktop</strong></summary>Add to your claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"webhook": {
"command": "npx",
"args": ["-y", "@kevinwatt/mcp-webhook"],
"env": {
"WEBHOOK_URL": "your-webhook-url"
}
}
}
}
</details>
<details>
<summary><strong>Cursor</strong></summary>
Go to Cursor Settings -> MCP -> New MCP Server. Use the config provided above.
Install via the VS Code CLI:
code --add-mcp '{"name":"webhook","command":"npx","args":["-y","@kevinwatt/mcp-webhook"],"env":{"WEBHOOK_URL":"your-webhook-url"}}'
Or follow the MCP install guide with the standard config from above.
</details> <details> <summary><strong>Windsurf</strong></summary>Follow the configure MCP guide using the standard config from above.
</details> <details> <summary><strong>Cline</strong></summary>Follow Cline MCP configuration guide and use the config provided above.
</details> <details> <summary><strong>Warp</strong></summary>Go to Settings | AI | Manage MCP Servers -> + Add to add an MCP Server. Use the config provided above.
Go to Settings | Tools | AI Assistant | Model Context Protocol (MCP) -> Add. Use the config provided above.
Installing via Smithery
To install MCP Webhook Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @kevinwatt/mcp-webhook --client claude
Manual Installation
npm install -g @kevinwatt/mcp-webhook
🛠️ Available Tools
<table> <tr> <th width="30%">Tool</th> <th width="70%">Description</th> </tr> <tr> <td><code>send_message</code></td> <td>Send a message to the configured webhook endpoint
- Parameters:
content(string, required): Message content to sendusername(string, optional): Custom display nameavatar_url(string, optional): Custom avatar URL
- Returns: Success/failure status
💡 Usage Examples
Basic Messages
"Send a message to webhook: Hello World!"
"Send 'Build completed successfully' to the webhook"
"Notify the team: Deployment finished"
Custom Username
"Send a message with username 'Deploy Bot': Production update complete"
"Send content='Server restarted', username='System Monitor'"
With Avatar
"Send a message with custom avatar: content='Alert!', avatar_url='https://example.com/alert.png'"
Automation Examples
"Send a webhook message when the build completes"
"Notify via webhook: All tests passed!"
"Send deployment status to the webhook channel"
🔧 Configuration
Environment Variables
| Variable | Description | Required |
|---|---|---|
WEBHOOK_URL | The webhook endpoint URL | Yes |
Example Configurations
Discord Webhook:
{
"env": {
"WEBHOOK_URL": "https://discord.com/api/webhooks/..."
}
}
Slack Incoming Webhook:
{
"env": {
"WEBHOOK_URL": "https://hooks.slack.com/services/..."
}
}
Mattermost Webhook:
{
"env": {
"WEBHOOK_URL": "https://your-mattermost.com/hooks/..."
}
}
🏗️ Architecture
Built With
- MCP SDK - Model Context Protocol
- Axios - HTTP client
- TypeScript - Type safety and developer experience
Key Features
- ✅ Simple: Minimal setup, just provide a webhook URL
- ✅ Flexible: Works with any webhook-compatible service
- ✅ Type-Safe: Full TypeScript support
- ✅ Lightweight: Minimal dependencies
🤝 Contributing
Contributions are welcome!
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
📝 License
This project is licensed under the MIT License - see the LICENSE file for details.
🙏 Acknowledgments
📚 Related Projects
- MCP Servers - Official MCP server implementations
- Dive Desktop - AI agent platform
<div align="center"> </div>
FAQ
- What is the Webhooks MCP server?
- Webhooks is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Webhooks?
- This profile displays 38 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.4 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.4★★★★★38 reviews- ★★★★★Anika Okafor· Dec 24, 2024
Webhooks is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Ganesh Mohane· Dec 8, 2024
We wired Webhooks into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Arjun Park· Dec 4, 2024
Strong directory entry: Webhooks surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Rahul Santra· Nov 27, 2024
Webhooks reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Anika Wang· Nov 15, 2024
We evaluated Webhooks against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Pratham Ware· Oct 18, 2024
Webhooks is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★James Park· Oct 6, 2024
We wired Webhooks into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Piyush G· Sep 25, 2024
According to our notes, Webhooks benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Henry Li· Sep 17, 2024
We wired Webhooks into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Emma Ndlovu· Sep 13, 2024
Webhooks is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 38
