Connects AI agents to YADE for API lookup, live Python execution, and background simulation task control.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Yade MCP.
yade_browse_apiWalk the YADE Python class tree
yade_query_apiBM25 keyword search across the API
yade_execute_codeRun Python in the live YADE process; returns synchronously
yade_execute_taskSubmit a script as a long-running background task
yade_check_task_statusInspect a running or finished task (output, status)
yade_interrupt_taskGracefully stop a running task
The yusong652/yade-mcp MCP server exposes YADE functionality through the Model Context Protocol. YADE is an open-source discrete element method engine used for granular and particle simulation. An MCP-compatible agent can search YADE’s API documentation, execute Python code, submit scripts, inspect task output, and stop active work through separate tools.
The project divides its seven tools into two groups. yade_browse_api and yade_query_api provide documentation access without the bridge. The remaining tools interact with a running YADE process and therefore require the bridge to be active.
API exploration is available through class-tree navigation and BM25 keyword search. These tools can help an agent locate YADE classes and relevant API entries before it writes code.
For interactive work, yade_execute_code sends Python to the live YADE process and returns synchronously. This supports inspecting particles, changing parameters, stepping the engine, and examining variables or object state. It can also be used while a background task is running.
Long-running scripts use yade_execute_task. The task tools let an agent check status and output, list submitted tasks with metadata, and request a graceful interruption. Task records include the submitted script, live output, and final state, allowing a later session to review prior work.
The yusong652/yade-mcp MCP server requires YADE and uv. Register the server in the MCP client with uvx and the yade-mcp package:
Execution features also require installing yade-mcp-bridge with YADE’s own Python interpreter. After restarting YADE, import yade_mcp_bridge in the YADE Python console and call its start() function. The README notes that externally managed Python environments may need the project’s bootstrap guide instead of the basic user-level pip command.
After restarting the MCP client, verify the connection by asking the agent to call yade_execute_code.
The yusong652/yade-mcp MCP server does not provide bridge-backed execution until the bridge is installed and started inside YADE. Documentation browsing and API search are listed as bridge-free, but code execution and task management depend on that connection.
The supplied setup requires YADE to be installed separately; the MCP package does not replace the YADE installation. The README identifies Python 3.10 or newer for the project and documents verification with several command-line and coding agents, while the exact client configuration format may vary between MCP clients.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/yusong652-yade-mcp)<a href="https://allmcps.com/mcp/yusong652-yade-mcp"><img src="https://allmcps.com/api/badge/yusong652-yade-mcp?style=directory" alt="Yade MCP on AllMCPs" /></a>