Skip to main content
Glama

Related Servers

Alternatives to itasca-mcp

  • A
    license
    A
    quality
    B
    maintenance
    yade-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.
    7
    86 PyPI
    15
    MIT

Related Servers

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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).

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessUsually handled