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.
- App credentials
- Free 14-day trial
- No credit card
List process instances with open incidents from this week
Working in Camunda with Elaichi
-
Get single Camunda process instance by ID
-
List all Camunda process instances
-
Get single Camunda user task by ID
How to connect Camunda to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Camunda MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Camunda MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Camunda through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Camunda is logged.
-
Operations
Clear the morning's stuck process instances
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.
-
Support
Find a customer's order where it stalled
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.
-
Engineering
Move running instances onto the new version
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.
-
Finance
Work through the approval tasks queue
List the Camunda user tasks waiting on you, assign the ones a colleague should take, and complete the approvals in one sitting.
-
Product
See where a process keeps falling over
Ask which steps of a Camunda process collect the most incidents this month and get a plain summary to bring to the review.
-
IT
Pause processes during a planned maintenance window
Suspend the affected Camunda process instances before the window opens, then resume them in bulk once the dependency is back.
Try asking
- “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”
What connecting Camunda gets you
6 screens from Elaichi, each doing one job for your Camunda account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Camunda questions, get answers from live instances.
Three starter prompts pull process instances, user tasks and incidents into plain answers.
Copy the endpoint
AI apps
One endpoint puts Camunda in every client.
Claude, ChatGPT and Cursor reach Camunda through one governed endpoint, no SDK, no shared key.
Tool catalog
All 244 Camunda tools, no code to write.
Process instances, user tasks and incidents covered, with resources and methods listed in one catalog.
Toolboxes
Each team gets its own Camunda toolbox.
Operations, support and engineering each see a toolbox scoped to the work they do.
Shared connections
Share a Camunda connection, never a credential.
The table shows who connected each account and which teams and members work through it.
Audit log
Every Camunda call names the person behind it.
When, who, what happened, type and resource, so cancelled instances are never a mystery.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Camunda digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch process instances
Camunda
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Camunda
Queued
Workflows
A schedule starts Camunda work, a person approves.
Open incidents are fetched, grouped, drafted into a digest, approved, then posted back to Camunda.
Camunda health
Refreshed 4 minutes ago · every 15 minutes · from the process instances collection
Process instances
1,284 ↓ 12%
User tasks
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Process instances created
Last 14 days
By team
Share of activity
Operations 34%
Support 27%
Engineering 21%
Finance 18%
Collections and dashboards
Camunda health numbers, computed without asking anyone.
Four metrics, 14 days of process instances created, a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Camunda tools for your AI agents
244 tools are ready to call through Elaichi's MCP endpoint the moment you connect Camunda, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Camunda in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot