FEKO MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEKO_HOME | No | Installation release root containing feko/bin, or the feko directory itself; otherwise discover via PATH. | |
| FEKO_MCP_BIN_DIR | No | Optional directory containing all three FEKO executables. | |
| FEKO_MCP_API_DOCS | No | Optional path to the local documentation appendix directory. | |
| FEKO_MCP_MAX_CORES | No | Maximum number of CPU cores to use. Default: CPU count; set lower for licence/resource limits. | |
| FEKO_MCP_WORKSPACE | No | Writable job directory. Default: .feko-mcp in the current working directory. |
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 |
|---|---|
| get_environmentC | Locate FEKO components, the supplied model and its documented assumptions. |
| run_cad_scriptB | Run CADFEKO Lua asynchronously in a new job directory; provide Lua/text assets by filename. |
| create_preliminary_modelC | Build a fresh parameterised copy of the antenna example. Overrides are in mm/Hz and SI material units. |
| start_solverA | Start FEKO in a completed CAD job. Return immediately, then poll get_job_status. |
| run_post_scriptB | Run POSTFEKO Lua in a solved job. An empty script uses the tested S11/impedance exporter. |
| get_job_statusB | Read persistent stage status and recent FEKO diagnostics without blocking a long solve. |
| get_artifactsC | List model, result, table and preview files produced by the job. |
| read_result_textC | Read exported CSV, Touchstone, notes or diagnostics for analysis in the assistant. |
| read_apiC | Read installed CADFEKO/POSTFEKO 2026.1 API, e.g. application=cadfeko, relative_path=object/rectangle.htm. |
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 9 tools
Each tool maps to a distinct stage of the FEKO workflow (environment, CAD scripting, model creation, solving, status, artifacts, results, API docs). The only mild overlap is between create_preliminary_model and run_cad_script, both of which produce CAD models, but their descriptions draw a clear line between a canned parameterised example and arbitrary Lua execution.
All nine tools follow a clean verb_noun convention (get_environment, run_cad_script, create_preliminary_model, start_solver, get_job_status, read_result_text, etc.). No mixing of camelCase or vague verb styles.
Nine tools is well-scoped for a simulation pipeline covering discovery, model building, solve, monitoring, and result extraction. Each tool earns its place with no filler.
The surface covers the full lifecycle from environment discovery to reading results and API reference, with polling-based status for async solves. Minor gaps like job cancellation/cleanup or solver configuration tweaking exist but are workaroundable via Lua scripts.