FDTD Lumerical MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FDTD_WORKSPACE | No | Override the default workspace directory for FDTD projects. | |
| LUMERICAL_API_PATH | No | Path to the lumapi.py file from an Ansys/Lumerical installation, used if automatic discovery fails. |
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 |
|---|---|
| fdtd_startC | Start a local Ansys Lumerical FDTD GUI session. |
| fdtd_closeA | Close the active FDTD session. |
| fdtd_statusA | Return FDTD MCP session status. |
| project_newA | Create a new blank FDTD project in the active session. |
| project_loadA | Load an .fsp project from FDTD_WORKSPACE. |
| project_saveC | Save the active FDTD project under FDTD_WORKSPACE. |
| script_evalC | Evaluate Lumerical script code in the active FDTD session. |
| script_run_fileC | Run a Lumerical script file from FDTD_WORKSPACE. |
| object_addC | Create an FDTD object with a Lumerical add* command. |
| object_setC | Set properties on a named FDTD object. |
| object_getC | Read selected properties from a named FDTD object. |
| object_deleteC | Delete a named FDTD object. |
| fdtd_runB | Run the active FDTD simulation. |
| result_getC | Read a result dataset from a named FDTD object. |
| data_exportC | Export data to FDTD_WORKSPACE, optionally using a Lumerical script. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| session_status_resource | |
| workspace_files_resource |
TDQS
Scored across 15 tools
Each tool targets a distinct operation: session management (fdtd_*), project CRUD (project_*), object CRUD (object_*), simulation running, result retrieval, script execution, and data export. No two tools have overlapping purposes.
All tools follow a consistent <resource>_<verb> pattern in snake_case (e.g., object_add, project_load, fdtd_close). No mixing of conventions.
15 tools is well-scoped for an FDTD simulation server, covering session, project, object, simulation, results, scripting, and data export without bloat.
Covers CRUD for projects and objects, simulation lifecycle, results, scripting, and export. Missing is a tool to list all objects in a project, which is a minor gap.