| FMRS | 55 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 11 / 20 | 15 / 20 |
|---|
| Best for | - Geotechnical and geomechanics engineers who already have an ITASCA engine installed and want to drive simulations through an AI agent by natural conversation
- Users who frequently need to look up PFC/FLAC/3DEC/MPoint/MassFlow commands and Python API documentation
- Researchers who submit and monitor long-running simulations while iterating on code
- Technical teams using MCP clients such as Claude Code, Codex CLI, or Gemini CLI
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
|
|---|
| Not for | - Users without any ITASCA engine installed — the execution tools depend on a local engine and bridge and cannot run simulations on their own
- Users expecting official ITASCA support or certification; this is a community project
- Users looking for browser, database, or cloud-storage capabilities rather than geomechanics simulation
- Users wanting a fully zero-configuration experience — first-time setup requires registering the MCP server and starting the bridge in the engine
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| Required permissions | - Run uvx locally and download/execute the itasca-mcp package from PyPI
- Execute code in the ITASCA engine's IPython console to start the bridge (addon.py or itasca_mcp_bridge.start())
- Submit code and simulation tasks to the running ITASCA engine through the bridge and read task state and results
- Network access to PyPI at bridge startup to check for and possibly self-upgrade to a newer release
- Read and write MCP client configuration files to register the server
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| Risks and side effects | - The execution tools run code and simulations in a real ITASCA engine; wrong commands or parameters can produce incorrect results or consume significant compute time and resources
- The bridge automatically checks PyPI and self-upgrades, pulling in updates without per-update user confirmation, which introduces supply-chain risk
- Documentation browsing reduces but cannot fully eliminate hallucinated commands produced by the model
- Long-running simulations, if not properly monitored or interrupted, can tie up machine resources for a long time
- This is a community project rather than an official ITASCA release, so compatibility and maintenance cadence are not guaranteed by the upstream vendor
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | Claude Code, Codex, Gemini CLI, GitHub Copilot CLI, OpenCode | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 1 | 26 |
|---|