Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
MCP server for ITASCA geomechanics engines
itasca-mcp connects an agent to ITASCA software through MCP so it can read command and API docs, run code, and manage simulation tasks. The server uses a bridge started inside the engine, and the agent can then query docs, submit work, watch progress, interrupt tasks, and inspect history.

Builders who want their agent to work with PFC, FLAC, 3DEC, MPoint, or MassFlow from Claude Code, Codex, Gemini CLI, or another MCP client.
You can run and inspect geomechanics simulations with your agent instead of switching between docs, scripts, and the engine UI.
What it does
Multi-engine documentation search
Browse command docs, Python API docs, and reference docs for PFC, FLAC, 3DEC, MPoint, and MassFlow.
Version-aware command docs
Switch between engine versions with the `version` parameter for supported PFC, FLAC, and 3DEC releases.
Hierarchical doc navigation
Move through command trees so the agent can find valid commands and avoid inventing ones.
Live REPL execution
Run code while a simulation is still active to inspect model state or test quick changes.
Task lifecycle tools
Submit long-running jobs, monitor progress, interrupt them, and review task history.
Agent bootstrap guide
Use the agentic setup guide in `docs/agentic/itasca-mcp-bootstrap.md` to self-configure a client.
How to get it
- 1Copy this to your AI agent and let it self-configure
Fetch and follow this bootstrap guide end-to-end: https://raw.githubusercontent.com/yusong652/itasca-mcp/main/docs/agentic/itasca-mcp-bootstrap.md
- 2Most agents register it with a single command
# Claude Code claude mcp add itasca-mcp -- uvx itasca-mcp # Codex / Codex-cli codex mcp add itasca-mcp -- uvx itasca-mcp # Gemini CLI gemini mcp add itasca-mcp uvx itasca-mcp
README
itasca-mcp
itasca>model new ;now, with LLM.
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.

Tools (10)
5 documentation tools — browse and search the selected engine's commands, Python API, 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"
- "What's different about the
zonecommands between FLAC 7.0 and 9.0?"
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.
- uv installed (for
uvx) - An AI agent — Claude Code, Codex CLI, Gemini CLI, or any MCP-capable client
Agentic Setup (Recommended)
Copy this to your AI agent and let it self-configure:
Fetch and follow this bootstrap guide end-to-end:
https://raw.githubusercontent.com/yusong652/itasca-mcp/main/docs/agentic/itasca-mcp-bootstrap.md
Manual Setup
1. Register the MCP server with your agent.
Most agents register it with a single command:
# Claude Code
claude mcp add itasca-mcp -- uvx itasca-mcp
# Codex / Codex-cli
codex mcp add itasca-mcp -- uvx itasca-mcp
# Gemini CLI
gemini mcp add itasca-mcp uvx itasca-mcp
Or fill in the MCP config file manually:
{
"mcpServers": {
"itasca-mcp": {
"command": "uvx",
"args": ["itasca-mcp"]
}
}
}
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:
import itasca_mcp_bridge
itasca_mcp_bridge.start()
start() checks PyPI for a newer bridge release and self-upgrades before starting. The MCP client config persists.
Features
- Multi-engine corpus - command, Python API, and reference docs for PFC, FLAC, 3DEC, MPoint, and MassFlow, selected via the required
softwareparameter - Multi-version support - command docs across engine versions (PFC: 6.0/7.0/9.0, FLAC: 7.0/9.0, 3DEC: 7.0/9.0) via the
versionparameter - Hierarchical documentation browsing - agents navigate the engine command tree to discover capabilities and boundaries, reducing hallucinated commands
- Enhanced plot documentation - plot items 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
- Multi-client compatible - works with Claude Code, Codex CLI, Gemini CLI, GitHub Copilot CLI, OpenCode, toyoura-nagisa, and other MCP clients
Troubleshooting
See Troubleshooting in the bootstrap guide.
Development
See Developer Guide: Install and Run from Source.
Contributing
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.
License
MIT - see LICENSE.
Files in the repo
- .github
- docker
- docs
- scripts
- src
- tests
- workspace
- .dockerignore
- .gitignore
- .gitmodules
- addon.py
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- CONTRIBUTING.md
- CONTRIBUTING.zh-CN.md
- GEMINI.md
- itasca-mcp-bridge
- LICENSE
- pyproject.toml
- README.md
- README.zh-CN.md
- server.json
- uv.lock
- WARP.md
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.
Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.