Processes MCP Server
Enable AI agents to discover and call your deployed BPMN processes as MCP tools.
About
The Processes MCP Server is a capability of the Orchestration Cluster that exposes your deployed BPMN processes as callable tools through the Model Context Protocol (MCP).
- Any process equipped with an MCP start event element template is automatically registered as an MCP tool when deployed.
- MCP clients discover these tools at runtime and invoke them by name. Each invocation starts a new process instance and returns the started process instance key immediately.
- The server shares the same authentication and authorization model as the Orchestration Cluster REST API.
The Processes MCP Server is not part of the Camunda 8 public API.
This is the Processes MCP Server documentation. If you are looking to:
- Give AI agents access to Camunda's operational capabilities, such as incidents, user tasks, and process instances, see the Orchestration Cluster MCP Server.
- Connect an AI agent running inside a BPMN process to an external MCP server, see the MCP Client connector.
Key features
| Feature | Description |
|---|---|
| Process tool registration | Processes with an MCP start event are automatically registered as MCP tools on deployment. |
| Tool discovery | MCP clients discover available process tools and their schemas at runtime. |
| Static tools | The server also exposes a set of static tools for inspecting running process instances. |
| Version binding | Only the latest deployed version of a process is exposed. See Version binding. |
| Standard transport | Uses Streamable HTTP, compatible with any MCP-compliant client. |
Authentication
The Processes MCP Server uses the same authentication model as the Orchestration Cluster REST API. OAuth tokens obtained for the REST API work without changes.
For the full authentication reference, including SaaS and Self-Managed setup, see Authentication.
Transport
The Processes MCP Server uses Streamable HTTP and is served at the /mcp/processes endpoint on the Orchestration Cluster. It is stateless; no session management is required.
Get started
The Processes MCP Server is only available from Camunda 8.10 onwards.
To expose a BPMN process as an MCP tool, see Expose a process as an MCP tool.
If you have a local Orchestration Cluster running with Camunda 8 Run or Docker Compose, the Processes MCP Server is enabled by default. Connect any MCP client using this configuration:
{
"servers": {
"camunda-processes": {
"type": "http",
"url": "http://localhost:8080/mcp/processes"
}
}
}
For production environments and other deployment types, the Processes MCP Server must be explicitly enabled before use. See Enable and connect for more details.
Static tools
In addition to dynamically registered process tools, the Processes MCP Server exposes a set of static tools for inspecting the process instances it starts. See static tools for more details.