Bring Webhooks
to CrewAI
Learn how to connect Hookdeck to CrewAI and start using 52 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 CrewAI?
When paired with CrewAI, Hookdeck becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Hookdeck tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Hookdeck in CrewAI
Hookdeck and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Hookdeck to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Kong (AI API Gateway)
10 toolsManage your API Gateway via Kong — orchestrate services, routes, and AI plugins directly from your agent.
iQiyi Open Platform / 爱奇艺开放平台
8 toolsChina's leading video platform — retrieve user info, VIP status, and search content via AI.
Clearscope
10 toolsOptimize content via Clearscope — create SEO reports, grade drafts using NLP, perform keyword research, and audit SERP competitors directly from any AI agent.
Eurostat Economy — EU Financial Intelligence
6 toolsOfficial EU economic data: quarterly GDP for all 27 member states, government debt and deficit (Maastricht criteria), HICP inflation (the ECB's target measure), interest rates, and EUR exchange rates.