Skip to main content
Glama
Mendix Context Bridge

Mendix Context Bridge

by EGorsel

Related Servers

Alternatives to Mendix Context Bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      Not graded
      maintenance
      Enables AI assistants to extract and document Mendix Studio Pro modules by interrogating local .mpr files. Generates comprehensive JSON documentation of domain models, pages, microflows, and enumerations without sending data to the cloud.
      1
      7 npm
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to connect local knowledge bases, preview and index selected directories, search for traceable snippets with source metadata, and read indexed document versions through MCP tools.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to read and modify Mendix application models through MCP tools for creating modules, entities, pages, microflows, deploying, and querying runtime data.
      1
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable AI clients to read user-authorized local folders, inspect code and tables, and propose file changes that users review and apply in VS Code.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure, read-only access to local project files (including text, DOCX, PDF, and XLSX) through MCP, with strict directory whitelisting and no write, edit, or command-execution tools.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_domain_model covers entities and types in a module, inspect_database_schema focuses on table column structures, inspect_local_microflow handles microflow logic steps, and list_local_modules lists modules in a file. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as get_domain_model, inspect_database_schema, inspect_local_microflow, and list_local_modules. This uniformity makes the set predictable and easy to understand.

    Tool Count4/5

    With 4 tools, the count is slightly low but reasonable for the server's purpose of providing Mendix context insights. It covers key areas like modules, domain models, database schemas, and microflows, though it might benefit from additional tools for more comprehensive coverage.

    Completeness3/5

    The tools cover basic inspection and listing functions for modules, domain models, database schemas, and microflows, but there are notable gaps. For example, there are no tools for creating, updating, or deleting elements, which limits the server to read-only operations and may cause agent failures in workflows requiring modifications.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues