Skip to main content
Glama
liqtranq

FEKO MCP

by liqtranq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to FEKO MCP

No user-submitted related servers found.

    Related Servers

    • Ansys Workbench MCP

      Chen-Xin-Yuan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.
      2
      MIT

    • FEFLOW MCP Server

      Followmyself
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control FEFLOW 7.5 groundwater simulation software through MCP, supporting model loading, mesh operations, parameter management, and result export.
      -

    • ABAQUS MCP Pro

      TutuBarry
      A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to control and automate Abaqus/CAE simulations via MCP, including model query, job management, ODB inspection, KPI extraction, capsule tracking, physics contract validation, report generation, and viewport capture. It also supports noGUI batch mode, dual transport, and integration with Codex/Claude clients.
      110
      4
      MIT

    • COMSOL MCP Server

      HBPEKING-TKS
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization through the MCP protocol.
      78
      MIT

    • Mechanical MCP Server

      codersag
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      19
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources