Skip to main content
Glama
TutuBarry

ABAQUS MCP Pro

by TutuBarry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ABAQUS MCP Pro

No user-submitted related servers found.

    Related Servers

    • Abaqus-Control-MCP

      pyejy
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like Claude Code or Cursor to control Abaqus/CAE in real time, including running Python scripts, reading ODB results, and capturing viewport screenshots.
      -

    • Codex MCP Abaqus

      Zhangyoupeng1996
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with Abaqus FEA software through an MCP bridge, supporting connection checks, script execution, model queries, job submission, and simulation automation.
      3
      -

    • abaqus-mcp

      yezg9920-kely
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables controlling a live Abaqus/CAE session through natural language, allowing model inspection, job submission, ODB analysis, and viewport capture.
      MIT

    • abaqus-mcp

      Patrick-Miles-Z
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI assistant to drive Abaqus/CAE through file IPC—sending Python commands, querying model info, submiting jobs, and capturing viewport screenshots—so finite element models can be built and solved without manual GUI interaction.
      2
      -

    • 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
    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

    C2.6/5.0

    Scored across 110 tools

    Disambiguation2/5

    The set contains explicit wrappers/duplicates such as run_python/execute_script, inspect_odb/get_odb_info, and capture_viewport/get_viewport_image, plus overlapping tools like check_silent_failures/check_model_integrity and monitor_job_status/diagnose_job. Even with good individual descriptions, an agent will struggle to tell which tool is the intended one.

    Naming Consistency4/5

    Tool names are overwhelmingly snake_case and follow a consistent verb_noun pattern such as create_*, list_*, get_*, set_*, and check_*. Minor deviations like the bare 'ping', compatibility wrapper names, and _exp suffixes keep this from being a perfect 5.

    Tool Count1/5

    110 tools is far beyond the calibrated extreme-mismatch threshold of 50+. The surface includes several near-duplicate and subset tools that should be merged, making the overall tool count excessive for effective agent selection.

    Completeness3/5

    The workflow coverage is broad: parts, materials, meshes, steps, loads, BCs, contacts, job submission, diagnosis, ODB extraction, and reporting are all present. However, nearly every create_* entity lacks corresponding update/delete tools, so iterative correction requires the generic run_python escape hatch rather than a complete structured lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources