Hookbase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOOKBASE_ORG_ID | No | Organization ID (only needed if you have multiple orgs) | |
| HOOKBASE_API_KEY | Yes | Your Hookbase API key (starts with whr_) | |
| HOOKBASE_API_URL | No | API URL override (default: https://api.hookbase.app) | https://api.hookbase.app |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hookbase_list_sourcesB | List all webhook sources in the organization. Sources are endpoints that receive incoming webhooks. |
| hookbase_get_sourceB | Get detailed information about a specific webhook source, including its configuration and statistics. |
| hookbase_create_sourceA | Create a new webhook source. Sources receive incoming webhooks and can be connected to destinations via routes. |
| hookbase_update_sourceC | Update an existing webhook source configuration. |
| hookbase_delete_sourceA | Delete a webhook source. This will also delete all associated routes. |
| hookbase_list_destinationsB | List all webhook destinations in the organization. Destinations are endpoints where webhooks are forwarded to. |
| hookbase_get_destinationB | Get detailed information about a specific destination, including authentication configuration. |
| hookbase_create_destinationC | Create a new webhook destination. Destinations are endpoints where webhooks are forwarded after processing. |
| hookbase_update_destinationC | Update an existing destination configuration. |
| hookbase_delete_destinationA | Delete a destination. This will also delete all associated routes. |
| hookbase_test_destinationB | Test connectivity to a destination by sending a test request. Returns response status and timing. |
| hookbase_list_routesB | List all routes in the organization. Routes connect sources to destinations and define how webhooks are processed. |
| hookbase_get_routeB | Get detailed information about a specific route, including filter and transform configuration. |
| hookbase_create_routeB | Create a new route connecting a source to a destination. Optionally add filters to control which webhooks are forwarded. |
| hookbase_update_routeC | Update an existing route configuration. |
| hookbase_delete_routeC | Delete a route. |
| hookbase_list_eventsC | Query webhook events with optional filters. Events represent incoming webhooks received by sources. |
| hookbase_get_eventA | Get detailed information about a specific event, including the full payload and all delivery attempts. |
| hookbase_get_event_debugB | Generate a cURL command to replay an event for debugging purposes. |
| hookbase_list_deliveriesC | Query webhook deliveries with optional filters. Deliveries represent attempts to forward webhooks to destinations. |
| hookbase_get_deliveryB | Get detailed information about a specific delivery, including the response body and error details. |
| hookbase_replay_deliveryA | Retry a failed delivery. This will re-send the original webhook payload to the destination. |
| hookbase_bulk_replayA | Retry multiple failed deliveries at once. Useful for recovering from destination outages. |
| hookbase_list_tunnelsB | List all localhost tunnels in the organization. Tunnels allow forwarding webhooks to local development servers. |
| hookbase_create_tunnelC | Create a new localhost tunnel. The tunnel can be connected using the Hookbase CLI to forward webhooks to your local server. |
| hookbase_get_tunnel_statusB | Check the connection status of a tunnel. Shows whether the tunnel is connected and live statistics. |
| hookbase_delete_tunnelC | Delete a localhost tunnel. |
| hookbase_list_cron_jobsA | List all scheduled cron jobs in the organization. Cron jobs make HTTP requests on a schedule. |
| hookbase_create_cron_jobC | Create a new scheduled cron job that makes HTTP requests on a schedule. |
| hookbase_delete_cron_jobC | Delete a scheduled cron job. |
| hookbase_trigger_cronA | Manually trigger a cron job immediately, regardless of its schedule. |
| hookbase_get_analyticsB | Get dashboard analytics and metrics for the organization, including event counts, delivery success rates, and top sources/destinations. |
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 32 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as create/delete/get/list for sources, destinations, routes, cron jobs, tunnels, events, and deliveries. There is no overlap or ambiguity, with tools like hookbase_replay_delivery and hookbase_bulk_replay serving different but related retry functions.
All tools follow a consistent verb_noun pattern with the prefix 'hookbase_' and snake_case throughout, such as hookbase_create_destination, hookbase_list_events, and hookbase_update_route. This predictability makes it easy to understand and navigate the toolset.
With 32 tools, the count is on the higher side but reasonable for a comprehensive webhook management system covering sources, destinations, routes, cron jobs, tunnels, events, deliveries, and analytics. It feels slightly heavy but each tool serves a distinct function, avoiding bloat.
The toolset provides complete CRUD and lifecycle coverage for all core entities (sources, destinations, routes, cron jobs, tunnels), plus operations for events, deliveries, analytics, debugging, and testing. There are no obvious gaps, enabling agents to handle full workflows from setup to monitoring and troubleshooting.