Compatible with every major AI agent and IDE
What is the Hookdeck MCP Server?
Connect your Hookdeck account to any AI agent to orchestrate your webhook infrastructure through natural conversation. Hookdeck provides the reliability layer for your event-driven architecture, and this server puts that power in your chat interface.
What you can do
- Connection Management — List, create, and update connections that route webhooks from sources to destinations.
- Traffic Control — Instantly pause or resume event routing for specific connections to manage maintenance windows or outages.
- Source Monitoring — Retrieve and count your webhook sources to understand where your incoming data originates.
- Lifecycle Operations — Enable or disable connections and manage their rules via JSON payloads without leaving your workflow.
- Deep Inspection — Fetch specific metadata for any connection or source using unique IDs to debug routing issues.
How it works
- Subscribe to this server
- Enter your Hookdeck API Key
- Start managing your webhook reliability layer from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Backend Engineers — quickly toggle webhook traffic or check connection statuses during deployments.
- DevOps Teams — monitor the health of event-driven pipelines and manage sources programmatically.
- Integration Specialists — verify routing rules and connection counts across different environments.
Built-in capabilities (52)
Cancel scheduled retries for an event
Count total connections
Count total sources
Create a new bookmark
Create a connection
Create a new destination
Create a new issue trigger
Create a new source
Create a new transformation
Remove a bookmark
Permanently delete a connection
Delete a destination
Delete an issue trigger
Delete a source
Disable a connection
Disable a source
Enable a disabled connection
Enable a source
Retrieve a specific attempt
Retrieve a specific connection
Retrieve a specific destination
Retrieve a specific event
Retrieve a specific issue trigger
Delivery attempt metrics
Event processing statistics
Current queue depth per destination
Request volume metrics
Transformation execution performance
Retrieve a specific request
Retrieve a specific source
Retrieve a specific transformation
Retrieve a list of delivery attempts
Retrieve a list of bookmarks
Retrieve a list of connections
Retrieve a list of destinations
Retrieve a list of events
Retrieve a list of issue triggers
Retrieve a list of requests
Retrieve a list of sources
Retrieve a list of transformations
Pause event routing for a connection
Manually retry a failed event
Retry a rejected request
Test transformation code against a payload
Replay the bookmarked request
Resume event routing for a connection
Update a connection rules or name
Update destination config (URL, rate limit, etc.)
Update an issue trigger
Update a source
Update transformation code
Create or update a connection by name
Why VS Code Copilot?
GitHub Copilot Agent mode brings Hookdeck data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 52 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Hookdeck in VS Code Copilot
Hookdeck and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Hookdeck to VS Code Copilot 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 in VS Code Copilot
The Hookdeck 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 52 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot 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 for VS Code Copilot
Every tool call from VS Code Copilot to the Hookdeck MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I temporarily stop webhooks from being delivered to a destination?
You can use the pause_connection tool with the specific Connection ID. This will halt event routing until you call unpause_connection.
Can I see how many active sources I have configured?
Yes, use the count_sources tool to get the total number of sources, or list_sources to see the details of each one.
Is it possible to update connection rules through the AI?
Absolutely. Use the update_connection tool by providing the Connection ID and a JSON body containing the new configuration rules.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Amazon Ads
8 toolsAdvertising management — manage Sponsored Products, brands, and performance reports via AI.

UK Environment Agency
9 toolsPull real-time flood monitoring, sensor readings, and water levels directly from the UK Environment Agency via any AI agent.

SketricGen
18 toolsConnect your AI agents to SketricGen to run multi-agent workflows, manage knowledge bases, debug traces, and interact with contacts.

Airmeet
10 toolsEvent management and orchestration — manage virtual events, attendees, and recordings via AI.
