M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionITASCA MCP ServerDrive ITASCA geotechnical and geomechanics simulations through natural conversationBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS55 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions9 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2014 / 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
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
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 needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
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 internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
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
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Code, Codex, Gemini CLI, GitHub Copilot CLI, OpenCodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools111