Important
Pulse is below 1.0.0, so its API is not stable: tools, settings, metric names, CLI commands and
the exports of the @miragon/pulse-* packages can change in any release. The
changelog lists every breaking change. Pin exact versions and update all
@miragon/pulse-* packages together.
Pulse brings your Camunda 7, CIB seven and Operaton engines to where you already work. One idea, three clients on the same engines:
- Your AI chat: an MCP server that answers with interactive views of incidents, instances and diagrams, in Claude, ChatGPT and other hosts.
- Your terminal:
pulse, every engine operation as one short command, for people and AI agents alike. - VS Code: runtime data next to your BPMN models: instances, incidents, variables and retries.
Pulse is part of Miragon AI, the family of Miragon's AI tools.
Finding out why a process instance is stuck usually means a cockpit, a few REST calls and a log. Pulse brings the engine to you instead:
- One question, one answer. Ask why an order is stuck and get the incident, the diagram and the root cause, in the chat, in one command or next to the model.
- Every engine of your fleet. CIB seven, Operaton and Camunda 7 side by side, with a default engine and an override per call.
- Safe by default. The MCP server starts read-only, the CLI previews a change with
--dry-runand asks before it deletes, and VS Code writes only to a local engine unless you allow more. - Analytics without the engine database. Process KPIs, bottlenecks and engine comparisons come from Prometheus, fed by a small metrics plugin in the engine.
- Self-hosted and open. One container image, public npm packages, MIT licensed.
| Client | Install | Read on |
|---|---|---|
| Your AI chat | docker run ghcr.io/miragon/pulse-server, or try the public playground |
Server README, docs |
| Your terminal | npm install -g @miragon/pulse-cli or brew install miragon/tap/pulse-cli |
CLI README, docs |
| VS Code | Pulse from the Marketplace or Open VSX (early prototype) | Extension README, docs |
No engine at hand? Connect your Claude to the public playground, or
start one locally with docker run -p 8080:8080 operaton/operaton:2.1.5.
| Path | Package | Role |
|---|---|---|
apps/mcp-server/ |
ghcr.io/miragon/pulse-server |
The MCP server: composes the modules, serves HTTP on :8400 |
apps/cli/ |
@miragon/pulse-cli |
The command line interface |
apps/vscode/ |
pulse-cockpit (a .vsix) |
Pulse for VS Code |
packages/connectors/engine/engine-connector/ |
@miragon/pulse-engine-connector |
Operations tools and widgets for Camunda 7 engines |
packages/connectors/analytics/analytics-connector/ |
@miragon/pulse-analytics-connector |
Prometheus-backed analytics tools and dashboards |
packages/connectors/engine/engine-client/ |
@miragon/pulse-engine-client |
Typed REST SDK and client for the engine |
packages/connectors/engine/engine-core/ |
@miragon/pulse-engine-core |
Camunda 7 workflow domain and pure engine REST rules |
packages/connectors/analytics/analytics-client/ |
@miragon/pulse-analytics-client |
Prometheus client, PromQL queries and the metrics contract |
packages/core/ui/ |
@miragon/pulse-ui |
Design kit for Pulse views and your own React UIs |
packages/core/widget-shell/ |
@miragon/pulse-widget-shell |
View runtime and server boot for composed MCP servers |
engine-plugins/ |
io.miragon.mcp:cibseven-history-metrics |
Micrometer metrics plugin for the engine (Java 21) |
playground/ |
— | Demo engine, Compose stack and the public playground |
templates/composed-server/ |
Miragon/pulse-starter |
Starter for your own server |
The docs site, miragon.github.io/pulse, is built from docs/,
one section per client:
- MCP server: getting started, usage, every tool, operations, architecture, building your own server
- CLI: install, commands, configuration, authentication, AI agents
- VS Code: installation, configuration, usage, architecture
The product page is miragon.ai/tools/pulse.
A fresh clone needs Node.js 22.22.2 or later, pnpm (corepack enable, or npm i -g pnpm@10.32.1 on
Node.js 25 and later) and Docker; no JDK (Gradle runs in a container without one), no .env:
pnpm play # installs, starts the playground, builds, MCP server on :8400, inspector at /mcp/inspector
pnpm play:cli -- ping # the CLI against the playground engine
pnpm stack:status # what runs; pnpm stack:up / stack:down start and stop the playground
pnpm check # the bar for every change: build, typecheck, test, lint, formatDetails: developer guide; the rules for code changes are in CLAUDE.md.
release-please releases everything together:
semantic commits on main open a release PR, and merging it publishes the server image, the npm
packages, the CLI (npm, binaries, image, Homebrew miragon/tap/pulse-cli), the VS Code extension
(Marketplace and Open VSX) and the engine plugin (Maven Central).
Issues, pull requests and discussions are welcome on GitHub.
Use semantic commit messages (they drive the release) and
keep pnpm build && pnpm typecheck && pnpm test && pnpm lint green.
MIT © Miragon GmbH