MCP Webhook Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBHOOK_URL | Yes | Your webhook URL endpoint for sending messages |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageC | Send message to webhook endpoint |
| send_jsonC | Send arbitrary JSON object to webhook endpoint |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Both tools send data to a webhook endpoint, but 'send_json' is specific to JSON objects while 'send_message' is for general messages. Some overlap exists as JSON could be sent via 'send_message', but descriptions help differentiate.
Both tools follow a clear verb_noun pattern ('send_json', 'send_message'), making the naming consistent and predictable.
With only 2 tools, the server feels too minimal for typical webhook interactions. Even basic functionality like managing endpoints or checking delivery status is missing, suggesting the scope is too narrow.
The tool surface is severely incomplete for a webhook server. There are no tools for configuration, validation, or testing of webhooks, which are essential for real-world use.