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 LlamaIndex?
LlamaIndex agents combine Hookdeck tool responses with indexed documents for comprehensive, grounded answers. Connect 52 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Hookdeck tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Hookdeck tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Hookdeck, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Hookdeck tools were called, what data was returned, and how it influenced the final answer
Hookdeck in LlamaIndex
Hookdeck and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Hookdeck to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Hookdeck tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
Tripleseat
8 toolsManage event bookings, leads, contacts, venues, and accounts for your Tripleseat event management platform through natural conversation.

Transport for London
11 toolsGet live tube status, bus arrivals, journey planning, road disruptions and bike point data across London.

Open-Meteo Weather Forecast
4 toolsGive your AI agent live weather intelligence: 16-day forecasts, current conditions, and hourly breakdowns for any GPS coordinate on Earth — zero API keys required.

Lemon Squeezy
11 toolsManage e-commerce stores, products, orders, and subscriptions via the Lemon Squeezy API.
