zhook-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZHOOK_API_KEY | Yes | Your Zhook API Key |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trigger_webhookA | Send a test webhook event to a specific Hook. This mimics a real third-party service sending data to the hook URL. |
| list_hooksB | List all webhooks configured in the Zhook account. Returns hook IDs, URLs, and active status. |
| create_hookB | Create a new webhook or MQTT hook. Returns the new hook ID and its public URL. |
| get_hookB | Get detailed configuration for a specific webhook, including delivery URL, metadata, and recent metrics. |
| list_destinationsC | List all destinations configured for a specific webhook. |
| create_destinationC | Add a new destination to a hook to forward events to. |
| get_destinationC | Get detailed configuration for a specific destination. |
| update_destinationC | Update an existing destination's configuration. |
| delete_destinationC | Remove a destination from a hook. |
| list_transformationsB | List all transformations configured for a specific webhook. |
| create_transformationC | Create a new JSONata transformation for a hook. |
| update_transformationC | Update an existing transformation. |
| delete_transformationC | Delete a transformation from a hook. |
| get_hook_metricsC | Get real-time metrics for a specific hook (request counts, success/failure rates). |
| get_aggregated_hook_metricsC | Get historical aggregated metrics for a specific hook with custom date ranges. |
| list_eventsB | List recent events received by a specific hook. Useful for checking what payloads have been delivered. |
| get_eventC | Get the full JSON payload and details of a specific event. |
| wait_for_eventA | Connects to the Zhook WebSocket and waits for the NEXT event to arrive on a specific hook. Returns the full event payload immediately. TIMEOUT is 60 seconds. |
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 18 tools
Every tool has a clearly distinct purpose targeting specific resources (hooks, destinations, transformations, events, metrics) and actions (create, get, list, delete, update, trigger, wait). There is no overlap or ambiguity; for example, get_hook retrieves configuration while get_hook_metrics focuses on real-time metrics, and list_events is separate from get_event.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_destination, list_hooks, and update_transformation. The naming is predictable and uniform across all 18 tools, with no deviations in style or convention.
With 18 tools, the count is slightly high but reasonable for a webhook management server covering hooks, destinations, transformations, events, and metrics. It provides comprehensive coverage without being excessive, though it borders on the upper limit of a well-scoped set.
The tool set offers complete CRUD/lifecycle coverage for the domain: hooks (create, get, list, trigger, wait), destinations (create, get, list, update, delete), transformations (create, get, list, update, delete), events (list, get), and metrics (real-time and aggregated). There are no obvious gaps, and agents can manage the full workflow from setup to monitoring.