Skip to main content
Glama
SethGame

FlexSim MCP Server

by SethGame
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to FlexSim MCP Server

No user-submitted related servers found.

    Related Servers

    • RSAP MCP

      nhantruong96
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude to control Autodesk Robot Structural Analysis Professional via COM API for modeling, loads, analysis, and results retrieval.
      35
      MIT

    • opm-mcp

      ojaogezi
      A
      license
      B
      quality
      B
      maintenance
      Provides Claude with direct access to the Open Porous Media (OPM) reservoir simulation stack, enabling running simulations, inspecting results, and automating workflows via natural language.
      40
      4
      MIT

    • COMSOL MCP

      Twofruitsgrape
      A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to read and write .mph model files, control the COMSOL desktop GUI in real time, and run complete modeling, meshing, solving, and post-processing workflows.
      23
      1
      MIT

    • digital-twin

      squall321
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language control of a digital twin simulation pipeline for phone drop tests, converting LS-DYNA .k meshes to solid .k files with hand grip poses using 7 MCP tools.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. For example, flexsim_run starts continuous simulation, flexsim_run_to_time runs to a specific time, and flexsim_step advances by events, while flexsim_compile checks for errors versus flexsim_evaluates executes code. The descriptions clearly differentiate each tool's function.

    Naming Consistency5/5

    All tools follow a consistent 'flexsim_verb' or 'flexsim_verb_noun' pattern with snake_case throughout. Examples include flexsim_open_model, flexsim_get_time, and flexsim_set_node_value, making them predictable and readable.

    Tool Count5/5

    With 15 tools, the set is well-scoped for a FlexSim simulation server, covering essential operations like model management, simulation control, data access, and result export. Each tool earns its place without being overwhelming or insufficient.

    Completeness5/5

    The tool surface provides complete coverage for the FlexSim domain, including model creation, opening, saving, simulation control (run, stop, reset, step), time and statistics retrieval, node value manipulation, code evaluation, and result export. There are no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources