# Camunda MCP connector

The Camunda connector brings process instances, user tasks and incidents to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can find, resolve and complete Camunda work as themselves, with every call logged.

Source: https://elaichi.ai/connectors/camunda/

## Facts

| | |
| --- | --- |
| Application | Camunda |
| Category | Product Development |
| AI tools | 244 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Camunda is connected

- List process instances with open incidents from this week
- Which user tasks assigned to me are still open?
- Show me the process instance with business ID ORD-4821

## Connect Camunda in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Camunda.
2. Optionally set Share with, then press Connect.
3. Paste your Camunda app credentials. Camunda authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Camunda tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Camunda MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Camunda MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Camunda MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Camunda MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Camunda MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Camunda to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Camunda tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Camunda through Elaichi

### Clear the morning's stuck process instances

Operations. Ask for every Camunda process instance with an open incident, read what went wrong, and resolve the ones that only needed a retry before the standup.

### Find a customer's order where it stalled

Support. Give the order number and get the matching Camunda process instance, which step it is sitting on, and which user task is holding it up.

### Move running instances onto the new version

Engineering. After a process deploys, list the instances still on the old version and migrate them in bulk, or suspend them while the fix goes in.

### Work through the approval tasks queue

Finance. List the Camunda user tasks waiting on you, assign the ones a colleague should take, and complete the approvals in one sitting.

### See where a process keeps falling over

Product. Ask which steps of a Camunda process collect the most incidents this month and get a plain summary to bring to the review.

### Pause processes during a planned maintenance window

IT. Suspend the affected Camunda process instances before the window opens, then resume them in bulk once the dependency is back.

## Elaichi vs Zapier MCP vs Composio for Camunda

All three can connect Camunda to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Camunda tools | Allow or restrict single Camunda tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Camunda call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Camunda to Claude?

Connect Camunda in Elaichi, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Camunda's own sign-in step uses app credentials: you enter them once in Elaichi, and there is no OAuth application to register and no client ID or secret to generate. From then on you sign in to Elaichi as yourself and Camunda is available in Claude.

### Does Camunda work with ChatGPT and Cursor as well as Claude?

Yes. Camunda is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You do not set Camunda up again for each client.

### What can an AI agent actually do with my Camunda data?

It can look up a Camunda process instance by ID or business ID, list the instances that are running, suspended or carrying incidents, and start, suspend, resume, migrate or cancel them, one at a time or in bulk. It can also list your user tasks, assign or unassign them, update them and complete them. Short, concrete asks such as "list instances with open incidents" work better than long sentences.

### Does connecting Camunda give the AI everything in my cluster?

No. Every call to Camunda runs as the person who signed in to Elaichi, so the agent sees only the process instances and user tasks that person could already reach. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Camunda itself allows.

### Can my team share one Camunda connection?

Yes. One person connects Camunda in Elaichi and shares it with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who cancelled an instance or completed a task.

### Can I stop an agent from deleting or cancelling things in Camunda?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting or bulk cancelling Camunda process instances for a role or for one person while leaving lookups and task completion open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Camunda connection when someone leaves?

Offboarding that person in Elaichi ends their access to Camunda at once, in every client they used. A shared Camunda connection keeps working for everyone else on the team. If you later want Camunda gone entirely, disconnecting it once in Elaichi removes it from every client.

### Does the Camunda MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Camunda is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Camunda?

Yes. Both let Claude, ChatGPT or Cursor use Camunda. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Camunda call.

### How is Elaichi different from Composio for Camunda?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Camunda: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 244 Camunda tools

Every tool below is callable through https://api.elaichi.ai/mcp once Camunda is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single Camunda process instance by ID** (Get). Get one process instance by its processInstanceKey. Read-only. Required: id (processInstanceKey).
- **List all Camunda process instances** (List). Search process instances by key, process definition, state, parent, incident flag, tenant or business id. Each result has processInstanceKey, processDefinitionId/Key/Name/Version, state (ACTIVE, COMPLETED, TERMINATED), startDate, endDate, hasIncident, tenantId and tags. Pages with a cursor in the request body (page.after from page.endCursor; page.limit default and max 100 per page here). Search results are eventually consistent: newly created data can take a few seconds to appear. Read-only.
- **Camunda process instances cancel** (Cancel). Cancel a running process instance (and its child instances). Returns 204 with an empty body; the cancellation is applied asynchronously. Required: process_instance_id (processInstanceKey).
- **Create a Camunda process instance** (Create). Create process instance. Creates and starts an instance of the specified process. The process definition to use to create the instance can be specified either using its unique key (as returned by Deploy resources), or using the BPMN process id and either a version or a version tag. If only the process definition id is given, the latest ACTIVE version is used. If no ACTIVE version exists, the request is rejected as not found.
- **Camunda process instances bulk cancel** (Cancel). Cancel process instances (batch). Cancels multiple active or suspended process instances. Only ACTIVE and SUSPENDED root instances are cancelled; child instances are cancelled together with their root instance. The given filter only narrows the batch, so a filter on parentProcessInstanceKey matches no instances. Other `state` operators (`$neq`, `$notIn`, `$exists`, `$like`) are applied as given and are not validated. Required: filter.
- **Camunda process instances bulk delete** (Delete). Delete process instances (batch). Delete multiple process instances. This will delete the historic data from secondary storage. Only process instances in a final state (COMPLETED or TERMINATED) can be deleted. This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: filter.
- **Camunda process instances bulk resolve incidents** (Action). Resolve related incidents (batch). Resolves multiple instances of process instances. Since only process instances with ACTIVE state can have unresolved incidents, any given filters for state are ignored and overridden during this batch operation. This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: filter.
- **Camunda process instances bulk migrate** (Action). Migrate process instances (batch). Migrate multiple process instances. Since only process instances with ACTIVE state can be migrated, any given filters for state are ignored and overridden during this batch operation. This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: filter, migrationPlan.
- **Camunda process instances bulk modify** (Action). Modify process instances (batch). Modify multiple process instances. Since only process instances with ACTIVE state can be modified, any given filters for state are ignored and overridden during this batch operation. In contrast to single modification operation, it is not possible to add variable instructions or modify by element key. It is only possible to use the element id of the source and target. This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: filter, moveInstructions.
- **Camunda process instances bulk resume** (Resume). Resume process instances (batch). Resumes multiple suspended process instances. Only SUSPENDED process instances are resumed. The given filter only narrows the batch. Other `state` operators (`$neq`, `$notIn`, `$exists`, `$like`) are applied as given and are not validated. Resumption does not cascade, so child instances are resumed independently of their parent or root instance. This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: filter.
- **Camunda process instances bulk suspend** (Suspend). Suspend process instances (batch). Suspends multiple running process instances. Only ACTIVE process instances are suspended. The given filter only narrows the batch. Other `state` operators (`$neq`, `$notIn`, `$exists`, `$like`) are applied as given and are not validated. Suspension does not cascade, so child instances are suspended independently of their parent or root instance. This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: filter.
- **Camunda process instances assign business ID** (Assign). Assign business id to process instance. Assigns a business id to an already-running process instance that currently has none. Required: process_instance_key, businessId.
- **Delete a Camunda process instance by ID** (Delete). Delete process instance. Deletes a process instance. Only instances that are completed or terminated can be deleted. Required: id (processInstanceKey).
- **Camunda process instances resolve incidents** (Action). Resolve related incidents. Creates a batch operation to resolve multiple incidents of a process instance. Required: process_instance_key.
- **Camunda process instances migrate** (Action). Migrate process instance. Migrates a process instance to a new process definition. This request can contain multiple mapping instructions to define mapping between the active process instance's elements and target process definition elements. Required: process_instance_key, targetProcessDefinitionKey, mappingInstructions.
- **Camunda process instances modify** (Action). Modify process instance. Modifies a running process instance. This request can contain multiple instructions to activate an element of the process or to terminate an active instance of an element. Required: process_instance_key.
- **Camunda process instances resume** (Resume). Resume process instance. Resumes a suspended process instance, returning it to the ACTIVE state and continuing processing. Only process instances in the SUSPENDED state can be resumed. A child process instance can be resumed independently of its parent or root process instance; resumption does not cascade to or from related instances. Required: process_instance_key.
- **Camunda process instances suspend** (Suspend). Suspend process instance. Suspends a running process instance, pausing further processing until it is resumed. Only process instances in the ACTIVE state can be suspended. A child process instance can be suspended independently of its parent or root process instance; suspension does not cascade to or from related instances. Required: process_instance_key.
- **Get single Camunda user task by ID** (Get). Get one user task by its userTaskKey (only Camunda user tasks, not job-worker-based ones). Read-only. Required: id (userTaskKey).
- **List all Camunda user tasks** (List). Search user tasks by assignee, candidate group or user, state (CREATED, COMPLETED, CANCELED, FAILED, ...), process instance, process definition, element, priority, tenant or business id. Pages with a cursor in the request body (page.after from page.endCursor; page.limit default and max 100 per page here). Search results are eventually consistent: newly created data can take a few seconds to appear. Read-only.
- **Camunda user tasks assign** (Assign). Assign a user task to a user. Returns 204 with an empty body. By default an already assigned task is reassigned; set allow_override false to fail instead. Required: user_task_id, assignee.
- **Camunda user tasks complete** (Complete). Complete a user task, optionally setting process variables. Returns 204 with an empty body. Required: user_task_id.
- **Update a Camunda user task by ID** (Update). Update user task. Update a user task with the given key. Updates wait for blocking task listeners on this lifecycle transition. If listener processing is delayed beyond the request timeout, this endpoint can return 504. Other gateway timeout causes are also possible. Retry with backoff and inspect listener worker availability and logs when this repeats. Required: id (userTaskKey).
- **Camunda user tasks unassign** (Action). Unassign user task. Removes the assignee of a task with the given key. Unassignment waits for blocking task listeners on this lifecycle transition. If listener processing is delayed beyond the request timeout, this endpoint can return 504. Other gateway timeout causes are also possible. Retry with backoff and inspect listener worker availability and logs when this repeats. Required: user_task_key.
- **Camunda user tasks get form** (Get). Get user task form. Get the form of a user task. Note that this endpoint will only return linked forms. This endpoint does not support embedded forms. Required: user_task_key.
- **List all Camunda users** (List). Search users by username, name or email. Each result has username, name and email. Pages with a cursor in the request body (page.after from page.endCursor; page.limit default and max 100 per page here). Search results are eventually consistent: newly created data can take a few seconds to appear. Read-only.
- **Create a Camunda user** (Create). Create user. Create a new user. Required: password, username.
- **Get single Camunda user by ID** (Get). Get user. Get a user by its username. Required: id (username).
- **Update a Camunda user by ID** (Update). Update user. Updates a user. Required: id (username).
- **Delete a Camunda user by ID** (Delete). Delete user. Deletes a user. Required: id (username).
- **List all Camunda batch operations** (List). Search batch operations (bulk cancel, migrate, modify, resolve incidents, ...) by key, operation type, state or actor. Pages with a cursor in the request body (page.after from page.endCursor; page.limit default and max 100 per page here). Search results are eventually consistent: newly created data can take a few seconds to appear. Read-only.
- **Get single Camunda batch operation by ID** (Get). Get batch operation. Get batch operation by key. Required: id (batchOperationKey).
- **Camunda batch operations cancel** (Cancel). Cancel Batch operation. Cancels a running batch operation. This is done asynchronously, the progress can be tracked using the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: batch_operation_key.
- **Camunda batch operations resume** (Resume). Resume Batch operation. Resumes a suspended batch operation. This is done asynchronously, the progress can be tracked using the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: batch_operation_key.
- **Camunda batch operations suspend** (Suspend). Suspend Batch operation. Suspends a running batch operation. This is done asynchronously, the progress can be tracked using the batch operation status endpoint (/batch-operations/{batchOperationKey}). Required: batch_operation_key.
- **Create a Camunda deployment** (Create). Deploy one or more BPMN, DMN, form or other resource files (multipart/form-data, one part named resources per file). MCP clients cannot send files; use the proxy API with multipart. Returns deploymentKey and the deployed process definitions, decisions and forms. Required: resources.
- **Camunda incidents resolve** (Action). Resolve an incident (after fixing its cause, e.g. updating variables or job retries) so the process instance continues. Returns 204 with an empty body. Required: incident_id (incidentKey).
- **List all Camunda incidents** (List). Search incidents. Search for incidents based on given criteria. Paginated with a cursor in the request body (up to 100 items per page). Read-only.
- **Get single Camunda incident by ID** (Get). Get incident. Returns incident as JSON. Required: id (incidentKey).
- **List all Camunda topology** (List). Get the cluster topology: brokers, partitions and their roles and health, cluster size, partitions count, replication factor and gateway version. Also used to check the connection. Read-only.
- **Get single Camunda agent definition by ID** (Get). Get agent definition. Returns an agent definition by key. Required: id (agentDefinitionKey).
- **List all Camunda agent definitions** (List). Search agent definitions. Search for agent definitions based on given criteria. Paginated with a cursor in the request body (up to 100 items per page). Read-only.
- **Create a Camunda agent instance** (Create). Create agent instance. Creates a new agent instance. The returned key identifies the instance and must be used in subsequent update and query calls. Required: elementInstanceKey, jobKey, jobLeaseToken, history.
- **Get single Camunda agent instance by ID** (Get). Get agent instance. Returns agent instance as JSON. Required: id (agentInstanceKey).
- **Update a Camunda agent instance by ID** (Update). Update agent instance. Updates the status of an agent instance and appends a batch of history items to its conversation history. Each history item created for this request is echoed back in the response. Required: id (agentInstanceKey), elementInstanceKey, jobKey, jobLeaseToken.
- **List all Camunda agent instances** (List). Search agent instances. Search for agent instances based on given criteria. Paginated with a cursor in the request body (up to 100 items per page). Read-only.
- **List all Camunda agent instance history** (List). Search agent instance history. Searches the conversation history of an agent instance. Committed items are returned by default. Paginated with a cursor in the request body (up to 100 items per page). Read-only. Required: agent_instance_key.
- **List all Camunda audit logs** (List). Search audit logs. Search for audit logs based on given criteria. Paginated with a cursor in the request body (up to 100 items per page). Read-only.
- **Get single Camunda audit log by ID** (Get). Get audit log. Get an audit log entry by auditLogKey. Required: id (auditLogKey).
- **Camunda current user get current** (Get). Get current user. Retrieves the current authenticated user. On an unprotected API (`camunda.security.authentication.unprotected-api=true`) a caller without an identity gets a result with `isAnonymous` set to `true` instead of a `401`, because no credentials can authenticate it there.
- ...and 194 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
