BPMN-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| create_bpmn_diagramC | Create a new BPMN diagram. Returns a diagram ID that can be used with other tools. |
| add_bpmn_elementC | Add an element (task, gateway, event, etc.) to a BPMN diagram |
| connect_bpmn_elementsC | Connect two BPMN elements with a sequence flow |
| export_bpmn_xmlC | Export a BPMN diagram as XML |
| export_bpmn_svgC | Export a BPMN diagram as SVG |
| list_bpmn_elementsC | List all elements in a BPMN diagram |
| import_bpmn_xmlC | Import an existing BPMN XML diagram |
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 7 tools
Each tool has a clearly distinct purpose: create_diagram, add_element, connect_elements, list_elements, import_xml, export_xml, and export_svg. There is no overlap in functionality—tools target specific actions like creation, modification, listing, import, and export without ambiguity.
All tools follow a consistent verb_noun pattern with 'bpmn' as a prefix (e.g., create_bpmn_diagram, add_bpmn_element). The naming is uniform across all seven tools, using snake_case and clear action descriptors without any deviations.
With 7 tools, the set is well-scoped for BPMN diagram management. It covers core operations like create, modify, list, import, and export, which is appropriate for the domain without being too sparse or bloated.
The toolset provides strong coverage for BPMN diagram lifecycle: create, modify (add/connect), list, import, and export (XML/SVG). A minor gap is the lack of update or delete operations for elements or diagrams, but agents can work around this by re-importing or managing via XML.