camunda-mcp 0.10.0

Camunda (7 & 8) API + MCP Server + A2A Server for Agentic AI!

Camunda Mcp

API | MCP Server | A2A Agent

Camunda (7 & 8) process automation API + MCP Server + A2A Agent for the agent-utilities ecosystem.

Version: 0.5.0

Documentation — Installation, deployment, usage across the API, CLI, and MCP interfaces, and guidance for provisioning the Camunda platform are maintained in the official documentation.

camunda-mcp wraps the Camunda process automation APIs with thin, deterministic MCP tools, targeting both platforms from a single server: the Camunda 7 Engine REST API and the Camunda 8 Zeebe / Operate / Tasklist REST APIs. It additionally ships an A2A agent server that exposes the same capability through a Pydantic-AI graph agent for agent-to-agent orchestration.

What it provides

• Api (camunda_mcp.api_client) — a facade holding both the Camunda 7 Engine REST client (Camunda7Api) and the Camunda 8 Zeebe / Operate / Tasklist client (Camunda8Api), each constructed lazily so a server configured for one platform never needs the other's URLs or credentials.
• Action-dispatch MCP tools (camunda-mcp console script): camunda_process, camunda_instance, camunda_task, camunda_deploy, camunda_message, camunda_external_task, camunda_job, camunda_history, camunda_deployment, and camunda_ops. Each takes a platform argument (7 or 8). See docs/overview.md for the full surface.
• An A2A agent server (camunda-agent console script, described by a2a.json) wrapping the tool surface in a Pydantic-AI graph agent.

Configuration (environment)

Var	Default	Meaning
CAMUNDA_PLATFORM	7	Target platform: 7 or 8
CAMUNDA_SSL_VERIFY	True	Verify TLS (set False for self-signed homelab)
CAMUNDA7_URL	http://localhost:8080/engine-rest	Camunda 7 Engine REST base URL
CAMUNDA7_TOKEN / CAMUNDA7_USERNAME / CAMUNDA7_PASSWORD	—	Camunda 7 bearer or basic auth
CAMUNDA8_ZEEBE_REST_URL	http://localhost:8080	Camunda 8 Zeebe REST base URL
CAMUNDA8_OPERATE_URL / CAMUNDA8_TASKLIST_URL	—	Camunda 8 Operate / Tasklist URLs
CAMUNDA8_CLIENT_ID / CAMUNDA8_CLIENT_SECRET / CAMUNDA8_OAUTH_URL / CAMUNDA8_AUDIENCE	—	Camunda 8 OAuth client_credentials
CAMUNDATOOL	True	Register the Camunda tool set

Credentials left blank leave the corresponding platform inactive — the connector remains inactive when credentials are absent. A starter .env.example ships with the repository; copy it to .env and populate the values for the platform you use.

Install & run

pip install -e ".[all]"
camunda-mcp                       # stdio MCP server (default transport)
camunda-mcp --transport streamable-http --host 0.0.0.0 --port 8000

Run the A2A agent server against a deployed MCP endpoint:

MCP_URL=http://camunda-mcp:8000/mcp camunda-agent --host 0.0.0.0 --port 8001

MCP config

Register in the multiplexer under nickname camun (tools surface as camun__process, camun__instance, camun__task, …). See camunda_mcp/mcp_config.json.

Additional Deployment Options

camunda-mcp can also run as a local container (Docker / Podman / uv) or be consumed from a remote deployment. The Deployment guide has full, copy-paste mcp_config.json for all four transports — stdio, streamable-http, local container / uv, and remote URL:

• Local container / uv — launch the server from mcp_config.json via uvx, docker run, or podman run, or point at a local streamable-http container by url.
• Remote URL — connect to a server deployed behind Caddy at http://camunda-mcp.arpa/mcp using the "url" key.

Documentation

The complete documentation is published as the official documentation site and is the recommended reference for installation, deployment, and day-to-day operation.

Page	Contents
Installation	pip, source, extras, prebuilt Docker image
Deployment	run the MCP and agent servers, Compose, Caddy + Technitium, env config
Usage	the MCP tools, the Api client, the CLI
Backing Platform	deploy Camunda with Docker
Overview	the Camunda 7 / Camunda 8 surface
Concepts	concept registry (CONCEPT:CAMUNDA-*)

AGENTS.md is the canonical contributor/agent guidance.