PLAXIS 2D / 3D MCP servers and AI agent skills

How AI connects to PLAXIS 2D / 3D

An MCP server or skill can only do what PLAXIS 2D / 3D lets programs do. PLAXIS 2D / 3D exposes 2 automation interfaces:

• Remote scripting server (plxscripting) (Python): PLAXIS Input and Output each run a local HTTP scripting server, switched on under Expert > Configure remote scripting server. The plxscripting package that ships inside every PLAXIS installation connects to it from Python, by default on port 10000 for Input. Since CONNECT Edition V20 the full command reference is under Help > Scripting reference. Each PLAXIS release ships its own plxscripting version, which is why both MCP servers below ask you to point them at the copy in your own installation. Documentation
• Commands runner and command line (Other): Every action in the PLAXIS user interface is also a text command, so models can be scripted as command sequences. MCP servers usually expose these through a generic "call a command" tool alongside their named tools.

What Bentley (Seequent) offers

Bentley lists official MCP servers for STAAD.Pro and STAAD Foundation Advanced (downloadable), MicroStation (early access) and ProjectWise, iTwin IoT, AssetWise, PLS-CADD and TOWER/PLS-POLE (on request). Its MCP page doesn't mention PLAXIS or any other geotechnical product, so there is no official PLAXIS server as of this check.

Checked 4 Nov 2026. Sources: Bentley MCP servers

What you can do with PLAXIS 2D / 3D and AI

• Build a staged-construction model from a description, such as an embankment on soft clay with initial K0, construction and safety phases, including materials, boreholes, structures and mesh.
• Run calculations and read results back, such as displacements and safety factors per phase, from PLAXIS Output.
• Inspect an existing project by listing its phases, materials and structures before you change it.
• Follow PLAXIS-specific modelling steps and known version quirks through a bundled skill, so the agent doesn't repeat errors such as conflicting undrained settings with K0 procedure phases.

Taken from the listings' own documentation. Check each listing for exactly what it supports.

Installing

The listings here document setup for Claude Code, Codex, Cursor and VS Code (GitHub Copilot). Install steps, copied from each project's own documentation, are on each listing's page. Most PLAXIS 2D / 3D integrations run on your own computer next to PLAXIS 2D / 3D, so you need PLAXIS 2D / 3D installed and licensed on the same machine unless the listing says otherwise.