Xcos MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCILAB_CLI_BIN | No | Path to the scilab-cli executable used for lightweight runtime checks. Set when the executable is not on PATH. | |
| SCILAB_GUI_BIN | No | Path to the full Scilab executable required for Xcos operations. Set when the executable is not on PATH. | |
| XCOS_SERVER_MODE | No | Transport mode for the server. Default is stdio; set to 'http' for streamable HTTP. | stdio |
| XCOS_SERVER_PORT | No | Port for the HTTP server when XCOS_SERVER_MODE=http. | |
| XCOS_ARTIFACT_DIR | No | Directory for generated templates and reference-run artifacts. Defaults to .xcos-mcp/artifacts. | |
| XCOS_ALLOWED_MODEL_ROOTS | No | Platform-separated list of explicit roots for model reads/writes. Defaults to the server working directory and project root. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Check that the MCP process is responsive. |
| get_xcos_runtimeA | Report the discovered Scilab CLI, Xcos-capable GUI, and exact version. |
| list_xcos_blocksC | List block interfaces discovered from the installed Xcos macros. |
| get_xcos_block_sourceC | Read an installed block's Scilab interface source for accurate configuration. |
| create_xcos_block_templateC | Ask real Xcos to export a one-block diagram and return its XML. |
| inspect_xcos_modelC | Inspect a saved Xcos diagram, including blocks, links, and recorded outputs. |
| save_xcos_modelB | Validate basic structure and atomically save Xcos XML inside an allowed root. |
| validate_xcos_modelC | Perform structural checks and import the diagram with real Scilab/Xcos. |
| simulate_xcos_modelC | Run a real diagram for any positive duration and return requested TOWS_c series. |
| simulate_first_order_modelC | Build and simulate G(s)=1/(s+1) in real Xcos, returning its numerical response. |
| analyze_step_responseC | Calculate rise, settling, overshoot, error, and optional control-effort metrics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes, but validate_xcos_model and save_xcos_model both perform structural validation, and simulate_first_order_model overlaps functionally with the generic simulate_xcos_model. Descriptions help disambiguate, but an agent could hesitate between the specific and general simulation tools.
Names follow a snake_case verb_noun pattern consistently, with domain-specific prefixes (get_xcos_runtime, list_xcos_blocks). Minor deviations: ping lacks a verb_noun structure, and some tools omit the xcos prefix (simulate_first_order_model, analyze_step_response).
11 tools is well within the ideal range and each tool appears to earn its place, covering discovery, block inspection, model handling, simulation, and analysis without excessive redundancy.
The set covers environment discovery, block inspection, model validation, saving, and simulation well, but lacks tools to construct or modify arbitrary models (e.g., add blocks, connect links, set parameters). Only a one-block template can be created, which is a notable gap for building general Xcos diagrams.