How to Use the Hookdeck (Webhook Gateway) MCP in Claude

Q: Can Claude Desktop automatically retry failed webhooks from Hookdeck (Webhook Gateway)?

Not automatically. Your agent can find failed events using listevents and then suggest running retryevent or bulkretryevents, but it will always require your confirmation to execute the action.

Q: My webhook is stuck. How do I use Claude to fix my Hookdeck (Webhook Gateway) connection?

First, ask Claude to getmetricsqueuedepth to confirm there's a backlog. Then use listevents to find the stuck items. From there, you can either retryevent or, if the destination is down, pauseconnection to stop more events from piling up.

Manage your entire Hookdeck webhook setup right from your Claude Desktop chat.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Hookdeck (Webhook Gateway) MCP to Claude Desktop

Create your Vinkius account to connect Hookdeck (Webhook Gateway) to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Hookdeck (Webhook Gateway) with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

See What Your Webhooks Are Doing

Webhooks fail. It's a fact. Instead of digging through logs, just ask Claude what's going on. It can run `get_metrics_events` to show you success rates or `get_metrics_queue_depth` to see if a destination is falling behind. You can get specific. Ask it to `list_issues` for a project, then drill down into one with `get_issue`. This isn't a static dashboard; it's a conversation with your infrastructure. Your agent gets you the data you need, when you need it.

Fix Broken Deliveries from Chat

When an event fails to deliver, you don't have to go to the Hookdeck UI. Tell Claude to find the problem. It can use `list_events` with a query to find exactly what failed. Once you've found the broken event, just tell your agent to `retry_event`. Or, if a whole batch of events got stuck, you can authorize a `bulk_retry_events` command. You're in control, but the manual work is gone.

Configure Routes with Plain English

Setting up new webhook routing is tedious. With this MCP Server, you just describe what you need. "Create a new webhook source for Stripe, and send it to my staging endpoint." Claude translates that into the right API calls. It'll run `create_source`, `create_destination`, and `create_connection` for you. You can even pass the full configuration in a single `create_connection` call. It confirms the details, you approve, and the connection is live.

Setup guide

Set up Hookdeck (Webhook Gateway) MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Hookdeck (Webhook Gateway) MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Hookdeck (Webhook Gateway) MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under hookdeck-webhook-gateway-mcp.

json

{
  "mcpServers": {
    "hookdeck-webhook-gateway-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Hookdeck (Webhook Gateway) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Hookdeck (Webhook Gateway) MCP in Claude Desktop

Go to Settings -> Developer -> Edit Config to open the config file. Add this server's details under the `mcpServers` key, then restart the app. Your tools will show up next to the chat input.

Claude Desktop runs the MCP server as a local process on your machine. This means it can connect to services on your local network, like a dev server running on localhost, which the web version can't do.

Not automatically. Your agent can find failed events using `list_events` and then suggest running `retry_event` or `bulk_retry_events`, but it will always require your confirmation to execute the action.

First, ask Claude to `get_metrics_queue_depth` to confirm there's a backlog. Then use `list_events` to find the stuck items. From there, you can either `retry_event` or, if the destination is down, `pause_connection` to stop more events from piling up.

The server only accesses data when you explicitly tell your agent to run a tool. It handles Hookdeck connection settings, source and destination URLs, and can fetch webhook event bodies and metadata using tools like `get_event_raw`. Since it runs locally, none of this data leaves your machine unless a tool's purpose is to send it.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript