Zeev MCP Server for CrewAIGive CrewAI instant access to 11 tools to Cancel Request, Create Request, Delegate Task, and more
Connect your CrewAI agents to Zeev through Vinkius, pass the Edge URL in the `mcps` parameter and every Zeev tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
Ask AI about this MCP Server for CrewAI
The Zeev MCP Server for CrewAI is a standout in the Productivity category — giving your AI agent 11 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
from crewai import Agent, Task, Crew
agent = Agent(
role="Zeev Specialist",
goal="Help users interact with Zeev effectively",
backstory=(
"You are an expert at leveraging Zeev 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 Zeev "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 11 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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 Zeev MCP Server
What you can do
- List and manage your pending tasks in real-time.
- Start new process requests with custom form data.
- Complete tasks and make decisions directly from your AI agent.
- Delegate tasks to other team members and track process history.
Who is it for?
- Process managers looking for automated workflow control.
- Operations teams needing quick task execution.
- Developers integrating BPM into their AI-driven applications.
When paired with CrewAI, Zeev becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Zeev tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
The Zeev MCP Server exposes 11 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 11 Zeev tools available for CrewAI
When CrewAI connects to Zeev through Vinkius, your AI agent gets direct access to every tool listed below — spanning bpm, workflow-automation, process-management, 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 request on Zeev
Cancel an active process request
Create request on Zeev
Start a new process request in Zeev
Delegate task on Zeev
Delegate a task to another user
Finish task on Zeev
Finish/Complete a Zeev task
Get me on Zeev
Get current user information
Get process on Zeev
Get details of a process definition
Get request on Zeev
Get details of a specific process request
Get task on Zeev
Get details of a specific Zeev task
List processes on Zeev
List available process definitions
List requests on Zeev
List process requests (instances) in Zeev
List tasks on Zeev
List pending tasks in Zeev
Connect Zeev to CrewAI via MCP
Follow these steps to wire Zeev into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Install CrewAI
pip install crewaiReplace the token
[YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.comCustomize the agent
role, goal, and backstory to fit your use caseRun the crew
python crew.py. CrewAI auto-discovers 11 tools from ZeevWhy Use CrewAI with the Zeev MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Zeev through the Model Context Protocol.
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 `mcps` parameter 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
Zeev + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Zeev MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Zeev for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Zeev, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Zeev tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Zeev against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Example Prompts for Zeev in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Zeev immediately.
"List my pending tasks in Zeev."
"Finish task 123 with decision 'Approved'."
"Start a new 'Expense Report' process."
Troubleshooting Zeev MCP Server with CrewAI
Common issues when connecting Zeev to CrewAI through Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Zeev + CrewAI FAQ
Common questions about integrating Zeev MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Explore More MCP Servers
View all →
Basis Technologies
10 toolsManage your Basis DSP campaigns, tactics, and ads directly from any AI agent.

Figma Alternative
16 toolsAccess Figma design files, comments, components and images via API — inspect nodes, render exports and track version history from any AI agent.

Gotify
22 toolsSend and receive push notifications via your own Gotify server — manage messages, applications, and clients directly through AI.

Road511
8 toolsAccess real-time US and Canada traffic data via Road511 — track incidents, monitor cameras, check road conditions, and analyze trends from any AI agent.
