Skip to main content
Glama
@millwork/solver-mcp

@millwork/solver-mcp

Official
by millworkdev

Related Servers

Alternatives to @millwork/solver-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI agent or MCP client to delegate tasks to an installed WorkBuddy runtime through seven tools, including starting native worker sessions, sending messages, streaming public results, selecting models, loading configured MCP servers and skills, and cancelling tasks.
      7
      76 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an LLM to control Solibri through 25 MCP tools, covering model inspection, rule checking, BCF issue handling, presentations, and Autorun batch verification, all restricted to a local workspace.
      25
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to build and edit native CAD parts and assemblies, inspect saved geometry and measurements, retain revisions, run mechanism and interference checks, and export STEP/STL/GLB artifacts through MCP tools.
      MIT

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools map cleanly to distinct lifecycle stages: source handoff, connection testing, deployment sync, arm registration, execution submission, and proposal review. The main ambiguity is between solver_enable_model_arm and solver_register_arm, which both create arms, and between solver_list_source_connections and solver_list_sources because their names are very close.

    Naming Consistency4/5

    All tool names share the solver_ prefix and consistently use snake_case with clear action/resource stems. Minor inconsistency comes from noun-style names like solver_proposals, solver_status, solver_result, and solver_receipt, which deviate from the verb_noun pattern used elsewhere.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 range, but the count is reasonable for a governed execution platform spanning source connections, credential handoffs, arms, executions, and proposals. There are no obvious redundant or filler tools.

    Completeness3/5

    The core workflow is well covered: connect a source, sync deployments, register arms, submit executions, poll status, fetch results/receipts, and review proposals. However, there are notable lifecycle gaps: no way to list executions, disconnect or delete a source connection, or disable/delete an arm.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues