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

Q: How do I set up the Hookdeck (Webhook Gateway) MCP server in Cursor?

Create a .cursor/mcp.json file in your project's root directory. Add this server's configuration details to the mcpServers array. The tools will become available in Agent mode automatically for anyone working in that project.

Q: How does using Hookdeck (Webhook Gateway) with Cursor help with writing webhook handler code?

You can ask the agent to fetch a live payload with geteventraw. It then uses that real data to generate accurate types, validation schemas, or even a full handler function, which saves you from guesswork and typos.

Q: How do I debug a failing webhook from my Hookdeck (Webhook Gateway) connection in Cursor?

Tell the agent which webhook failed. It can use tools like getevent and listattempts to pull the exact request, response, and headers. The full context of the failure appears right in your editor, next to your code.

Inject live Hookdeck event data and manage connections without leaving your Cursor editor.

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 Cursor

Create your Vinkius account to connect Hookdeck (Webhook Gateway) to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate Code from Real Payloads

Stop writing code against stale, fake data. Tell the Cursor agent to fetch a real webhook payload using `get_event_raw` for a specific event. It will drop the live JSON directly into your editor. From there, the agent can generate a correct TypeScript interface, a Zod schema for validation, or a complete handler function. This closes the gap between your webhook provider and your actual codebase. It's based on reality, not a guess.

Manage Infrastructure in Your Editor

You're in the middle of coding and realize you need a new webhook route. Don't switch contexts. Just open the agent chat and tell it: "Create a new Hookdeck connection from our GitHub source to this new API endpoint." The agent uses `create_source`, `create_destination`, and `create_connection` to build the pipeline. You can see the commands it runs. If you need to check something, just ask it to `get_connection` or `list_destinations`. Your infrastructure is now just a conversation away.

Debug Webhooks with Your MCP Server

A test that depends on a webhook just failed. You can ask the Cursor agent to investigate the failure directly within your IDE. It'll use `get_event` and `list_attempts` to pull the delivery logs and error messages from Hookdeck. No more jumping between your terminal, your browser, and your editor. The agent presents the findings, and you can even tell it to `retry_request` for a specific failed attempt to see if your fix worked. This keeps your entire debugging loop in one place.

Setup guide

Set up Hookdeck (Webhook Gateway) MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Hookdeck (Webhook Gateway) MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Hookdeck (Webhook Gateway) transactions." If the MCP tools are loaded correctly, Cursor will call the Hookdeck (Webhook Gateway) tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Create a `.cursor/mcp.json` file in your project's root directory. Add this server's configuration details to the `mcpServers` array. The tools will become available in Agent mode automatically for anyone working in that project.

Yes. You can instruct the agent in plain English to set up a new route. It will use the `create_source`, `create_destination`, and `create_connection` tools to provision the new infrastructure and show you the results.

You can ask the agent to fetch a live payload with `get_event_raw`. It then uses that real data to generate accurate types, validation schemas, or even a full handler function, which saves you from guesswork and typos.

Tell the agent which webhook failed. It can use tools like `get_event` and `list_attempts` to pull the exact request, response, and headers. The full context of the failure appears right in your editor, next to your code.

When you invoke a tool, the server accesses only the data needed for that operation, like connection strings, source configurations, or event payloads. Your project's `.cursor/mcp.json` file controls access, so it's scoped to your codebase and not exposed elsewhere.

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