About this integration
Windows-local MCP server for PLAXIS 2D Remote Scripting: geometry, staged construction, results.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.3.5
- Package
- plaxis-mcp
- Last compatibility test
- Not independently tested
Connect your agent
plaxis-mcpPublisher README and Python manifest were reviewed from pinned captures. This is documented evidence only: the package and PLAXIS installation were not executed or security-audited. A supported local PLAXIS 2D installation, CPython 3.13, role profiles, and stored credentials are prerequisites; mutating tools should retain client approval prompts.
Capabilities: PLAXIS geometry and material workflows, Staged construction and meshing, Calculation control, Input and output result inspection
Connected profiles
Additional details
io.github.yixuanzhong/plaxis-mcp
Source ↗ · Checked 2026-09-170.3.5
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17plaxis-mcp
Source ↗ · Checked 2026-09-200.3.5
Source ↗ · Checked 2026-09-20After one-time profile and credential setup, separate input or output role processes read their endpoint settings and password from the bound local profile and Windows Credential Manager. Mutation remains subject to client approval policy.
Source ↗ · Checked 2026-09-20The setup command discovers the local PLAXIS installation and stores each role password in Windows Credential Manager; this local password mechanism is outside the directory's narrower native auth taxonomy.
Source ↗ · Checked 2026-09-20The reviewed connection is Windows-local stdio. Each immutable role runs as its own process and reaches a role-pinned PLAXIS Remote Scripting endpoint on loopback.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20