Skip to main content
Glama
SethGame

FlexSim MCP Server

by SethGame
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FLEXSIM_LOG_LEVELNoOverride logging levelINFO
FLEXSIM_CONFIG_PATHNoPath to an alternate config.toml file
FLEXSIM_INSTALL_PATHNoOverride FlexSim program path
FLEXSIM_PYTHON_VERSIONNoOverride Python version for FlexSimPy3.12

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
flexsim_open_modelB

Open a FlexSim model file.

Args:
    model_path: Path to .fsm or .fsx file

Example:
    model_path="C:/Models/warehouse.fsm"
flexsim_resetB

Reset simulation to initial state (time = 0).

flexsim_runB

Start running the simulation continuously.

flexsim_run_to_timeA

Run simulation until reaching target time.

Args:
    target_time: Target simulation time in seconds
    fast_mode: Run at maximum speed (default: True). Set to False for real-time GUI updates.

Example:
    target_time=3600  # Run for 1 hour
flexsim_stopA

Stop the running simulation.

flexsim_get_timeB

Get current simulation time.

flexsim_stepB

Step through simulation events.

Args:
    steps: Number of events to step (1-1000, default: 1)

Example:
    steps=10  # Advance 10 events
flexsim_evaluateB

Execute FlexScript code.

Args:
    script: FlexScript code to evaluate

Examples:
    script='Model.find("Queue1").subnodes.length'  # Get queue content
    script='getmodeltime()'  # Get simulation time
flexsim_get_node_valueC

Get value from FlexSim tree node.

Args:
    node_path: Path to node (e.g., "Model/Queue1/stats/input")
flexsim_set_node_valueB

Set value in FlexSim tree node.

Args:
    node_path: Path to node
    value: New value to set

Example:
    node_path="Model/Processor1/variables/processtime"
    value=5.0
flexsim_save_modelB

Save the current model.

Args:
    save_path: Path to save (optional, uses current if not provided)

Example:
    save_path="C:/Models/warehouse_v2.fsm"
flexsim_new_modelB

Create a new blank model.

flexsim_compileB

Compile the model (check for FlexScript errors).

flexsim_get_statisticsB

Get simulation statistics and performance metrics.

flexsim_export_resultsB

Export simulation results to file.

Args:
    export_path: Path to save results
    format: Export format (csv, xlsx, json)

Example:
    export_path="C:/Results/output.csv"
    format="csv"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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