Compatible with every major AI agent and IDE
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
- Subscribe to this server
- Enter your Camunda Base URL and Bearer Token
- 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 (poll) jobs for workers
Assign a user task to a specific user
Complete an activated job
Complete a user task with variables
Deploy BPMN, DMN, or Form resources
Mark a job as failed (triggers retries or incidents)
Get incident details
Retrieve the BPMN XML of a process definition
Get details of a specific process instance
Get cluster topology and partition status
Get details of a specific user task
Retrieve the linked form for a user task
Get a specific variable value
Search for user groups
Search for process incidents
Search for job instances
Search for deployed process definitions
Search for process instances
Search for tenants (Multi-tenancy)
Search for human tasks
Search for users
Search for process or local variables
Start a new process instance
Throw a BPMN error from a job
Unassign a user task
Why VS Code Copilot?
GitHub Copilot Agent mode brings Camunda (BPMN Engine) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 25 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Camunda (BPMN Engine) in VS Code Copilot
Camunda (BPMN Engine) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Camunda (BPMN Engine) to VS Code Copilot 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 Camunda (BPMN Engine) in VS Code Copilot
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 VS Code Copilot 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
Camunda (BPMN Engine) for VS Code Copilot
Every tool call from VS Code Copilot to the Camunda (BPMN Engine) 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 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.
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.
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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Notion
12 toolsManage your Notion workspace, databases, and pages via AI.

Fireworks AI
6 toolsEmpower LLM applications via Fireworks AI — perform ultra-fast chat completions, generate embeddings and images, and transcribe audio directly from any AI agent.

Salesforce Marketing Cloud
6 toolsManage campaigns, track member engagement, measure marketing ROI, and optimize lead generation through natural conversation.

Craft (Docs & Notes)
10 toolsManage collaborative docs via Craft.do — list documents, handle blocks, track tasks, and retrieve daily notes directly from any AI agent.
