bpmn-generator-mcp
Related Servers
Alternatives to bpmn-generator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI assistants to create and manage one BPMN 2.0 diagram at a time, including Mermaid conversion, validation, layout, persistence, and XML or SVG export.27MIT
- FlicenseNot gradedqualityFmaintenanceEnables AI-driven graphical diagram creation and manipulation using natural language, with support for BPMN workflows, analysis, and manual editing via the Model Context Protocol.1-
- FlicenseBqualityDmaintenanceEnables AI agents to create, manipulate, and manage BPMN 2.0 diagrams programmatically, with support for Mermaid conversion, auto-layout, and file persistence.249-
- AlicenseAqualityCmaintenanceEnables generating, reading, auditing, and previewing BPMN 2.0 diagrams for Bizagi Modeler, with an automatic layout engine that produces files Bizagi can open, plus optional control of the Bizagi Modeler desktop app on Windows.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, explain, lint, and edit existing BPMN 2.0 files in a repository while preserving diagram layout and structural integrity through parsed-document patch operations.Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to programmatically create, modify, and export BPMN 2.0 workflow diagrams. It supports managing various process elements and sequence flows while providing export capabilities to standard XML and SVG formats.712MIT
TDQS
Scored across 41 tools
Many tools are clearly distinct, but the set includes several overlapping reference/catalog tools (e.g., get_flow_elements_catalog vs list_bpmn_elements, get_activities_catalog vs get_task_types_info) and closely related creation variants (e.g., create_process_with_boundary_events vs create_process_with_error_handling). Descriptions help, but an agent could easily select the wrong lookup or generator in a 41-tool surface.
Tool names consistently use snake_case and mostly follow a verb_noun pattern, which is predictable. Minor deviations exist, such as create_from_yaml_spec vs create_process_from_text_description vs create_simple_linear_process, but the overall style remains coherent.
With 41 tools, the server is over-scoped for most agent workflows. The many catalog/reference/lookup tools could be consolidated into a smaller set, and the proliferation of create_process_with_* variants adds unnecessary bulk.
The server covers BPMN generation well: multiple construction patterns, validation, templates, catalogs, OCR input, and output file access. Minor gaps exist around updating/deleting generated files or directly editing existing BPMN models, but these are not core to a generator's main workflow.