pfc-mcp
pfc-mcp is an MCP server that gives AI agents access to ITASCA PFC (Particle Flow Code) for browsing documentation, running simulations, and capturing visualizations through natural conversation.
Documentation Tools (no PFC installation required)
Browse PFC command tree (
pfc_browse_commands): Explore commands by category or get full docs for specific commands (e.g.,ball create)Browse Python SDK reference (
pfc_browse_python_api): Navigate the ITASCA Python API (e.g.,itasca.ball,itasca.ball.Ball.pos)Browse reference documentation (
pfc_browse_reference): Look up contact model properties, range element syntax, and other language elementsSearch PFC commands by keyword (
pfc_query_command): BM25-ranked keyword search across all PFC commandsSearch Python API by keyword (
pfc_query_python_api): BM25-ranked keyword search across the PFC Python SDK
Execution Tools (requires bridge running inside a live PFC process)
Submit scripts for execution (
pfc_execute_task): Asynchronously queue and run Python scripts inside a live PFC sessionMonitor task progress (
pfc_check_task_status): Poll real-time status and output with filtering and paginationList all tasks (
pfc_list_tasks): View tracked tasks across sessionsInterrupt running simulations (
pfc_interrupt_task): Gracefully stop long-runningcycle()calls mid-executionCapture plot images (
pfc_capture_plot): Screenshot PFC visualizations with configurable camera position, ball/wall/contact coloring, cut planes, zoom, and projection type
Works with any MCP-compatible client (Claude Code, Codex CLI, Gemini CLI, etc.). The documentation tools serve as a boundary map to reduce hallucinated commands by letting agents discover PFC capabilities directly.
itasca-mcp
itasca>model new ;now, with LLM.
itasca-mcp connects AI agents to ITASCA's numerical modeling 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.
Related MCP server: mcp-server-terminal
First-time Setup
Prerequisites
An ITASCA engine installed — PFC, FLAC, 3DEC, MPoint, or MassFlow. 9.0+ recommended; PFC 6.0 / 7.0 and FLAC 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.mdManual 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-mcpOr 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
softwareparameterMulti-version support - command docs across engine versions (PFC: 6.0/7.0/9.0, FLAC: 7.0/9.0) via the
versionparameterHierarchical 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 the Developer Guide to get started.
License
MIT - see LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceA simple MCP server for interacting with OpenAI assistants. This server allows other tools (like Claude Desktop) to create and interact with OpenAI assistants through the Model Context Protocol.Last updated939MIT
- Alicense-qualityBmaintenanceMCP server enabling AI agents to interact with terminal applications through structured Terminal State Tree representation. Works with any AI assistant that supports the Model Context Protocol.Last updated6219MIT
- AlicenseAqualityAmaintenanceyade-mcp connects AI agents to YADE — the open-source discrete element method engine — through the Model Context Protocol. Browse API docs, run simulations, and execute code, all through natural conversation.Last updated713MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Discord-based AI agent-user communication. Enables AI agents to communicate with users through Discord instead of IDE chat interfaces.Last updated59MIT
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for AI dialogue using various LLM models via AceDataCloud
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yusong652/itasca-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server