Compatible with every major AI agent and IDE
What is the Hookdeck (Webhook Gateway) MCP Server?
Connect your Hookdeck account to any AI agent and take full control of your webhook gateway and event-driven architecture through natural conversation.
What you can do
- Connection Management — List, create, and update connections that route events from sources to destinations with specific rules.
- Operational Control — Instantly pause, unpause, enable, or disable connections to handle maintenance or traffic spikes without touching code.
- Source Monitoring — Manage your webhook sources, retrieve their configurations, and monitor the flow of incoming events.
- Infrastructure Auditing — Count active connections and sources to get a high-level overview of your integration health.
- Lifecycle Actions — Delete or update existing infrastructure components as your project requirements evolve.
How it works
- Subscribe to this server
- Enter your Hookdeck API Key
- Start managing your webhook reliability from Claude, Cursor, or any MCP-compatible client
No more jumping between dashboards to pause a failing webhook or check a source configuration. Your AI acts as a dedicated DevOps engineer for your event pipeline.
Who is this for?
- Backend Engineers — quickly debug and manage webhook routes without leaving the terminal or IDE.
- DevOps & SREs — automate the enabling/disabling of connections during deployment windows or incidents.
- Support Engineers — check source configurations and connection statuses to troubleshoot client integration issues.
Built-in capabilities (75)
Bulk cancel events
Bulk retry events based on a query
Bulk retry rejected requests
Cancel an ongoing bulk retry
Cancel a scheduled retry for an event
Count connections
Count destinations
Get issue count
Count sources
Count transformations
Create a bookmark
Can include inline source/destination. Create a connection
Create a destination
Create an issue trigger
Create a source
Create a transformation
Delete a bookmark
Delete a connection
Delete a destination
Dismiss an issue
Delete an issue trigger
Delete a source
Delete a transformation
Disable a connection
Disable a destination
Disable a source
Enable a connection
Enable a destination
Enable a source
Retrieve a specific attempt
Retrieve a bookmark
Get status of a bulk retry
Retrieve a specific connection
Retrieve a destination
Retrieve a specific event
Get event raw body data
Retrieve an issue
Retrieve an issue trigger
Delivery attempt pattern metrics
Event processing and success rate metrics
Failures grouped by issue metrics
Monitor processing backlogs
Request volume and status metrics
Transformation performance metrics
Retrieve a specific request
Retrieve events generated by a request
Retrieve ignored events for a request
Get request raw body data
Retrieve a source
Get a specific transformation execution
Retrieve delivery attempts
Retrieve bookmarks
Retrieve connections
Retrieve destinations
Retrieve events
Retrieve issue triggers
Retrieve issues
Retrieve requests
Retrieve sources
Get transformation executions
Retrieve transformations
Events will be marked as HOLD. Pause a connection
Send events directly to Hookdeck
Retry a specific event
Retry a rejected request
Test a transformation
Replay the bookmarked request
Unpause a connection
Update a bookmark
Update a connection
Update a destination
Update issue status
Update an issue trigger
Update a source
Update a transformation
Why Cursor?
Cursor's Agent mode turns Hookdeck (Webhook Gateway) into an in-editor superpower. Ask Cursor to generate code using live data from Hookdeck (Webhook Gateway) and it fetches, processes, and writes. all in a single agentic loop. 75 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Hookdeck (Webhook Gateway) in Cursor
Hookdeck (Webhook Gateway) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Hookdeck (Webhook Gateway) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Hookdeck (Webhook Gateway) in Cursor
The Hookdeck (Webhook Gateway) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 75 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Hookdeck (Webhook Gateway) for Cursor
Every tool call from Cursor to the Hookdeck (Webhook Gateway) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Telnyx Fax
10 toolsSend, receive, and manage faxes via Telnyx u2014 transmit documents, track delivery, and manage fax numbers from your AI agent.

CoinPaprika API
10 toolsAccess cryptocurrency data — audit coins, markets, and exchanges via AI.

Makeswift
10 toolsBuild stunning Next.js websites with a visual editor that lets marketers update pages without touching code or deployments.

Smsmobile
26 toolsTurn your smartphone into an SMS/WhatsApp gateway — send messages, read incoming texts, and track call logs directly from any AI agent.
