4,000+ servers built on vurb.ts
Vinkius

Hookdeck MCP Server for CrewAIGive CrewAI instant access to 52 tools to Cancel Event, Count Connections, Count Sources, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Hookdeck through Vinkius, pass the Edge URL in the `mcps` parameter and every Hookdeck tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Hookdeck MCP Server for CrewAI 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

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Hookdeck Specialist",
    goal="Help users interact with Hookdeck effectively",
    backstory=(
        "You are an expert at leveraging Hookdeck tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Hookdeck "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 52 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Hookdeck
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.

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.

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 CrewAI 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 CrewAI

When CrewAI 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 CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 52 tools from Hookdeck

Why Use CrewAI with the Hookdeck MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Hookdeck through the Model Context Protocol.

01

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

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

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

04

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 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Hookdeck MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Hookdeck for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Hookdeck, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Hookdeck tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Hookdeck against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Hookdeck in CrewAI

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

01

"List all my current Hookdeck connections."

02

"Pause the connection with ID conn_456 immediately."

03

"How many webhook sources do I have?"

Troubleshooting Hookdeck MCP Server with CrewAI

Common issues when connecting Hookdeck to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

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.

Hookdeck + CrewAI FAQ

Common questions about integrating Hookdeck MCP Server with CrewAI.

01

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

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

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

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

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.

Explore More MCP Servers

View all →