Bring Bpm
to CrewAI
Learn how to connect Zeev to CrewAI and start using 11 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 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.
How it works
- Get your Zeev domain and API Key from your profile settings.
- Enter your credentials in Vinkius platform.
- Start chatting with your Zeev agent to manage your workflows.
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.
Built-in capabilities (11)
Cancel an active process request
Start a new process request in Zeev
Delegate a task to another user
Finish/Complete a Zeev task
Get current user information
Get details of a process definition
Get details of a specific process request
Get details of a specific Zeev task
List available process definitions
List process requests (instances) in Zeev
List pending tasks in Zeev
Why CrewAI?
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.
- —
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
Zeev in CrewAI
Zeev and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Zeev 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 Zeev in CrewAI
The Zeev 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 11 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
Zeev for CrewAI
Every tool call from CrewAI to the Zeev MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I start any process using the AI agent?
Yes, as long as you have the process ID and the required initial form data.
Is it possible to delegate tasks to specific users?
Yes, you can use the delegate_task tool by providing the Task ID and the target User ID.
Can I see the history of a request?
Yes, the get_request tool provides details including the current status and history of the instance.
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 →
Worktile
10 toolsCollaborative project management and team communication platform — manage tasks, projects, and messages via AI.
Vertex AI Vector Search
6 toolsBring Google's massive vector matching power to your AI agent. Search billions of semantic embeddings and administer Vertex Index endpoints directly in chat.
Google Fonts API
4 toolsManage web fonts — audit families, variants, and categories via AI.
Adobe Customer Journey Analytics (CJA)
6 toolsOmnichannel journey insights — manage data views, connections, and reports via AI.