FEKO MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FEKO MCP Build a centre-fed dipole at 2.4 GHz, solve it, and export S11."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FEKO MCP
Control CADFEKO → FEKO solver → POSTFEKO from an MCP-compatible AI client. This local stdio server runs Lua API scripts, launches asynchronous jobs, reads progress, and exports S11, impedance, Touchstone, model files, and images.
Tested with Windows, Altair FEKO 2026.1, Python 3.11+. Other FEKO versions and operating systems have not been validated. You need your own FEKO installation and suitable licence; neither is included. This is an independent community integration, not an official Altair product.
Install
git clone https://github.com/liqtranq/feko-mcp.git
cd feko-mcp
py -3 -m venv .venv
.\.venv\Scripts\python.exe -m pip install .
$env:FEKO_HOME = 'C:\Program Files\Altair\2026.1'
$env:FEKO_MCP_WORKSPACE = "$PWD\jobs"
.\.venv\Scripts\feko-mcp.exe doctorSet paths to your installation and a writable job directory. FEKO_HOME
accepts the release root containing feko/bin, or the feko directory itself.
If the programs are on PATH, the installation can be discovered. The example
path may differ on your computer. doctor checks program paths; FEKO checks
licence availability when a job runs.
Related MCP server: ansys-aedt-mcp
Connect an AI client
Start the stdio server with feko-mcp, or python -m feko_mcp. Use absolute
paths in the client. Shell environment variables are not automatically inherited
by an already-running desktop app: put them in the MCP configuration.
For Codex, add to config.toml, replacing paths:
[mcp_servers.feko]
command = 'C:\path\to\feko-mcp\.venv\Scripts\python.exe'
args = ['-m', 'feko_mcp']
startup_timeout_sec = 20
[mcp_servers.feko.env]
FEKO_HOME = 'C:\Program Files\Altair\2026.1'
FEKO_MCP_WORKSPACE = 'C:\path\to\feko-jobs'Restart the MCP connection after saving. See OpenAI's MCP configuration
documentation. Clients using
mcpServers JSON can use mcp-config.example.json.
This server needs no OpenAI API key.
Tools and workflow
Tool | Purpose |
| Check programs, workspace, and example assumptions |
| Read/search installed CADFEKO/POSTFEKO Lua API documentation |
| Run a Lua build with optional text assets in a new job |
| Build the included antenna with parameter overrides |
| Start a solver job and return immediately |
| Read stage state and log tails |
| Run custom POSTFEKO Lua or the supplied exporter |
| List output paths and sizes |
| Read exported tables, notes, or diagnostics |
Check get_environment; build a model; poll until build completes; call
start_solver; wait for solve; call run_post_script; read the exports.
Keep the returned job_id. Use the filename produced by your build script.
Process startup does not mean calculation success: check stage state, exit
code, and FEKO diagnostics. job_id="example" reads the bundled model notes,
not precomputed results. Build a new job to obtain results.
Sample prompt:
Use the FEKO tools to build a centre-fed dipole at 2.4 GHz. Read the installed API first, solve on one core, check status, and export S11 referenced to 50 ohm. Report solver errors and output paths.
Jobs live in <workspace>/jobs/<job_id>. Workers continue after MCP requests
return. There is no built-in cancellation: inspect worker status/PID before
managing a process manually. No network listener is opened. Lua runs with the
local user's permissions: use trusted scripts and clients; this is not a
sandbox for untrusted code.
Example without an AI client
.\.venv\Scripts\feko-mcp.exe example build --smoke
.\.venv\Scripts\feko-mcp.exe example solve --smoke --cores 1
.\.venv\Scripts\feko-mcp.exe example post --smokeThe smoke example runs at 2.4 GHz. Omit --smoke from all three commands
for 1–10 GHz. Outputs live in <workspace>/example. Edit its parameters.lua
before rebuilding to change geometry or frequency sampling.
The antenna is a preliminary reconstruction with assumptions, not a validated design. Read the model notes. Source PDFs, figures, calculated result binaries, and vendor files are omitted.
Configuration
Variable | Default / meaning |
| Installation release root; otherwise discover via PATH |
| Optional directory containing all three executables |
|
|
| Optional path to the local documentation |
| CPU count; set lower for licence/resource limits |
read_api accepts e.g. application="cadfeko",
relative_path="object/rectangle.htm". It reads local docs, not the internet.
If CADFEKO reports that it cannot open its user settings, check the client's
execution permissions: FEKO also needs access to its own configuration and
licensing files outside the job directory. A missing documentation directory
can be configured separately with FEKO_MCP_API_DOCS.
Development and verification
.\.venv\Scripts\python.exe -m pip install -e .
.\.venv\Scripts\python.exe -m unittest discover -s tests -v
# Requires FEKO and a licence; runs a small native dipole:
.\.venv\Scripts\python.exe -m feko_mcp.verify_nativeCI checks configuration, input validation, worker outcomes, and stdio tools without FEKO. It does not verify electromagnetic accuracy. Native verification is opt-in and creates a new job. Report FEKO/Python/OS versions and a minimal script in issues. See CONTRIBUTING.md.
MIT licence covers the bridge code. Altair software and third-party source material retain their own licences and are not redistributed.
Available Tools
9 toolscreate_preliminary_modelC
Build a fresh parameterised copy of the antenna example. Overrides are in mm/Hz and SI material units.
Inputs: parameters.
get_artifactsC
List model, result, table and preview files produced by the job.
Inputs: job_id.
get_environmentC
Locate FEKO components, the supplied model and its documented assumptions.
Inputs: no named parameters.
get_job_statusB
Read persistent stage status and recent FEKO diagnostics without blocking a long solve.
Inputs: job_id (required).
read_apiC
Read installed CADFEKO/POSTFEKO 2026.1 API, e.g. application=cadfeko, relative_path=object/rectangle.htm.
Inputs: application (required), relative_path (required), search_term. Returns: result
read_result_textC
Read exported CSV, Touchstone, notes or diagnostics for analysis in the assistant.
Inputs: job_id (required), filename (required), max_chars. Returns: result
run_cad_scriptB
Run CADFEKO Lua asynchronously in a new job directory; provide Lua/text assets by filename.
Inputs: script_text (required), assets.
run_post_scriptB
Run POSTFEKO Lua in a solved job. An empty script uses the tested S11/impedance exporter.
Inputs: job_id (required), model_base, script_text.
start_solverA
Start FEKO in a completed CAD job. Return immediately, then poll get_job_status.
Inputs: job_id (required), cores, model_filename.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
MCP server for AI access to Swagger by SmartBear.
MCP server exposing the Backtest360 engine API as tools for AI agents.
Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization through the MCP protocol.78MIT
- AlicenseCqualityDmaintenanceEnables AI agents to control Ansys Electronics Desktop (HFSS, Maxwell, Q3D, etc.) using MCP tools for simulation automation.10063PolyForm Noncommercial 1.0.0
- AlicenseBqualityCmaintenanceEnables natural language interaction with ANSYS Mechanical simulation software via gRPC, allowing users to manage geometry, mesh, boundary conditions, solve analyses, and generate reports through MCP-compatible AI clients.3720Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to control FEFLOW 7.5 groundwater simulation software through MCP, supporting model loading, mesh operations, parameter management, and result export.-