# Hookdeck (Webhook Gateway) MCP for AI Agents AI Agent Connect

> Hookdeck (Webhook Gateway) MCP. Manage your entire webhook infrastructure through your AI agent. Monitor connections, route events, and control sources without leaving your IDE or terminal. It gives you a voice-controlled dashboard for your event-driven architecture.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_iSLKZT9oqmhKMCvOFyHo6WnmH3SbRloVhta67nLa/ai-agent-connect
- **Tags:** webhooks, event-gateway, api-management, event-delivery, infrastructure

## Description

Hookdeck (Webhook Gateway) lets you treat your webhook infrastructure like a conversation. Instead of hunting through a dashboard to figure out why a source is failing or manually toggling a connection during a traffic spike, you just tell your agent to do it. You can audit your current setup, see how many connections are active, and get a pulse on your event delivery health instantly. It handles the heavy lifting of managing sources, destinations, and the transformations between them. If an event gets stuck, you can trigger retries or cancel scheduled ones on the fly. It's about taking the friction out of event-driven architecture. When you're building with Vinkius, this Connector acts like a dedicated DevOps engineer sitting in your prompt, keeping your pipeline running smoothly while you focus on shipping code.

## Tools

### bulk_retry_events
Bulk retry events based on a query. Trigger retries for a group of failed events.

### bulk_retry_requests
Bulk retry rejected requests. Force a retry on a batch of rejected requests.

### get_bulk_retry_events
Get status of a bulk retry. Use this to monitor the progress of a large-scale retry operation.

### get_event_raw
Get event raw body data. Use this to see the exact payload received from a source.

### get_issue
Retrieve an issue. Get the details of a specific event that failed or was flagged.

### count_destinations
Count how many destinations you have. This provides a quick overview of your endpoint distribution.

### count_sources
Count your active sources. This helps you track the variety of input streams in your gateway.

### cancel_bulk_retry_events
Cancel an ongoing bulk retry. Stop a large-scale retry operation that is already running.

### cancel_event
Cancel a scheduled retry for a specific event. This helps stop a retry loop from hammering a destination.

### create_bookmark
Create a bookmark for a request. This allows you to replay specific requests later for testing.

### count_connections
Get the total number of connections. Use this to quickly audit your current infrastructure scale.

### count_issues
Get the total issue count. Use this to see how many events are currently failing or stuck.

### count_transformations
Count your transformations. Use this to see how many data mapping rules are currently active.

### create_connection
Create a new connection between a source and a destination. You can also include inline source or destination details.

### create_destination
Create a new destination. This adds a new endpoint where your events will be delivered.

### create_issue_trigger
Create an issue trigger. Use this to define specific conditions that should flag an event as an issue.

### delete_destination
Delete a destination. Remove endpoints that are no longer in use by your application.

### delete_source
Delete a source. Remove the ability for a specific provider to send events to your gateway.

### disable_destination
Disable a destination. Prevent events from reaching a specific endpoint.

### get_attempt
Retrieve a specific attempt. Use this to see the details of a single delivery try.

### get_metrics_events
Get event processing and success rate metrics. This provides a high-level view of your gateway health.

### list_bookmarks
Retrieve bookmarks. Get a list of all bookmarked requests for testing.

### list_issue_triggers
Retrieve issue triggers. See all the rules currently flagging events.

### publish_event
Send events directly to Hookdeck. Use this to push data into your gateway manually.

### create_source
Create a new webhook source. This allows you to start accepting events from a new provider.

### create_transformation
Create a transformation rule. This defines how data should be modified before it reaches the destination.

### delete_bookmark
Delete a bookmark. Use this to clean up old test bookmarks you no longer need.

### delete_connection
Delete a connection. Use this to remove old routes from your infrastructure.

### delete_issue
Dismiss an issue. Use this to clear a specific failure from your monitoring view.

### delete_issue_trigger
Delete an issue trigger. Remove specific rules that flag events as issues.

### delete_transformation
Delete a transformation. Remove specific data mapping rules from your pipeline.

### disable_connection
Disable a connection. This stops traffic flow without deleting the configuration.

### disable_source
Disable a source. Stop a provider from sending data while keeping the source configuration.

### enable_connection
Enable a connection. Restore traffic flow to a previously disabled connection.

### enable_destination
Enable a destination. Allow events to flow to a specific endpoint again.

### enable_source
Enable a source. Turn on a provider to start receiving events.

### get_bookmark
Retrieve a bookmark. Fetch the details of a specific bookmarked request.

### get_connection
Retrieve a specific connection. Use this to see the rules and status of a single route.

### get_destination
Retrieve a destination. Get the configuration details for a specific endpoint.

### get_event
Retrieve a specific event. Fetch the full details of a single event in your pipeline.

### get_issue_trigger
Retrieve an issue trigger. See the logic used to flag specific events as issues.

### get_metrics_attempts
Get delivery attempt pattern metrics. Use this to analyze your success and failure rates.

### get_metrics_events_by_issue
Get failures grouped by issue metrics. Use this to see which specific issues are causing the most friction.

### get_metrics_queue_depth
Monitor processing backlogs. Use this to see if your events are piling up in the queue.

### get_metrics_requests
Get request volume and status metrics. Use this to monitor the overall traffic flow.

### get_metrics_transformations
Get transformation performance metrics. See how your data mappings are performing over time.

### get_request_events
Retrieve events generated by a request. See all events tied to a specific request.

### get_request_ignored_events
Retrieve ignored events for a request. See which events were filtered out.

### get_request_raw
Get request raw body data. View the raw payload of a specific request.

### get_request
Retrieve a specific request. Fetch the full details of a request in your system.

### get_source
Retrieve a source. Get the configuration details for a specific source.

### get_transformation_execution
Get a specific transformation execution. See how a specific rule was applied to a piece of data.

### list_attempts
Retrieve delivery attempts. See a history of tries for your events.

### list_connections
Retrieve connections. See all your active and inactive webhook routes.

### list_destinations
Retrieve destinations. See all the endpoints where you send your data.

### list_events
Retrieve events. Get a list of recent events passing through your gateway.

### list_issues
Retrieve issues. Get a list of all events that have failed or been flagged.

### list_requests
Retrieve requests. See a list of all requests in your system.

### list_sources
Retrieve sources. See all the providers currently connected to your gateway.

### list_transformation_executions
Get transformation executions. See a history of how your data was mapped.

### list_transformations
Retrieve transformations. See all the mapping rules in your pipeline.

### pause_connection
Pause a connection. Mark events as HOLD without disabling the connection.

### retry_event
Retry a specific event. Trigger a manual retry for an event that failed previously.

### retry_request
Retry a rejected request. Force a retry on a request that was initially rejected.

### test_transformation
Test a transformation. Verify that your mapping rules work correctly before deploying them.

### trigger_bookmark
Replay the bookmarked request. Send the data from a bookmark through your pipeline again.

### unpause_connection
Unpause a connection. Resume traffic flow for a connection that was on hold.

### update_bookmark
Update a bookmark. Modify the data of a bookmarked request for a new test.

### update_connection
Update a connection. Change the rules or destinations for an existing route.

### update_destination
Update a destination. Modify the configuration of an existing endpoint.

### update_issue
Update issue status. Change the status of a specific flagged event.

### update_issue_trigger
Update an issue trigger. Modify the logic used to flag specific events.

### update_source
Update a source. Change the configuration of a provider source.

### update_transformation
Update a transformation. Modify an existing data mapping rule.

### bulk_cancel_events
Bulk cancel events. Stop multiple events from retrying at the same time.

## Prompt Examples

**Prompt:** 
```
Check if any of my connections are currently failing.
```

**Response:** 
```
I've analyzed your Hookdeck connections. Here is the current status:

| Connection | Status | Issues |
| :--- | :--- | :--- |
| **Stripe-Webhooks** | Active | 12
| **Shopify-Sync** | Paused | 0
| **Auth0-Events** | Active | 2

Would you like me to trigger a bulk retry for the Stripe issues?
```

**Prompt:** 
```
Pause the Shopify connection for an hour.
```

**Response:** 
```
I've paused the 'Shopify-Sync' connection. Events will be marked as HOLD until you're ready to resume them.
```

**Prompt:** 
```
Show me the raw data for the last event from the GitHub source.
```

**Response:** 
```
Fetching the raw payload for the latest GitHub event...

```json
{
  "id": "evt_12345",
  "repository": "vinkius-mcp-repo",
  "action": "push",
  "payload": {
    "ref": "refs/heads/main",
    "message": "Update documentation"
  }
}
```
```

## Capabilities

### Toggle webhook connections
Pause, unpause, enable, or disable connections to manage traffic flow instantly.

### Audit infrastructure scale
Get counts for active connections, sources, and destinations to monitor your setup.

### Handle large-scale retries
Trigger bulk retries or cancel ongoing retry events using specific queries.

### Manage data transformations
Create, update, and test mapping rules to ensure data reaches its destination correctly.

### Monitor event health
Retrieve raw event bodies and check success rate metrics for your entire pipeline.

## Use Cases

### Emergency traffic throttling
A production webhook is flooding a downstream service. The SRE asks the agent to `pause_connection` for the specific source to give the service breathing room.

### Pre-deployment mapping verification
A developer needs to test a new data mapping. They use `test_transformation` to see if the output matches the requirements before pushing to production.

### Batch recovery after network outage
A batch of events failed due to a temporary network blip. The backend engineer uses `bulk_retry_events` to re-process the entire batch in one command.

### Customer integration troubleshooting
A customer reports a missing update. The support engineer uses `get_event_raw` to see the actual data received and identify if the issue is with the sender or the receiver.

## Benefits

- Stop manual dashboard hopping by using `disable_connection` or `pause_connection` to handle traffic spikes without logging into a UI.
- Audit your infrastructure scale instantly with `count_connections` and `count_sources` to see exactly how many routes are active.
- Verify data integrity before deployment by using `test_transformation` to check your mapping rules against real payloads.
- Handle large-scale failures efficiently with `bulk_retry_events` to recover multiple events at once instead of one by one.
- Debug specific integration issues by fetching `get_event_raw` to see the exact payload received from a source in your pipeline.

## How It Works

The bottom line is you get a voice-controlled dashboard for your webhook gateway.

1. Subscribe to the Hookdeck MCP via the Vinkius catalog.
2. Provide your Hookdeck API Key to your preferred AI client.
3. Manage your webhooks using natural language commands like 'pause the Shopify connection'.

## Frequently Asked Questions

**Can Hookdeck (Webhook Gateway) help me manage high-volume webhooks?**
Yes. It allows you to manage thousands of events and connections via your AI agent, making it much easier to handle high-volume traffic without manual intervention.

**How does the Hookdeck (Webhook Gateway) handle failed events?**
It provides tools to see exactly why an event failed and allows you to trigger bulk retries for entire groups of failed messages instantly.

**Can I use Hookdeck (Webhook Gateway) to test my data mappings?**
Absolutely. You can test transformations to see how your data will be mapped before you push those rules into your production pipeline.

**Is Hookdeck (Webhook Gateway) good for DevOps teams?**
It's ideal for DevOps teams because it lets you automate infrastructure actions like pausing connections or auditing source counts through natural language.

**How does Hookdeck (Webhook Gateway) simplify webhook auditing?**
It gives you a high-level view of your entire infrastructure, letting you count active connections, sources, and destinations with a simple question.

**Can I use Hookdeck (Webhook Gateway) to stop a webhook from sending data temporarily?**
Yes, you can use the pause or disable commands to stop traffic to a specific destination or source without deleting your configuration.

**Can I pause a specific webhook connection if my destination server is undergoing maintenance?**
Yes. Use the `pause_connection` tool with the Connection ID. This will hold incoming events until you use `unpause_connection` to resume delivery.

**How do I see all the active sources currently receiving webhooks?**
Simply ask the agent to run `list_sources`. It will return a list of all configured sources, including their IDs and current status.

**Is it possible to get a quick count of how many connections I have configured?**
Yes, the `count_connections` tool provides the total number of connections in your Hookdeck project instantly.