Skip to main content
Glama
FelipeDiazAimar

FlexSim MCP Server

by FelipeDiazAimar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to FlexSim MCP Server

No user-submitted related servers found.

    Related Servers

    • FEKO MCP

      Zircon04
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-compatible AI clients to control CADFEKO, the FEKO solver, and POSTFEKO by running Lua API scripts, launching asynchronous jobs, monitoring progress, and exporting S11, impedance, Touchstone, model files, and images.
      9
      MIT

    • FlexSim MCP Server

      SethGame
      A
      license
      A
      quality
      D
      maintenance
      Control and automate FlexSim simulations through AI assistants like Claude, enabling manufacturing and warehouse digital twin analysis, parameter studies, and real-time model manipulation via tools for opening models, running simulations, evaluating FlexScript, and exporting results.
      15
      7
      MIT

    • FEKO MCP

      liqtranq
      A
      license
      B
      quality
      C
      maintenance
      Enables an MCP-compatible AI client to control CADFEKO, the FEKO solver, and POSTFEKO by running Lua API scripts, launching asynchronous jobs, tracking progress, and exporting S11, impedance, Touchstone, model files, and images.
      9
      MIT

    • AspenPlus MCP Server

      brack101
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Aspen Plus process simulations through a standardized MCP interface, supporting simulation control, data access, and flowsheet manipulation.
      35
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 73 tools

    Disambiguation2/5

    Many tools overlap in reading statistics (flexsim_get_statistics, flexsim_fluid_level, flexsim_get_performance_measure, flexsim_chart_snapshot), creating objects (flexsim_create_objects, flexsim_create_any, flexsim_person_create, flexsim_dashboard_create, flexsim_collector_create, flexsim_fluid_tank), and connecting objects (flexsim_connect_objects, flexsim_attach_resource, flexsim_agv_connect, flexsim_pf_connect). Despite detailed descriptions and cross-references, the boundaries between tools remain fuzzy, forcing agents to parse experimental notes and backend hints to choose correctly.

    Naming Consistency4/5

    All tool names follow a consistent flexsim_ prefix and snake_case convention with descriptive terms. Minor deviations exist (e.g., verb-first vs. noun-first ordering, abbreviations like pf and agv), but there is no mixing of casing or chaotic naming styles.

    Tool Count1/5

    With 73 tools, the set is far beyond the typical 3-15 range and even exceeds the 50+ threshold for an extreme mismatch. Many tools are experimental, overlapping, or superseded, and do not all earn their place, indicating an overgrown surface for the server's purpose.

    Completeness3/5

    The surface covers many operations (create, connect, run, read statistics, export results), but notable gaps remain: no general delete tool, incomplete ProcessFlow building and chart binding, no verified experiment launching, and several read-only diagnostic stubs. These gaps will cause agents to work around missing functionality.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources