Skip to main content
Glama

Related Servers

Alternatives to MCP-BPMN Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to create and edit valid BPMN 2.0 diagrams with automatic layout, validation, and export to XML, SVG, PNG, and other formats. Supports HTTP deployment with token-based authentication and session-isolated diagram handling.
      20
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to create, manipulate, and manage BPMN 2.0 diagrams programmatically, with support for Mermaid conversion, auto-layout, and file persistence.
      24
      13
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants and other tools to create, edit, import, and export BPMN 2.0 workflow diagrams, including through a local browser-based live modeler with explicit save back to the session.
      11
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables 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
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables assistants to turn a plain-language process description into a checked BPMN swimlane diagram, asking only for missing details and showing a picture for approval. Once approved, it exports the diagram as SVG, PNG and a .bpmn file that opens in Camunda, all drawn and checked locally on the user's own computer.
      3
      MIT
    • F
      license
      C
      quality
      B
      maintenance
      Enables generating BPMN 2.0 process models from natural language descriptions, YAML, or images via OCR, with templates, validation, and compatibility with tools like Bizagi Modeler and Camunda Modeler.
      41
      -

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action or resource. Element creation tools are separated by type (event, activity, gateway, data object, annotation, pool, lane), and file operations are distinct (new, open, save, save_as, close, list, delete). No two tools appear to overlap in purpose.

    Naming Consistency4/5

    The naming pattern is mostly consistent with verb-first, underscore-separated names (e.g., add_event, list_elements, delete_diagram_file). Minor deviations exist, such as 'new_from_mermaid' and 'open_mermaid_file' vs. 'open_bpmn', and the noun 'current' as a standalone tool, but overall the convention is coherent.

    Tool Count4/5

    27 tools is above the typical 3-15 range, but the complexity of a BPMN editor justifies the breadth. The tools cover file management, element operations, validation, layout, and export without excess overlap, so the count feels justified rather than bloated.

    Completeness5/5

    The tool surface is remarkably complete for a BPMN diagramming server. It covers full CRUD for elements and files, connections, associations, validation at multiple levels, layout, and export. There are no glaring gaps that would hinder common workflows, including lifecycle operations for diagrams and elements.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues