4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Camunda (BPMN Engine) MCP Server

Bring Bpmn
to CrewAI

Learn how to connect Camunda (BPMN Engine) to CrewAI and start using 25 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Activate JobsAssign User TaskComplete JobComplete User TaskDeploy ResourcesFail JobGet IncidentGet Process Definition XmlGet Process InstanceGet TopologyGet User TaskGet User Task FormGet VariableSearch GroupsSearch IncidentsSearch JobsSearch Process DefinitionsSearch Process InstancesSearch TenantsSearch User TasksSearch UsersSearch VariablesStart Process InstanceThrow Job ErrorUnassign User Task

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Camunda (BPMN Engine)

What is the Camunda (BPMN Engine) MCP Server?

Connect your Camunda engine to any AI agent to automate and monitor complex business workflows through natural language.

What you can do

  • Process Management — Deploy BPMN, DMN, or Form resources and start new process instances with custom variables.
  • Human Task Orchestration — Search for pending user tasks, assign them to specific users, and complete them to move workflows forward.
  • Incident Monitoring — Identify and inspect process incidents and jobs to troubleshoot bottlenecks or failures in real-time.
  • Definition Inspection — Retrieve BPMN XML definitions and search through deployed process definitions to understand workflow logic.
  • Cluster Topology — Monitor the health and topology of your Camunda cluster directly from your conversation.

How it works

  1. Subscribe to this server
  2. Enter your Camunda Base URL and Bearer Token
  3. Start managing your BPMN workflows from Claude, Cursor, or any MCP-compatible client

No more jumping between the Camunda Modeler and Operate dashboard to check task statuses. Your AI acts as a technical process orchestrator.

Who is this for?

  • Process Engineers — instantly check process definitions and deploy updates without leaving the terminal or IDE.
  • Operations Teams — monitor incidents and manage job failures through simple natural language queries.
  • Developers — start process instances and complete user tasks during local development and testing flows.

Built-in capabilities (25)

activate_jobs

Activate (poll) jobs for workers

assign_user_task

Assign a user task to a specific user

complete_job

Complete an activated job

complete_user_task

Complete a user task with variables

deploy_resources

Deploy BPMN, DMN, or Form resources

fail_job

Mark a job as failed (triggers retries or incidents)

get_incident

Get incident details

get_process_definition_xml

Retrieve the BPMN XML of a process definition

get_process_instance

Get details of a specific process instance

get_topology

Get cluster topology and partition status

get_user_task

Get details of a specific user task

get_user_task_form

Retrieve the linked form for a user task

get_variable

Get a specific variable value

search_groups

Search for user groups

search_incidents

Search for process incidents

search_jobs

Search for job instances

search_process_definitions

Search for deployed process definitions

search_process_instances

Search for process instances

search_tenants

Search for tenants (Multi-tenancy)

search_user_tasks

Search for human tasks

search_users

Search for users

search_variables

Search for process or local variables

start_process_instance

Start a new process instance

throw_job_error

Throw a BPMN error from a job

unassign_user_task

Unassign a user task

Why CrewAI?

When paired with CrewAI, Camunda (BPMN Engine) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Camunda (BPMN Engine) 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 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

See it in action

Camunda (BPMN Engine) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Camunda (BPMN Engine) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Camunda (BPMN Engine) 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Camunda (BPMN Engine) in CrewAI

The Camunda (BPMN Engine) 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 25 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.

Camunda (BPMN Engine)
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

The Vinkius Advantage

How Vinkius secures Camunda (BPMN Engine) for CrewAI

Every tool call from CrewAI to the Camunda (BPMN Engine) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I start a process instance with specific input data?

Yes! Use the start_process_instance tool and provide the variables JSON object. The AI will map your data to the process requirements automatically.

02

How do I find all tasks currently assigned to a specific user?

You can use the search_user_tasks tool with a filter like {"assignee": "user-id"}. The agent will return a list of all active human tasks for that person.

03

Is it possible to see why a process instance is stuck?

Yes. Use search_incidents to find errors in the cluster, and then get_incident with the specific key to see the error message and stack trace.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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 →