MCP-BPMN Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_BPMN_DIAGRAMS_PATH | No | Custom path for storing BPMN diagrams. Overrides the default storage location. | ~/mcp-bpmn/ (Unix) or %USERPROFILE%\mcp-bpmn\ (Windows) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| new_bpmnA | Create a new BPMN diagram and set it as current context |
| new_from_mermaidB | Create a new BPMN diagram from Mermaid code and set it as current context |
| open_bpmnA | Open an existing BPMN file and set it as current context |
| open_mermaid_fileA | Open a Mermaid file, convert it to BPMN, and set as current context |
| saveA | Save the current diagram to its file (error if no filename set) |
| save_asB | Save the current diagram with a new filename |
| closeB | Close the current diagram and clear the context |
| currentB | Get information about the current diagram |
| add_eventC | Add an event to the current diagram |
| add_activityC | Add an activity to the current diagram |
| add_gatewayC | Add a gateway to the current diagram |
| connectC | Connect two elements in the current diagram |
| add_poolC | Add a pool to the current collaboration diagram |
| add_laneA | Add a lane to an existing pool in the current diagram |
| list_elementsB | List all elements in the current diagram |
| get_elementC | Get details of a specific element in the current diagram |
| update_elementB | Update properties of an element in the current diagram |
| delete_elementA | Delete an element from the current diagram |
| exportC | Export the current diagram as BPMN XML |
| validateB | Validate the current diagram for BPMN correctness |
| auto_layoutB | Apply automatic layout to the current diagram |
| list_diagramsA | List all saved BPMN diagrams |
| delete_diagram_fileC | Delete a saved BPMN diagram file |
| get_diagrams_pathA | Get the path where BPMN diagrams are saved |
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 24 tools
Each tool has a clearly distinct purpose, targeting specific operations like adding different BPMN elements, file management, or validation. Overlap is minimal and descriptions clearly differentiate similar tools like new_bpmn and new_from_mermaid.
All tools use snake_case with a verb_noun pattern, which is consistent. The only minor deviation is 'current' as a noun instead of a verb (e.g., get_current), but overall the naming is predictable.
With 24 tools, the count is on the higher side but still reasonable for a comprehensive BPMN editor. Each tool serves a specific function, and the set covers the full workflow without being overwhelming.
The tool set covers core CRUD operations for diagram elements, lifecycle management, validation, export, and layout. Missing features like text annotations or image export are minor gaps, but the overall coverage is solid.