Hookdeck MCP Server for VS Code CopilotGive VS Code Copilot instant access to 52 tools to Cancel Event, Count Connections, Count Sources, and more

Name: Hookdeck
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The Hookdeck MCP Server for VS Code Copilot is a standout in the Developer Tools category — giving your AI agent 52 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

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

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Hookdeck and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

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.

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.

The Hookdeck MCP Server exposes 52 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 52 Hookdeck tools available for VS Code Copilot

When VS Code Copilot connects to Hookdeck through Vinkius, your AI agent gets direct access to every tool listed below — spanning webhooks, event-driven, api-integration, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

cancel

Cancel event on Hookdeck

Cancel scheduled retries for an event

count

Count connections on Hookdeck

Count total connections

count

Count sources on Hookdeck

Count total sources

create

Create bookmark on Hookdeck

Create a new bookmark

create

Create connection on Hookdeck

Create a connection

create

Create destination on Hookdeck

Create a new destination

create

Create issue trigger on Hookdeck

Create a new issue trigger

create

Create source on Hookdeck

Create a new source

create

Create transformation on Hookdeck

Create a new transformation

delete

Delete bookmark on Hookdeck

Remove a bookmark

delete

Delete connection on Hookdeck

Permanently delete a connection

delete

Delete destination on Hookdeck

Delete a destination

delete

Delete issue trigger on Hookdeck

Delete an issue trigger

delete

Delete source on Hookdeck

Delete a source

disable

Disable connection on Hookdeck

Disable a connection

disable

Disable source on Hookdeck

Disable a source

enable

Enable connection on Hookdeck

Enable a disabled connection

enable

Enable source on Hookdeck

Enable a source

get

Get attempt on Hookdeck

Retrieve a specific attempt

get

Get connection on Hookdeck

Retrieve a specific connection

get

Get destination on Hookdeck

Retrieve a specific destination

get

Get event on Hookdeck

Retrieve a specific event

get

Get issue trigger on Hookdeck

Retrieve a specific issue trigger

get

Get metrics attempts on Hookdeck

Delivery attempt metrics

get

Get metrics events on Hookdeck

Event processing statistics

get

Get metrics queue depth on Hookdeck

Current queue depth per destination

get

Get metrics requests on Hookdeck

Request volume metrics

get

Get metrics transformations on Hookdeck

Transformation execution performance

get

Get request on Hookdeck

Retrieve a specific request

get

Get source on Hookdeck

Retrieve a specific source

get

Get transformation on Hookdeck

Retrieve a specific transformation

list

List attempts on Hookdeck

Retrieve a list of delivery attempts

list

List bookmarks on Hookdeck

Retrieve a list of bookmarks

list

List connections on Hookdeck

Retrieve a list of connections

list

List destinations on Hookdeck

Retrieve a list of destinations

list

List events on Hookdeck

Retrieve a list of events

list

List issue triggers on Hookdeck

Retrieve a list of issue triggers

list

List requests on Hookdeck

Retrieve a list of requests

list

List sources on Hookdeck

Retrieve a list of sources

list

List transformations on Hookdeck

Retrieve a list of transformations

pause

Pause connection on Hookdeck

Pause event routing for a connection

retry

Retry event on Hookdeck

Manually retry a failed event

retry

Retry request on Hookdeck

Retry a rejected request

test

Test transformation on Hookdeck

Test transformation code against a payload

trigger

Trigger bookmark on Hookdeck

Replay the bookmarked request

unpause

Unpause connection on Hookdeck

Resume event routing for a connection

update

Update connection on Hookdeck

Update a connection rules or name

update

Update destination on Hookdeck

Update destination config (URL, rate limit, etc.)

update

Update issue trigger on Hookdeck

Update an issue trigger

update

Update source on Hookdeck

Update a source

update

Update transformation on Hookdeck

Update transformation code

upsert

Upsert connection on Hookdeck

Create or update a connection by name

Connect Hookdeck to VS Code Copilot via MCP

Follow these steps to wire Hookdeck into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Hookdeck

Ask Copilot: "Using Hookdeck, help me...". 52 tools available

Why Use VS Code Copilot with the Hookdeck MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Hookdeck through the Model Context Protocol.

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 + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Hookdeck MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Hookdeck in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Hookdeck immediately.

"List all my current Hookdeck connections."

"Pause the connection with ID conn_456 immediately."

"How many webhook sources do I have?"

Troubleshooting Hookdeck MCP Server with VS Code Copilot

Common issues when connecting Hookdeck to VS Code Copilot through Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Hookdeck + VS Code Copilot FAQ

Common questions about integrating Hookdeck MCP Server with VS Code Copilot.

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.