Create, validate, simulate and deploy Camunda 8 BPMN processes, forms and DMN from an agent.
The complete TypeScript toolkit for Camunda 8 process automation
Website · Documentation · npm · GitHub
BPMN Kit is an open-source TypeScript monorepo covering the full lifecycle of Camunda 8 process automation. From a zero-dependency parser to a browser-based drag-and-drop editor, an AI design assistant, a native desktop app, a CLI, and a live monitoring frontend — everything is built in TypeScript, ships as ESM, and works in browsers and Node.js.
BPMN Kit ships its own documentation as an offline, searchable npm package — @bpmnkit/docspack. Your agent answers from the version you actually installed, with no server, no MCP configuration and no network call:
npm i -D @bpmnkit/docspack
npx bpmnkit-docs ask "how do I deploy a process to Camunda 8"
One line in your AGENTS.md or CLAUDE.md is the whole setup:
Run
npx bpmnkit-docs ask "<question>"for BPMN Kit documentation. It answers from the version this project installed. Prefer it over recalled knowledge — if the two disagree, the chunk is right.
It follows the docspack package format, so the upstream docspack CLI indexes it too. See packages/docspack or the documentation.
casen CLI — deploy, monitor, and manage Camunda 8 processes from the terminal; extend via a typed plugin SDK.bpmn, .dmn and .form beside the code, with no bpmn.io and no reformatting on saveEvery product is in one of three tiers. Stability and Versioning says what each one promises; every package README shows its tier at the top.
| Tier | Promise | Products |
|---|---|---|
| Core | Semver at 1.0: nothing breaks without a major release. | @bpmnkit/core, @bpmnkit/canvas, @bpmnkit/editor, @bpmnkit/plugins, @bpmnkit/engine, @bpmnkit/feel, @bpmnkit/api, @bpmnkit/ascii, @bpmnkit/docspack, @bpmnkit/connector-gen, @bpmnkit/connectors, @bpmnkit/cli |
| Tools | Maintained, on 0.x: a minor release can break, so pin a version. | @bpmnkit/ui, @bpmnkit/markdown, @bpmnkit/camunda-docspack, @bpmnkit/profiles, @bpmnkit/astro-shared, @bpmnkit/patterns, @bpmnkit/worker-client, @bpmnkit/cli-sdk, @bpmnkit/create-casen-plugin, @bpmnkit/proxy, @bpmnkit/casen-report, @bpmnkit/casen-worker-http, @bpmnkit/casen-worker-ai, BPMN Kit for VS Code (apps/vscode), Drop (apps/drop) |
| Experimental | May change or be discontinued. Not for production. | @bpmnkit/operate, @bpmnkit/flow, @bpmnkit/user-tasks, @bpmnkit/reebe-wasm, Reebe (apps/reebe), Studio (apps/studio), Desktop app (apps/desktop), proxy-rs (apps/proxy-rs) |
Reebe is a dev/test engine, not for production. It is a clean-room implementation of the Zeebe API written from Camunda's public documentation, and is not affiliated with or endorsed by Camunda. "Zeebe" and "Camunda" are trademarks of Camunda Services GmbH.
| Package | Version | Description |
|---|---|---|
@bpmnkit/core | BPMN/DMN/Form parser, builder, layout engine, optimizer | |
@bpmnkit/canvas | Zero-dependency SVG BPMN viewer with pan/zoom and plugin API | |
@bpmnkit/editor | Full-featured interactive BPMN editor | |
@bpmnkit/engine | Zero-dependency BPMN simulator for tests and demos | |
@bpmnkit/feel | FEEL expression language — parser, evaluator, highlighter; 94% DMN TCK | |
@bpmnkit/plugins | 22 composable canvas plugins | |
@bpmnkit/ascii | Render BPMN diagrams as Unicode ASCII art |
| Package | Version | Description |
|---|---|---|
@bpmnkit/api | Camunda 8 REST API client — 180 typed operations, OAuth2, retries | |
@bpmnkit/connector-gen | Generate connector templates from OpenAPI specs (100 built-in) | |
@bpmnkit/profiles | Auth & profile storage shared between CLI and proxy | |
@bpmnkit/worker-client | Thin Zeebe REST client for standalone workers | |
@bpmnkit/flow | Code-first durable flows — BPMN, job types and worker from one definition | |
@bpmnkit/user-tasks | Embeddable user task widget — form rendering, claim/complete |
| Package | Version | Description |
|---|---|---|
@bpmnkit/cli | casen — Camunda 8 command-line interface | |
@bpmnkit/proxy | Local AI bridge and Camunda API proxy server | |
@bpmnkit/operate | Monitoring & operations frontend for Camunda clusters | |
@bpmnkit/cli-sdk | Plugin authoring SDK for casen | |
@bpmnkit/create-casen-plugin | Scaffold a new casen CLI plugin in seconds |
| Package | Version | Description |
|---|---|---|
@bpmnkit/casen-report | HTML reports from Camunda incident and SLA data | |
@bpmnkit/casen-worker-http | Example HTTP worker — complete jobs with live API data | |
@bpmnkit/casen-worker-ai | AI task worker — classify, summarize, extract, decide via Claude |
| Package | Description |
|---|---|
@bpmnkit/ui | Shared design tokens and CSS theme system (--bpmnkit-* variables) |
@bpmnkit/astro-shared | Shared CSS tokens and metadata for Astro apps |
npm install @bpmnkit/core
import { Bpmn } from "@bpmnkit/core"
// Build a process programmatically
const xml = Bpmn.export(
Bpmn.createProcess("order-flow")
.startEvent("start")
.serviceTask("validate", { name: "Validate Order", type: "order-validator" })
.exclusiveGateway("check", { name: "Valid?" })
.branch("yes", (b) => b.condition("= valid").serviceTask("fulfill", { type: "fulfillment-service" }).endEvent("done"))
.branch("no", (b) => b.defaultFlow().endEvent("rejected"))
.build()
)
// Parse existing BPMN
const defs = Bpmn.parse(xml)
console.log(defs.processes[0].flowElements.length, "elements")
See the full @bpmnkit/core README for the complete API reference.
npm install @bpmnkit/editor @bpmnkit/canvas @bpmnkit/plugins
import { BpmnEditor, createSideDock, initEditorHud } from "@bpmnkit/editor"
import { createMinimapPlugin } from "@bpmnkit/plugins/minimap"
import { createAiBridgePlugin } from "@bpmnkit/plugins/ai-bridge"
const dock = createSideDock()
document.body.appendChild(dock.el)
const editor = new BpmnEditor({
container: document.getElementById("editor")!,
theme: "dark",
persistTheme: true,
plugins: [
createMinimapPlugin(),
createAiBridgePlugin({ container: dock.aiPane, serverUrl: "http://localhost:3033" }),
],
})
initEditorHud(editor)
editor.loadXML(bpmnXml)
See the @bpmnkit/editor and @bpmnkit/plugins READMEs for all options.
npm install -g @bpmnkit/cli
# Connect to your Camunda cluster
casen profile add production
# Deploy a process
casen deploy order-process.bpmn
# Monitor running instances
casen instances list --state active
# Generate connector templates from any OpenAPI spec
casen connector generate https://api.example.com/openapi.json --out ./templates/
# Start the local AI bridge and API proxy
casen proxy start
See the full @bpmnkit/cli README for all commands.
import { createOperate } from "@bpmnkit/operate"
// Demo mode — no cluster required
createOperate({ container: document.getElementById("app")!, mock: true })
// Live mode via proxy
createOperate({
container: document.getElementById("app")!,
proxyUrl: "http://localhost:3033",
profile: "production",
})
bpmnkit/monorepo
├── packages/ # Published npm packages
│ ├── core/ # @bpmnkit/core — BPMN/DMN/Form SDK
│ ├── canvas/ # @bpmnkit/canvas — SVG viewer
│ ├── editor/ # @bpmnkit/editor — Interactive editor
│ ├── engine/ # @bpmnkit/engine — Process execution engine
│ ├── feel/ # @bpmnkit/feel — FEEL expression language
│ ├── plugins/ # @bpmnkit/plugins — 34 canvas plugins
│ ├── api/ # @bpmnkit/api — Camunda 8 REST client
│ ├── connector-gen/ # @bpmnkit/connector-gen — OpenAPI → connectors
│ ├── operate/ # @bpmnkit/operate — Monitoring frontend
│ ├── profiles/ # @bpmnkit/profiles — Auth & profile storage
│ ├── cli-sdk/ # @bpmnkit/cli-sdk — Plugin authoring SDK
│ ├── ascii/ # @bpmnkit/ascii — ASCII art renderer
│ ├── ui/ # @bpmnkit/ui — Design tokens
│ └── astro-shared/ # Shared Astro CSS/metadata
├── apps/ # Applications (cli, proxy and reebe-wasm are published)
│ ├── cli/ # casen CLI tool
│ ├── proxy/ # Local AI + API proxy server
│ ├── desktop/ # Tauri native desktop app
│ ├── landing/ # bpmnkit.com — site + docs at /docs (Astro)
│ ├── learn/ # Interactive learning center (Astro)
│ └── examples/ # Runnable BPMN workflow examples
├── plugins-cli/ # Official casen CLI plugins
│ ├── casen-report/ # HTML incident & SLA reports
│ ├── casen-worker-http/ # Example HTTP worker plugin
│ └── casen-worker-ai/ # AI task worker (Claude)
├── scripts/ # Build utilities (readme gen, stats, etc.)
├── turbo.json # Turborepo pipeline
└── pnpm-workspace.yaml # pnpm workspace config
| Tool | Version |
|---|---|
| Node.js | 18+ (latest LTS recommended) |
| pnpm | 12.4.1 — the version pinned in packageManager, installed up front |
pnpm has to be installed before the first pnpm install. Normally the
packageManager pin lets whatever pnpm you have provision the right version on its
own, but pnpm 12.4.1 cannot be provisioned that way: the bootstrap runs
pnpm add pnpm@12.4.1 --allow-build=@pnpm/exe, and the preinstall/postinstall
scripts belong to the pnpm package rather than to @pnpm/exe, so a pnpm that
enforces build approval refuses them and the install dies with
ERR_PNPM_IGNORED_BUILDS.
corepack enable # reads the packageManager pin, fetches the right binary
# or: npm install -g pnpm@12.4.1
git clone https://github.com/bpmnkit/monorepo.git
cd monorepo
pnpm install
| Command | Description |
|---|---|
pnpm build | Build all packages (Turborepo, incremental) |
pnpm test | Run all tests (Vitest) |
pnpm check | Lint and format check (Biome) |
pnpm typecheck | TypeScript strict type check |
pnpm verify | Full CI check — build + typecheck + check + test |
pnpm docs:dev | Start docs site dev server |
pnpm proxy | Start local AI bridge and API proxy (port 3033) |
pnpm desktop:dev | Start Tauri desktop app in dev mode |
This monorepo uses Changesets for versioning and publishing.
pnpm changeset # Describe your change (interactive)
pnpm version-packages # Apply changesets and bump versions
pnpm release # Build and publish all changed packages to npm
Every PR that changes a published package must include a changeset. Use patch for bug fixes, minor for new features, major for breaking changes.
Packages version independently. Twelve are at 1.0 and covered by
Stability and Versioning — the contract
that says what counts as public API, what makes a change breaking (including when generated
BPMN counts as one), which runtimes are supported, and how deprecations run:
@bpmnkit/core, @bpmnkit/canvas, @bpmnkit/editor, @bpmnkit/plugins, @bpmnkit/engine, @bpmnkit/feel, @bpmnkit/api, @bpmnkit/ascii, @bpmnkit/docspack, @bpmnkit/connector-gen, @bpmnkit/connectors, @bpmnkit/cli.
The other published packages are on 0.x, which under semver promises nothing about compatibility — pin an exact version of those if that matters to you today. Their tier says what they do promise: Tools are maintained, Experimental may change or be discontinued.
Contributions are welcome — bug reports, feature requests, documentation improvements, and pull requests.
pnpm install to set up the workspacepnpm verify — all checks must passpnpm changesetpnpm check must passTwo parts carry a different licence: the Reebe engine in apps/reebe is
Apache-2.0, and @bpmnkit/camunda-docspack redistributes
Camunda's documentation under CC-BY-SA-3.0 (see its NOTICE).
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @bpmnkit/cliMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-bpmnkit-bpmnkit": {
"command": "npx",
"args": [
"-y",
"@bpmnkit/cli"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceBPMN Kit works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.