# Hookdeck (Webhook Gateway) MCP > Hookdeck (Webhook Gateway) provides full control over your event-driven architecture. Manage webhook sources, connections, and destinations directly from any AI client, allowing you to monitor the flow of data and debug failures without touching code or switching dashboards. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** webhooks, event-gateway, api-management, event-delivery, infrastructure ## Description Stop juggling multiple consoles just to manage a single failing webhook. This MCP connects your entire webhooks infrastructure—the sources, connections, and final destinations—to your agent using natural conversation. You can list all existing connections and immediately pause them if traffic spikes or maintenance is needed. Need to debug? Your AI client retrieves raw event bodies or lets you check the performance metrics for request volume and failure grouping. It even handles complex tasks like retrying rejected requests in bulk, keeping your data pipeline running smoothly. If managing webhook reliability feels too complicated for a single dashboard, Vinkius puts all this power into one place. You use your agent to treat it like having an instant DevOps engineer dedicated solely to your event flow. ## Tools ### bulk_cancel_events Bulk cancel events ### bulk_retry_events Bulk retry events based on a query ### bulk_retry_requests Bulk retry rejected requests ### cancel_bulk_retry_events Cancel an ongoing bulk retry ### cancel_event Cancel a scheduled retry for an event ### count_connections Count connections ### count_destinations Count destinations ### count_issues Get issue count ### count_sources Count sources ### count_transformations Count transformations ### create_bookmark Create a bookmark ### create_connection Can include inline source/destination. Create a connection ### create_destination Create a destination ### create_issue_trigger Create an issue trigger ### create_source Create a source ### create_transformation Create a transformation ### delete_bookmark Delete a bookmark ### delete_connection Permanently removes a specific webhook connection from your gateway. ### delete_destination Permanently removes a destination from the webhook network. ### delete_issue Dismiss an issue ### delete_issue_trigger Delete an issue trigger ### delete_source Removes a webhook source entirely from your system. ### delete_transformation Delete a transformation ### disable_connection Stops all events for a connection immediately, marking it as inactive without deletion. ### disable_destination Disable a destination ### disable_source Disable a source ### enable_connection Restores full event flow and activity to a previously disabled connection. ### enable_destination Enable a destination ### enable_source Enable a source ### get_attempt Retrieve a specific attempt ### get_bookmark Retrieve a bookmark ### get_bulk_retry_events Get status of a bulk retry ### get_connection Retrieves the detailed configuration and current status of a specific connection. ### get_destination Retrieves the configuration details for a specific destination. ### get_event_raw Retrieves the unparsed, raw body data for an event payload. ### get_event Retrieves the full data payload for a single event that passed through the gateway. ### get_issue Retrieve an issue ### get_issue_trigger Retrieve an issue trigger ### get_metrics_attempts Delivery attempt pattern metrics ### get_metrics_events_by_issue Failures grouped by issue metrics ### get_metrics_events Gathers metrics showing event processing rates and overall success percentages. ### get_metrics_queue_depth Monitor processing backlogs ### get_metrics_requests Request volume and status metrics ### get_metrics_transformations Transformation performance metrics ### get_request_events Retrieve events generated by a request ### get_request_ignored_events Retrieve ignored events for a request ### get_request_raw Get request raw body data ### get_request Retrieve a specific request ### get_source Gets comprehensive details and configurations for one specific source. ### get_transformation_execution Get a specific transformation execution ### list_attempts Retrieves a list of past delivery attempt records for tracking purposes. ### list_bookmarks Retrieve bookmarks ### list_connections Lists all established connections within your webhook gateway. ### list_destinations Shows all endpoints that receive the processed webhooks (the final destinations). ### list_events Fetches a list of events that have been processed by your system. ### list_issue_triggers Retrieve issue triggers ### list_issues Lists all recorded issues or failures within the webhook pipeline. ### list_requests Retrieve requests ### list_sources Retrieves a list of all connected webhook sources (the origins of the data). ### list_transformation_executions Get transformation executions ### list_transformations Retrieve transformations ### pause_connection Events will be marked as HOLD. Pause a connection ### publish_event Send events directly to Hookdeck ### retry_event Manually attempts to process a specific, failed event again. ### retry_request Retry a rejected request ### test_transformation Test a transformation ### trigger_bookmark Replay the bookmarked request ### unpause_connection Unpause a connection ### update_bookmark Update a bookmark ### update_connection Modifies settings for an existing connection, like changing its rules or parameters. ### update_destination Makes changes to an existing destination, like updating its required format or endpoint. ### update_issue Update issue status ### update_issue_trigger Update an issue trigger ### update_source Modifies settings on a source, such as changing its credentials or endpoint URL. ### update_transformation Update a transformation ## Prompt Examples **Prompt:** ``` List all my current Hookdeck connections and their status. ``` **Response:** ``` I've retrieved your connections. You have 3 active connections: 'Shopify-Sync' (Enabled), 'Stripe-Webhooks' (Paused), and 'Auth0-Events' (Enabled). Would you like more details on any of these? ``` **Prompt:** ``` Disable the source with ID 'src_123abc'. ``` **Response:** ``` I have successfully disabled the source 'src_123abc'. It will no longer accept incoming webhook events until re-enabled. ``` **Prompt:** ``` Show me the details for connection 'conn_xyz789'. ``` **Response:** ``` Fetching details for 'conn_xyz789'... This connection routes from Source 'GitHub-Repo' to Destination 'Vercel-Deploy'. It currently has 2 active rules and is in 'Enabled' status. ``` ## Capabilities ### Audit and Monitor Event Flow Get counts for sources, connections, destinations, and transformations, providing a quick health check of the entire webhook setup. ### Control Connection Status Enable or disable any connection instantly, or pause it to mark events as held without deleting the configuration. ### Manage Data Components Create, update, and delete core infrastructure elements like sources, destinations, connections, and transformations. ### Debug and Retry Events Retrieve specific events or request raw body data. You can also trigger bulk retries for both rejected requests and failed event batches. ### Track Infrastructure Changes View historical records, including delivery attempt patterns and metrics on processing backlogs to understand system performance over time. ## Use Cases ### Debugging a payment webhook failure A user reports a failed payment event. Instead of manually digging through logs, the agent calls get_event and get_event_raw to pull the exact payload and show why the destination rejected it. They then use retry_event to resend the data. ### Preparing for a scheduled outage The SRE team needs to update an endpoint. Before they touch anything, the agent runs list_connections and uses disable_connection on all related webhooks. This prevents any unexpected events from hitting the outdated system. ### Analyzing systemic performance degradation A product manager notices a spike in errors. The agent calls get_metrics_failures_by_issue, which immediately groups failures by issue type, telling them exactly where the data pipeline is breaking down. ### Onboarding a new third-party integration The backend engineer needs to add a new webhook source. They use list_sources to check for conflicts and then run create_source, ensuring the new origin is correctly set up before linking it to any connections. ## Benefits - Debug failures instantly. Instead of manually checking logs, you ask your agent to retrieve the raw body data for a failed event or request, giving you immediate context. - Manage status without code changes. You don't need to write scripts to pause an entire connection during maintenance; just tell your AI client to 'disable the connection.' - Handle backlogs efficiently. Use tools like bulk_retry_events and list_attempts to recover large batches of failed events, minimizing data loss in one command. - Gain full visibility into performance. Check metrics like get_metrics_queue_depth or count active connections to understand your system's health at a glance. - Simplify component management. You can create new sources or destinations and link them together by running commands that manage the entire lifecycle, from creation (create_source) to deletion (delete_source). ## How It Works The bottom line is that instead of navigating complex web UIs, you talk directly to your webhook infrastructure and get results. 1. Subscribe to this MCP and enter your Hookdeck API Key. 2. Your AI client accesses the connection controls via conversation, allowing you to list sources or destinations. 3. You instruct your agent to perform an action—like disabling a source or retrieving event metrics—and the system executes it immediately. ## Frequently Asked Questions **How do I check if a webhook connection is active using Hookdeck (Webhook Gateway) MCP?** You use list_connections to see all connections. The status column tells you if it's currently enabled or paused, giving you immediate operational visibility. **Can I fix a failed webhook event with the Hookdeck (Webhook Gateway) MCP?** Yes, you can. After retrieving an event using get_event, you run retry_event to manually reprocess it through the gateway without any code changes. **What if I need to stop a connection temporarily for maintenance? Do I delete it?** No, don't delete it. Use disable_connection; this stops events immediately but keeps all your rules and configurations intact, ready to be re-enabled later. **Does the Hookdeck (Webhook Gateway) MCP help with billing or usage metrics?** The MCP provides detailed operational data. You can use get_metrics_events to see success rates and process volume, which helps you track usage patterns for optimization. **How do I update a source's API key using Hookdeck (Webhook Gateway) MCP?** You retrieve the current details with get_source first. Then, you use the update_source tool to apply the new credentials or configuration parameters.