bpmn-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BPMN_BROWSER | No | Path to Chrome or Edge, only needed for the PNG and the Camunda import check. Set BPMN_BROWSER if it is not found automatically. | |
| BPMN_BROWSER_ARGS | No | Extra flags to pass to the browser (for example --no-sandbox on a locked-down Linux machine). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bpmn_setup_checkA | Check that this computer can draw diagrams. Writes nothing. Returns plain-language findings. Run this when a user asks to set up, or when a build fails with a browser error. |
| bpmn_spec_guideA | Return the diagram spec format, layout rules and the fixes for each check error. Read this before the first bpmn_build call. |
| bpmn_buildA | Lay out and check a diagram, and write the files. spec: the diagram as a JSON object (see bpmn_spec_guide). name: file name without extension (letters, digits, - and _). out_dir: folder under the current working folder for the outputs. stage: "svg" = checks plus SVG only (use while drafting); "all" = also PNG, .bpmn and the Camunda import check (use only after the user approved the drawing). preview: also write a look-at-it PNG (svg stage) or a Camunda preview (all stage). Returns ok, errors (fix every one and build again), warnings, files (relative paths) and the log. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool occupies a distinct stage of a single workflow: environment check, spec reference, and build. There is no overlap in purpose, and descriptions explicitly state when to use each (e.g. read the guide before the first build).
All three share a clear bpmn_ prefix, giving a predictable namespace. The suffixes mix noun forms (spec_guide, setup_check) with a bare verb (build), a minor deviation from a strict verb_noun pattern but still readable.
Three tools is thin but justified for a narrowly scoped diagram-generation server, with each tool earning its place. A separate validate-only tool could arguably be split from bpmn_build, but the current split is defensible.
The surface covers the full draft-to-approved lifecycle (setup check, spec guide, staged build with checks and preview). Gaps are minor: there is no way to inspect or re-validate an existing .bpmn file or list prior outputs without rebuilding.