Skip to content
Agentmart
Submit a tool

ITASCA MCP Server

MCP server for ITASCA PFC, FLAC3D, 3DEC, MPoint and MassFlow: search docs, run simulations, plot.

Connector by yusong652 · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 219
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/yusong652-itasca-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

MCP server for ITASCA PFC, FLAC3D, 3DEC, MPoint and MassFlow: search docs, run simulations, plot.

Use cases: data-analysis, code-generation

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
7 read · 1 write · 1 delete · 1 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 10

Read from the source code; the running server may list different tools.

Read 7 · Look things up without changing anything.

  • itasca_browse_commands
  • itasca_browse_python_api
  • itasca_browse_reference
  • itasca_check_task_status
  • itasca_list_tasks
  • itasca_query_command
  • itasca_query_python_api

Write 1 · Create, change, send or run things.

  • itasca_execute_task

Delete 1 · Delete, drop, revoke or wipe things.

  • itasca_execute_code

Not yet classified 1 · We could not tell from the name and description.

  • itasca_interrupt_task

Tools (10)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • itasca_browse_commands

    Browse Itasca command documentation by path (like glob + cat). Navigation levels: - No command: All command categories overview - Category only (e.g., "ball"): List commands in category - Full command (e.g., "ball create"): Full documentation When to use: - You know the command category or exact command - You want to explore available commands Related tools: - itasca_query_command: Search commands by keywords (when path unknown) - itasca_browse_reference: Browse reference docs (e.g., "contact-models linear")

  • itasca_browse_python_api

    Browse Itasca Python SDK documentation by path (like glob + cat).

  • itasca_browse_reference

    Browse ITASCA reference documentation (syntax elements, model properties). Works across engines via the required ``software`` selector (pfc/flac/3dec). References are language elements used within commands, not standalone commands. Navigation levels: - No topic: All reference categories for the engine - Category (e.g., "constitutive-models"): List items in category - Full path (e.g., "constitutive-models mohr-coulomb"): Full documentation - Sub-item path (e.g., "plot-items zone contour"): Sub-item details When to use: - Need material/contact/joint model property names (kn, ks, fric, cohesio…

  • itasca_check_task_status

    Check status and paginated output for a submitted Itasca task. Output combines Python prints and Itasca console output from itasca.command() calls (table dumps, list output, command summaries) interleaved in execution order. Use skip_newest / limit to paginate, or filter to keep only matching lines.

  • itasca_execute_code

    Execute Python code synchronously in the running Itasca engine process. Returns stdout and an optional result variable immediately. Code runs in the engine's main thread, sharing the same __main__ namespace as any running task — side effects persist and are immediately visible to the task on its next cycle. The tool stays responsive while a task submitted via itasca_execute_task is cycling (calls interleave at cycle gaps), so use it as a live REPL — nothing has to be pre-scripted into the task up front. Typical uses: - Query model state and read Itasca command output: itasca.command('ball …

  • itasca_execute_task

    Submit a Python script file for asynchronous execution in the Itasca engine. Returns a task_id immediately; the script runs in the background. Companion tools manage the lifecycle: - itasca_check_task_status: poll output, progress, and final status - itasca_interrupt_task: cancel a running task - itasca_list_tasks: browse task history For synchronous, inline execution, use itasca_execute_code instead. While the task is cycling, itasca_execute_code shares the same __main__ namespace in the engine's main thread, so you can inspect or modify simulation state live — probe progress, tune paramete…

  • itasca_interrupt_task

    Request interruption of a pending or running Itasca task. Returns as soon as the request is accepted; it does not wait for the task to stop. Confirm the stop and read the output produced so far with itasca_check_task_status. Only the script stops; the engine state is preserved, so you can inspect it with itasca_execute_code or continue from it with a new itasca_execute_task. Tasks already completed, failed or interrupted return an error. If the task_id is unknown, find it with itasca_list_tasks.

  • itasca_list_tasks

    List tasks tracked by the bridge, newest first. Read-only. Each entry carries task_id, status (pending / running / completed / failed / interrupted), description, entry_script, start_time, end_time and elapsed_time; total_count gives the size of the full history for paging via skip_newest + limit. Task history is persisted in the engine working directory and survives GUI restarts. Use this to recover a task_id from an earlier session, to see what is running or recently finished, or as a cheap bridge-connectivity check. For a task's output and result use itasca_check_task_status; to submit a …

  • itasca_query_command

    Search Itasca command documentation by keywords (like grep). Returns matching command paths. Use itasca_browse_commands for full documentation. When to use: - You have keywords but don't know exact command path - Example: "ball create", "contact property", "model solve" Related tools: - itasca_browse_commands: Get full documentation for a known command path - itasca_browse_reference: Browse reference docs (e.g., "contact-models linear") - itasca_query_python_api: Search Python SDK by keywords

  • itasca_query_python_api

    Search Itasca Python SDK documentation by keywords (like grep). Returns matching API paths with signatures. Use itasca_browse_python_api for full documentation. When to use: - You have keywords but don't know exact API path - Example: "ball velocity", "create", "contact force" Related tools: - itasca_browse_python_api: Get full documentation for a known API path - itasca_query_command: Search Itasca commands by keywords

Signals

Stars
219
Forks
19
Open issues
1
Contributors
4
Weekly downloads
5,820
Last commit
Oct 22, 2026 (5 days ago)
Last release
Oct 22, 2026 (5 days ago)
Last package publish
Oct 22, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.yusong652/itasca-mcp
Version
0.10.5
Auth
No auth
Packages
pypi itasca-mcp
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from yusong652

Cite this page

ITASCA MCP Server. Agent Mart. https://agentmart.dev/connectors/yusong652-itasca-mcp (last updated 2026-10-24)