yade-mcp
Related Servers
Alternatives to yade-mcp
- AlicenseAqualityAmaintenanceMCP server that gives AI agents full access to ITASCA PFC - browse documentation, run simulations, capture plots, all through natural conversation. Built on the Model Context Protocol, pfc-mcp turns any MCP-compatible AI client (Claude Code, Codex CLI, Gemini CLI, OpenCode, toyoura-nagisa, etc.) into a PFC co-pilot that can look up commands, execute scripts, monitor long-running simulations.7225MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceThis project provides a robust integration between AI assistants and FreeCAD CAD software using the Model Context Protocol (MCP). It allows external applications to interact with FreeCAD through a standardized interface, offering multiple connection methods and specialized tools.27MIT
- AlicenseNot gradedqualityAmaintenanceAutomates OpenFOAM CFD simulations via MCP, enabling AI agents to mesh, run, and post-process cases from natural language prompts without any API keys.MIT
- AlicenseBqualityCmaintenanceEnables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization through the MCP protocol.78MIT
- AlicenseAqualityAmaintenanceThe official MCP interface for AgentFEM, giving AI agents seven typed tools to create, validate, run, inspect, and verify finite-element simulations while preserving scientific evidence.737 PyPIApache 2.0
- AlicenseNot gradedqualityCmaintenanceBlenderMCP connects Blender to AI agents via the Model Context Protocol, enabling direct 3D object manipulation, material application, asset downloads, and Python code execution with secure token-authenticated local communication.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate COMSOL Multiphysics simulations, including model management, geometry building, physics configuration, meshing, solving, and results visualization via the MCP protocol.MIT
TDQS
Scored across 7 tools
The task lifecycle tools, synchronous code execution, and API discovery tools are mostly distinct. The only likely point of confusion is yade_execute_task vs yade_execute_code, but their descriptions clearly separate async tracked production runs from synchronous REPL-style use.
All tools use a consistent yade_ prefix with snake_case verb_noun naming: list_tasks, execute_task, check_task_status, interrupt_task, execute_code, browse_api, query_api. The pattern is predictable throughout.
Seven tools is well-scoped for this server: four task-lifecycle tools, one synchronous execution tool, and two API discovery tools. Each tool has a clear role and the set does not feel bloated or thin.
The core surface is covered: async and sync execution, task listing/status/interrupt, and API browsing/search. Minor lifecycle gaps remain, such as no explicit task deletion/cleanup or separate wait/get-task tool, though yade_check_task_status covers output and final status.