Miragon AIImplement
Solution templatesYour own MCP server, engine tools included.
miragon-ai-starter, a GitHub template for developers, brings Pulse's modules for Camunda 7, CIB seven and Operaton, plus room for your own modules, such as your ERP. mcp-toolkit-starter is the base without BPM.
gh repo create my-mcp-server \ --template Miragon/miragon-ai-starter \ --private --clonecd my-mcp-serverpnpm installDone in 52.7s using pnpm v10.32.1cp .env.example .envpnpm dev[mcp-use] dev server ready ➜ MCP endpoint: http://localhost:8400/mcp ➜ Inspector: http://localhost:8400/mcp/inspector# camunda7 and analytics are in# add yours, in a second terminalcp -R modules/mcp-notes modules/mcp-erpThe problem
Reaching your ERP means forking Pulse or starting from scratch
Pulse covers the engine, and its stock server has no place for your ERP or CRM without a fork. From scratch, you wire OAuth, health checks, metrics, a Docker image and a widget bundle yourself, and some wiring mistakes only show up as a widget that renders empty or hangs on “Loading…”.
From scratch
- Tools written against the engine's REST API
- Working out how tool, widget and data fit together
- Wiring mistakes that show up as an empty widget
- A coding agent without guidance
- Login and permissions built by hand
- Dockerfile, probes and metrics endpoint by hand
With miragon-ai-starter
- camunda7_* and analytics_* tools with widgets, from Pulse's modules
- A copy of the example module mcp-notes, next to the engine modules
- Guard tests in server/test/ that fail when a wiring step is missing
- CLAUDE.md and four Claude Code skills, create-module among them
- OAuth with Keycloak or Auth0, engine tools start read-only without it
- A Docker image with a health check, /health/live, /health/ready and /metrics
How it works
From the template to a server with your own module
Shown for miragon-ai-starter. mcp-toolkit-starter brings a tasks module in place of the engine modules.
Create
Use the template on GitHub or with gh repo create. Everything installs from the public npm registry, without credentials.
Run
pnpm dev serves MCP on port 8400 with an inspector. The example widget renders without an engine or any other system.
Add your system
Copy modules/mcp-notes into a module for your ERP. The create-module skill walks your coding agent through the wiring.
Ship
The project builds into a Docker image with health probes, Prometheus metrics and OAuth. Without OAuth, the engine tools start read-only.
Two templates
With the engine modules or without them
- Engine plus your systemsmiragon-ai-starterPulse's modules for Camunda 7, CIB seven and Operaton, the example module mcp-notes, the guard tests, CLAUDE.md and four Claude Code skills. MIT licence.Open
- Without BPMmcp-toolkit-starterA plain mcp-use project with one tasks module and a widget, for systems that have nothing to do with a process engine.Open
Both templates build on mcp-use. Neither contains process automation code such as job workers or a BPMN project. Your team decides which systems the server may reach and reviews the module code.
Built for your coding agent
Four skills walk the agent through the wiring
Open miragon-ai-starter in Claude Code, or any agent that reads CLAUDE.md, and describe what you want. The skills in .claude/skills/ cover the four common tasks.
- setup-serverConfiguring, running, branding and deploying the server.
- create-moduleA connector module for your own API or system.
- add-widgetAn interactive widget for a module.
- add-settings-sectionPer-user settings for your module.
Everything also works by hand. CLAUDE.md is the compact architecture reference, and the guard tests in server/test/ fail when a wiring step is missing.
Get started
Your own MCP server from the template
Create your repo from the template, then run it from source or as a container. The README of Miragon/miragon-ai-starter has the steps.
Status
Where the templates stand on 14 October 2026
Pulse is the MCP server from the repo Miragon/miragon-ai. miragon-ai-starter is at Pulse v0.20.0, released 2026-10-13, and public under the MIT licence.
Synced on every Pulse release
miragon-ai-starter mirrors templates/composed-server and syncs once install and tests pass against the public npm registry. Neither template repo has releases of its own.
Pre-1.0 packages
The starter pins the @miragon-ai packages at 0.20.0. They release about weekly and still bring breaking changes.
No licence for mcp-toolkit-starter
It is public but has no licence yet, so there are no stated terms for building on it.
Red CI on mcp-toolkit-starter
It pins the Miragon MCP Toolkit at 2.8.1, released 2026-10-13. Its own CI failed after the last two syncs, because each ran minutes before the new toolkit version reached npm.
Proof you can open
Sources, packages and playgrounds
- templates/composed-serverThe source of miragon-ai-starter in Miragon/miragon-ai, where issues and pull requests go.Open
- templates/minimal-serverThe source of mcp-toolkit-starter in Miragon/mcp-toolkit.Open
- Pulse playgroundAn MCP endpoint without login, running the stock Pulse server built from the same @miragon-ai modules, read-only.Open
- Toolkit playground tourSeven stops through the toolkit's tools and widgets on a hosted server.Open
- camunda7-connector on npm@miragon-ai/camunda7-connector, the engine module the starter composes.Open
- MCP Toolkit docsThe guides behind mcp-toolkit-starter.Open
Where it fits
Solution templates in the lifecycle
- PhaseImplementSolution templates connect your AI to the engine and to your own systems.Learn more
- Same phaseSkillsSkills make the model deployable. No file passes between them and the templates.Learn more
- Next phaseExecuteReceives a Docker image that serves MCP on /mcp. You connect it to Claude Code, Claude Desktop, claude.ai or another MCP client.Learn more
- Stock serverPulseYour server has the same camunda7_* and analytics_* tools as Pulse, plus your own. You use it the way you use Pulse.Learn more
- Same engine APIoperateReaches the engine REST API on its own, from the shell and CI.Learn more
- LifecycleMiragon AIAll phases of the lifecycle and the tools in each.Learn more
Models from designIQ or bpmn-cli reach the server only through the engine, where tools such as camunda7_get_process_definition_xml read them. With the camunda7:admin toolset and CAMUNDA_ALLOW_DEPLOYMENTS=true, the assistant can deploy BPMN and DMN itself.
Bring your own systems next to the engine.
Tell us which systems your assistant should reach besides Camunda 7, CIB seven or Operaton. You get an honest assessment of whether miragon-ai-starter is the right start.
Talk to usA 30-minute first call.