Hookdeck (Webhook Gateway) MCP. Control and debug every event flow via conversation.
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.
Give Claude and any AI agent real-world access
Get counts for sources, connections, destinations, and transformations, providing a quick health check of the entire webhook setup.
Enable or disable any connection instantly, or pause it to mark events as held without deleting the configuration.
Create, update, and delete core infrastructure elements like sources, destinations, connections, and transformations.
Retrieve specific events or request raw body data. You can also trigger bulk retries for both rejected requests and failed event batches.
View historical records, including delivery attempt patterns and metrics on processing backlogs to understand system performance over time.
Ask an AI about this
Waiting for input…
What AI agents can do with Hookdeck (Webhook Gateway) 30 Tools
These tools let you list, create, update, delete, and monitor every single piece of infrastructure that handles your webhooks.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Hookdeck (Webhook Gateway) MCPBulk 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...
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
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Hookdeck (Webhook Gateway), then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Hookdeck. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The webhooks are your company's nervous system, and managing them feels like a constant chore.
Today, keeping your data pipelines running means jumping between three or four different dashboards. You check the source status on one tab, verify the connection rules on another, then finally go to a third dashboard just to see if events actually hit the destination. If something breaks, you're manually copying IDs and pasting them into separate troubleshooting forms.
With this MCP, all that complexity collapses into conversation. You tell your agent, 'The Stripe feed is failing,' and it instantly pulls up the source configuration, checks the connection status, retrieves the raw event body, and tells you exactly which component broke—all without leaving your terminal.
Mastering Event Control with Hookdeck (Webhook Gateway) MCP
The specific manual steps that disappear include checking connection status via list_connections, manually enabling a source with enable_source, and then needing to check metrics separately using get_metrics_events. All these actions become single commands.
Now you treat your entire event architecture like code: you audit it, you modify it, and you debug it—all from one place. You finally have full, conversational control over the flow of data.
What Hookdeck (Webhook Gateway) MCP does for your AI
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.
019e38a8-c3e2-71cc-875f-e1edba49662d How to set up Hookdeck (Webhook Gateway) MCP
The bottom line is that instead of navigating complex web UIs, you talk directly to your webhook infrastructure and get results.
Subscribe to this MCP and enter your Hookdeck API Key.
Your AI client accesses the connection controls via conversation, allowing you to list sources or destinations.
You instruct your agent to perform an action—like disabling a source or retrieving event metrics—and the system executes it immediately.
Who uses Hookdeck (Webhook Gateway) MCP
This MCP serves backend engineers who need to debug failing event routes fast. It's perfect for DevOps teams needing automated control during deployments, or support staff troubleshooting client integrations under pressure.
You use this MCP to quickly check connection status and retrieve raw data bodies when a webhook fails in production.
Your job is automating failover. You use the controls here to pause or unpause entire connections during planned maintenance windows.
When a client reports an issue, you check source configurations and connection statuses to isolate whether the problem is upstream or internal.
Benefits of connecting Hookdeck (Webhook Gateway) MCP
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).
Hookdeck (Webhook Gateway) MCP 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.
Hookdeck (Webhook Gateway) MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Using generic logging tools
Searching through a general log management system for 'webhook error' results in thousands of lines, making it impossible to isolate the specific failing payload or connection ID.
Use your MCP to run get_event and get_source. This gives you direct access to the exact data payload and source configuration that failed, skipping hours of log sifting.
Manual dashboard switching
To pause a connection, an engineer must jump from the main connections tab to the settings panel, click 'pause,' then switch back to verify the status. This process is slow and error-prone.
Keep everything in your IDE or terminal. Simply instruct your agent: 'Pause the Shopify-Sync connection.' The MCP handles the state change instantly.
Ignoring data history
A system fails and is fixed, but you don't know how many events were lost in the gap. You only see the current status, not the backlog.
Always check list_attempts or get_metrics_queue_depth after an outage. This confirms if there was a processing backlog that needs to be addressed using bulk_retry_events.
When to use Hookdeck (Webhook Gateway) MCP
Use this MCP if your problem is managing the flow, status, and failure recovery of asynchronous webhook events. You need programmatic control over every component: sources, connections, transformations, and destinations. Don't use it if you only want to view general application logs; that requires a dedicated logging tool. If you just need to move data from Point A to Point B without complex monitoring or retry logic, a simple integration connector might suffice. However, if your business depends on reliability—meaning knowing why an event failed and having the ability to programmatically retry it—this MCP is essential. It lets you manage the entire lifecycle, from listing sources (list_sources) to executing bulk retries (bulk_retry_events).
Frequently asked questions about Hookdeck (Webhook Gateway) MCP
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.