Skip to main content
Glama
Bettertoo2

ANSYS MCP Server

by Bettertoo2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ANSYS MCP Server

No user-submitted related servers found.

    Related Servers

    • icepak-mcp

      NedaEmami123
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with ANSYS Icepak through natural language commands, supporting geometry import, material assignment, thermal loads, meshing, solving, and result retrieval.
      -

    • 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.
      17
      Apache 2.0

    • openfoam-mcp

      kimlnw
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns an AI assistant into an OpenFOAM setup and debugging co-pilot, enabling case scaffolding, dictionary edits, mesh sizing, turbulence calculations, and solver log analysis through natural language.
      MIT

    • discovery

      ahmet-hoca-official
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create parametric geometry, apply loads, run simulations, and read results in Ansys Discovery through natural-language commands over gRPC.
      1
      MIT
    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.1/5.0

    Scored across 41 tools

    Disambiguation4/5

    Domain prefixes (geometry_, mechanical_, fluent_) clearly separate tools, and within each domain actions like apply_load, solve, and get_result are distinct. The only potential overlap is between geometry_import_file and mechanical_import, but their descriptions clarify the active model.

    Naming Consistency4/5

    Tool names follow a domain_verb_noun snake_case pattern, which is predictable. However, retrieval verbs vary ('list', 'get', 'read') and lifecycle verbs differ ('close' for geometry, 'exit' for mechanical/fluent), creating minor inconsistency.

    Tool Count2/5

    With 41 tools, the server exceeds the 25+ threshold for 'too many' and may overwhelm agents. While the broad scope (Geometry, Mechanical, Fluent) justifies some size, the count is still heavy and would benefit from consolidation.

    Completeness4/5

    Core workflows are covered: geometry creation/import/export, mechanical setup/solve/result, and fluent setup/solve/save. Minor gaps exist, such as no geometry editing/deletion and limited result types, but these are workable for typical simulation tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources