Skip to main content
Glama

Related Servers

Alternatives to fluig-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to compile AdvPL/TLPP sources, generate and apply patches, and inspect the RPO of TOTVS Protheus servers.
      14
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Exposes over 300 Operaton BPM REST operations as tools for AI agents to interact with the Operaton engine. It enables managing process deployments, instances, user tasks, and decision tables through natural language commands.
      100
      24 npm
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables complete VTEX e-commerce platform integration through natural language, allowing management of catalog, inventory, pricing, promotions, orders, marketplace operations, checkout, customer data, and payment configurations via AI conversations.
      84
      14 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to compile AdvPL/TLPP sources, generate and apply patches, and inspect RPO of TOTVS Protheus servers via the TDS Language Server.
      13
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Bridges AI agents to the Brazilian SEI system, enabling listing processes, reading documents, searching, and downloading files via session cookies.
      2
      -
    • F
      license
      Not graded
      quality
      C
      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
      -

    TDQS

    A3.5/5.0

    Scored across 56 tools

    Disambiguation4/5

    Tools are grouped by domain (dataset, form, process, etc.) and actions are distinct. Some overlap exists between process event reading tools (fluig_process_events_xml vs fluig_workflow_events_get, fluig_process_event_get) but descriptions clarify differences. Overall, agents can reliably distinguish tools.

    Naming Consistency5/5

    All tools follow a strict 'fluig_domain_action' snake_case pattern. Domain and action naming is consistent (list, get, save, delete, etc.). No mixing of styles or unexpected verbs.

    Tool Count3/5

    56 tools is relatively high for an MCP server. While each tool has a distinct purpose, the breadth may overwhelm agents. The scope justifies many tools but the count borders on excessive.

    Completeness5/5

    The tool set provides comprehensive coverage of Fluig's core domains: datasets (CRUD + schema), forms (read, save, metadata), processes (start, move, cancel, history, attachments, versions, export/import, event management), and RM integration. No obvious gaps for typical workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues