FEKO MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEKO_HOME | No | Installation release root; otherwise discover via PATH. Accepts the release root containing feko/bin, or the feko directory itself. | |
| FEKO_MCP_BIN_DIR | No | Optional directory containing all three 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 is CPU count; set lower for licence/resource limits. | |
| FEKO_MCP_WORKSPACE | No | Workspace directory for FEKO MCP jobs. Default is .feko-mcp in the current working directory. | .feko-mcp |
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
Most tools have clearly distinct roles across the FEKO workflow, from environment discovery to CAD scripting, solving, post-processing, and result reading. The only mild overlap is between run_cad_script and create_preliminary_model, since both can produce model changes, but the descriptions make their intended use distinguishable.
All tool names use a consistent snake_case verb_noun pattern, such as get_environment, run_cad_script, create_preliminary_model, start_solver, and read_result_text. The verb choices are varied but predictable for the actions they represent.
Nine tools is well-scoped for a FEKO automation workflow. Each tool covers a distinct stage or capability, with no obvious redundancy or unnecessary tool bloat.
The surface covers the core FEKO lifecycle: environment discovery, CAD scripting, model creation, solver start, post-processing, job status, artifact listing, result reading, and API reference. Minor gaps exist, such as no explicit tool to cancel or clean up a running/queued solve, but agents can work around these.