Hookdeck MCP. Manage Webhooks and Event Flow via Chat
Hookdeck manages your webhook infrastructure directly through conversation, letting you treat event routing like a chat command. You can list, create, and update connections, sources, and destinations without leaving your agent interface. It gives you deep visibility into every piece of data flowing through your system.
Give Claude and any AI agent real-world access
List and retrieve details for every connection, source, destination, event, and request in your webhook setup.
Pause or resume specific connections, sources, or entire pipelines to control traffic during deployments or outages.
Create, update, and delete core components like connections, destinations, sources, and transformations programmatically.
Get granular metrics on request volume, queue depth, or retrieve the full history of specific events and attempts for debugging.
Manually retry failed requests or events to ensure data integrity after a temporary failure.
Ask an AI about this
Waiting for input…
What AI agents can do with Hookdeck MCP with 52 Tools
Manage every aspect of your webhook infrastructure—from listing all connections to manually retrying failed events—using these specialized tools.
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 MCPCancel Event
Stops scheduled retries for a specific event.
Count Connections
Returns the total number of active connections in your account.
Count Sources
Counts the total number of webhook sources configured.
Create Bookmark
Creates a reusable bookmark for a specific request payload.
Create Connection
Establishes a new connection to route webhooks from one source to another...
Create Destination
Sets up a new endpoint where incoming webhook data will be sent.
Create Issue Trigger
Generates a new trigger that creates issues in an external system.
Create Source
Adds a new source endpoint to the webhook network.
Create Transformation
Builds a new data transformation rule to modify incoming payloads.
Delete Bookmark
Removes an existing request bookmark.
Delete Connection
Permanently deletes a specific connection route.
Delete Destination
Deletes an entire destination endpoint configuration.
Delete Issue Trigger
Removes an issue trigger from the webhook setup.
Delete Source
Permanently removes a source endpoint.
Disable Connection
Deactivates a connection, stopping event routing immediately.
Disable Source
Disables an entire webhook source from sending data.
Enable Connection
Restores normal operation for a previously disabled connection.
Enable Source
Reactivates a previously disabled webhook source.
Get Attempt
Retrieves details about a single, specific delivery attempt.
Get Connection
Fetches all configuration details for a specified connection route.
Get Destination
Retrieves the full configuration and status of a target destination.
Get Event
Gets comprehensive details about a single processed event.
Get Issue Trigger
Retrieves the configuration for a specific issue trigger.
Get Metrics Attempts
Returns delivery attempt metrics, showing success and failure rates over time.
Get Metrics Events
Provides statistics on event processing performance.
Get Metrics Queue Depth
Shows the current number of pending items waiting for each destination to process.
Get Metrics Requests
Delivers metrics on overall request volume and throughput.
Get Metrics Transformations
Presents data on how transformations are performing, including execution time.
Get Request
Retrieves the full payload and metadata for a specific webhook request.
Get Source
Fetches all details about a specific source endpoint configuration.
Get Transformation
Gets the full code and settings for a defined data transformation.
List Attempts
Retrieves a list of past delivery attempts, including status codes.
List Bookmarks
Lists all existing request bookmarks you've saved.
List Connections
Pulls a list of every active connection route by name and status.
List Destinations
Lists all configured destination endpoints.
List Events
Provides a paginated list of recent processed events.
List Issue Triggers
Displays a catalog of all issue triggers in your setup.
List Requests
Lists the most recent webhook requests received by the system.
List Sources
Provides a list of all configured source endpoints.
List Transformations
Lists all defined data transformation rules.
Pause Connection
Stops event routing for a specific connection route immediately.
Retry Event
Forces a manual retry of a single, failed event record.
Retry Request
Attempts to resend data for a rejected or failed request payload.
Test Transformation
Runs specific transformation code against sample data to test its logic.
Trigger Bookmark
Replays a previously saved, bookmarked request payload through the system.
Unpause Connection
Resumes event routing for a connection that was paused.
Update Connection
Modifies an existing connection's rules or name without deleting it.
Update Destination
Updates the configuration details, such as URL or rate limits, for a destination.
Update Issue Trigger
Modifies the settings of an existing issue trigger.
Update Source
Updates configuration details or credentials for a source endpoint.
Update Transformation
Changes the actual code or logic of a data transformation rule.
Upsert Connection
Creates a connection if it doesn't exist, or updates it by name if it does.
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, 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 Pain of Webhook Debugging
Today, when an event fails or a webhook connection breaks, you're trapped in a dashboard. You click into the Connections tab, then drill down to Sources, then check the Metrics panel. If you need to know why it failed last Tuesday, you have to filter by date, scroll through logs, and copy/paste IDs just to hand them off to a teammate.
With this MCP, that multi-step journey vanishes. You simply ask your agent: 'What was the status of the Stripe connection yesterday?' The agent pulls the specific metrics instantly. It's not about reading; it's about asking.
Hookdeck MCP Brings Control to Your Event Pipeline
The manual process of updating rules, toggling traffic, or fixing failures requires jumping between dozens of tabs and managing complex JSON payloads. You spend time figuring out *where* the control button is.
Now you just talk to your agent. Need to reroute data? Say so. Pause it for testing? Tell it. The power isn't in the buttons; it’s in the conversation, giving you operational command over every piece of event infrastructure.
What Hookdeck MCP does for your AI
Running an event-driven application means dealing with webhooks—and webhooks are notoriously fragile. This MCP connects to Hookdeck, giving you total control over your entire webhook pipeline using natural language commands. You can instantly check how many sources feed into your system or pause a connection during maintenance without ever logging into the dashboard.
Need to debug a weird routing issue? Fetch specific metadata for any source or destination using unique IDs. The Vinkius catalog makes this power available, letting you manage complex event reliability right from your chat client. You'll handle everything from listing connections and sources to updating rules or even manually retrying failed events, all through simple conversation.
019e38a8-7df3-73b4-994c-4868da0e6f61 How to set up Hookdeck MCP
The bottom line is: You manage a complex, production-grade data pipeline using only conversation.
Subscribe to this MCP and provide your Hookdeck API Key.
Connect the key in your preferred AI client, giving your agent access to the full webhook control panel.
Tell your agent what you need—for example, 'Show me all connections that are paused' or 'Retry the last failed event for source XYZ'.
Who uses Hookdeck MCP
This MCP targets highly technical roles that spend time debugging API failures and managing critical infrastructure. It’s for the backend engineer who can't afford to be blocked by a simple dashboard click, or the DevOps team member needing to audit event flow during an incident.
They use this MCP to quickly verify connection statuses and toggle webhook traffic when deploying new features.
They monitor the health of event-driven pipelines, checking metrics like request volume or queue depth immediately after a deployment.
They verify complex routing rules and connection counts across staging and production environments to ensure data integrity.
Benefits of connecting Hookdeck MCP
Avoid context switching. Instead of jumping into a web dashboard to check statuses, you just ask your agent for the connection list or current queue depth.
Maintain reliability during deployments. If you need to test an endpoint change, use 'pause_connection' and then 'unpause_connection' directly in conversation, zero clicks required.
Deep debugging access. Need to know why a request failed? Use 'get_request' or 'list_attempts' to pull the exact payload and error details instantly for root cause analysis.
Build resilient pipelines. You can create new components—like running 'create_source' or setting up complex data handling with 'create_transformation'—without writing setup scripts.
Control recovery efforts. If a critical event fails, you don't wait; you call 'retry_event' to force the system to reprocess the data immediately.
Hookdeck MCP use cases
Debugging a Failed Payment Webhook
The payment webhook failed after an update. Instead of logging into Hookdeck and manually sifting through logs, you ask your agent to 'get_metrics_attempts' for the relevant connection ID. The agent instantly shows which attempts failed and if they are retriable using 'list_attempts'.
Pre-Deployment Traffic Control
A team is updating a destination endpoint. Before going live, you use your agent to call 'pause_connection' on the production route. This guarantees no data gets sent while you test, and then you run 'unpause_connection' when it's safe.
Auditing Data Flow Changes
An integration specialist needs to know if a specific source is still active after a merge. They ask your agent to count sources using 'count_sources', then use 'get_source' for the problematic ID, confirming all rules are correct before proceeding.
Replaying Test Data
You manually created a perfect test request bookmark. You tell your agent to 'trigger_bookmark'. This re-runs that exact payload through the entire pipeline—including any transformations—without having to copy/paste the data again.
Hookdeck MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Manual Dashboard Monitoring
Waiting for a support ticket when your app fails, then manually navigating to Hookdeck's dashboard to find failure metrics or connection statuses.
Ask your agent directly: 'Show me the queue depth for my primary destination' (using 'get_metrics_queue_depth') or 'List all connections and their current status' (using 'list_connections').
Blindly Re-enabling Services
A system went down, so an engineer quickly enables everything to see if it works. This often causes more problems because they don't know which specific source or connection needs fixing.
Always isolate the problem first. Use 'list_sources', then use 'disable_source' on all but one test source. Once isolated, you can precisely call 'enable_source' only when ready.
Confusing Statuses
Seeing a connection is marked as 'active' in the UI, but data still isn't flowing because a dependency was missed.
Don't trust the status alone. Use your agent to call 'get_connection' and compare its retrieved rules against what you expect. If needed, use 'update_connection' before enabling it.
When to use Hookdeck MCP
Use this MCP if your core workflow involves complex data routing, event processing, or API integrations that require constant monitoring and manual intervention. You need to control the flow of data—pausing it for maintenance, checking its status, or replaying failures. It's essential when debugging unreliable systems where the failure point is hard to trace.
Don't use this if you only need static CRUD operations (like creating a simple record in a database) or if your 'messaging' requirement is just sending a simple text notification; those are better handled by dedicated messaging tools. If all you need is basic logging, the monitoring metrics are helpful, but for full operational control, this MCP is required.
Frequently asked questions about Hookdeck MCP
How do I list all active connections using the Hookdeck MCP? +
You ask your agent to use 'list_connections'. It will retrieve a clean, formatted list showing the name and current status of every connection route you have set up.
Can I test my data transformations with the Hookdeck MCP? +
Yes. You call 'test_transformation', giving it sample input data. The agent runs your code against that payload and reports back exactly what the output will look like, confirming its logic before deployment.
What is the difference between listing sources and listing connections with Hookdeck MCP? +
Listing sources shows you where data originates (the input). Listing connections shows you how that data moves from one source to a specific destination (the route).
If I need to fix a failed webhook, should I use 'retry_event' or 'retry_request' via the Hookdeck MCP? +
Use 'get_metrics_attempts' first. If you are retrying a known, specific failure instance, use 'retry_event'. If it was a general payload rejection, use 'retry_request'.
How many tools does the Hookdeck MCP have? +
The Hookdeck MCP provides access to over 50 specialized functions for managing every aspect of your webhook infrastructure.