itasca-mcp
Related Servers
Alternatives to itasca-mcp
- AlicenseAqualityBmaintenanceyade-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.786 PyPI15MIT
Related Servers
- AlicenseBqualityDmaintenanceMCP Server for COMSOL Multiphysics simulation automation via AI agents.782MIT
- 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.939MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.24 npm3MIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.103 npm21MIT
- 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.528 PyPI9MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).18 npm3Apache 2.0
TDQS
Scored across 7 tools
Each tool occupies a clearly distinct slot: query_doc (keyword search) vs browse_doc (path traversal), execute_code (synchronous inline) vs execute_task (async script file), and the task trio check_task_status / interrupt_task / list_tasks. The descriptions explicitly contrast the potentially confusable pairs and cross-reference each other for next steps, leaving no room for misselection.
Every tool uses the same itasca_ prefix plus a verb_noun pattern (browse_doc, query_doc, execute_code, execute_task, check_task_status, interrupt_task, list_tasks). The lifecycle tools even share the _task suffix, making the grouping obvious from names alone.
Seven tools is tightly scoped for an engine bridge: two for docs, two for code execution, three for async task lifecycle. Nothing feels redundant and no tool is a trivial wrapper, since each has a separate mechanism (sync/async, poll/interrupt/history).
The surface covers docs lookup, sync and async execution, plus full task lifecycle including status output, interruption, and persisted history — a solid closed loop. Minor gaps remain: there is no dedicated tool to write/upload the script file that execute_task consumes, and no way to wait/join on a task or prune task history, though both are workable via execute_code or polling.