Give AI agents full access to ITASCA PFC - documentation, simulation, and plot capture.
io.github.yusong652/pfc MCP Server
This Model Context Protocol (MCP) server provides AI agents “full access” to ITASCA PFC documentation, simulation, and plot capture. It is packaged as the itasca-mcp project, with repository resources including CI status and PyPI distribution badges.
🛠️ Key Features
MCP server for ITASCA PFC
Access to ITASCA PFC documentation
Access to ITASCA PFC simulation
Access to plot capture
🚀 Use Cases
Automating workflows that combine PFC documentation lookup with simulation runs
Capturing plots from PFC results for downstream analysis
⚡ Developer Benefits
Model Context Protocol integration for tool-based agent workflows
Focused scope around PFC: documentation, simulation, and plotting
⚠️ Limitations
Source data does not specify tool names, authentication, or supported platforms beyond the repository/module context
itasca-mcp connects AI agents to ITASCA's geomechanics simulation software — PFC, FLAC, 3DEC, MPoint, and MassFlow — through the Model Context Protocol. Browse documentation, run simulations, and execute code, all through natural conversation.
itasca>model solve ;LLM solves.
itasca-mcp demo
Tools (7)
2 documentation tools — browse by path and search by keywords across the selected engine's commands, Python API, FISH intrinsics, and reference docs. No bridge required.
5 execution tools — interactive REPL, task submission, progress monitoring, interruption, and history. Requires bridge.
Example Prompts
"Run a biaxial compression test on a dense specimen and plot the stress–strain curve"
"Build a slope model in FLAC3D and find the factor of safety"
"Model a tunnel excavation in jointed rock with 3DEC and check block displacements around the opening"
"Simulate a landslide runout with MPoint and report the final deposit profile"
"The simulation is still running, check the current unbalanced force without stopping it"
"Look up the plot commands in the docs, then plot the contact force chains of the current model"
"The command I just typed in the console doesn't seem right, take a look"
First-time Setup
Prerequisites
An ITASCA engine installed — PFC, FLAC, 3DEC, MPoint, or MassFlow. 9.0+ recommended; PFC 6.0 / 7.0, FLAC 7.0, and 3DEC 7.0 are also supported.
2. Start the bridge from inside the ITASCA engine:
Download addon.py, then use either of these two flows inside the engine GUI (PFC, FLAC, 3DEC, ...):
Copy the file contents into the engine's IPython console and run them
Or download the file and execute it in the engine GUI
Verify
Restart your AI agent and ask it to call itasca_execute_code to verify the connection.
Daily Startup
Once first-time setup is done, each new engine session only needs the bridge re-started — run this in the engine's IPython console and you're back online:
start() checks PyPI for a newer bridge release and self-upgrades before starting. The MCP client config persists.
Features
Multi-engine, multi-version corpus - command, Python API, and reference docs for PFC, FLAC, 3DEC, MPoint, and MassFlow across engine versions (PFC: 6.0/7.0/9.0, FLAC: 7.0/9.0, 3DEC: 7.0/9.0), selected via the software and version parameters
Documentation agents can navigate - agents browse the engine command tree to discover capabilities and boundaries, reducing hallucinated commands, with plot item reference docs supplementing the official documentation
Live REPL alongside running tasks - execute code while a simulation is running: check model state and intermediate results without stopping the task; also useful for quick iteration before writing a full script
Task lifecycle management - submit long-running simulations, monitor progress, interrupt running tasks, and browse task history
Sees what you do in the GUI - cells you run in the engine's IPython pane, commands you enter at its prompt, the plots and data files you open, close or switch to, the items you add to a plot, the data files you execute from the editor, and the edits you save to a data file (as a diff) all reach the agent on its next call, and on each call it sees the data files you are still editing, so you can work in the GUI and with the agent at the same time
Works inside your project - the scripts and data files the agent runs appear in the Project pane's Data Files, and a file it changes while you have it open in the editor is reloaded right away
Agent-started bridge - an AI agent can start the bridge itself through the engine's console.exe
Multi-client compatible - works with Claude Code, Codex CLI, Gemini CLI, GitHub Copilot CLI, OpenCode, toyoura-nagisa, and other MCP clients
PRs and issues are welcome! See CONTRIBUTING.md for where changes land and how the
documentation corpus is structured, and the Developer Guide for the
source install.