mech-cad-design-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MECH_DESIGN_WORKSPACE | Yes | Path to the mech-cad-design workspace, created via 'mech-cad-design init'. | |
| MECH_DESIGN_DATABASE_URL | No | Optional PostgreSQL connection string to use for durable knowledge storage instead of the default local SQLite database. | |
| MECH_DESIGN_MCP_TOOL_PROFILE | No | MCP tool surface to expose. Default is 'design'. Set to 'knowledge-admin' for knowledge administration tools. | design |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| design_system_statusB | Inspect local design, FreeCAD, knowledge, and provider readiness. |
| design_startC | Start or resume a design after natural-language direction approval. |
| design_statusC | Read current model, validation, confirmation, and lesson state. |
| design_listA | List every design job in the workspace with its current state. |
| design_knowledge_retrieveC | Retrieve applicable knowledge without making retrieval a CAD gate. |
| design_record_resultB | Bind the exact FCStd hash to passed JSON, Markdown, and PNG evidence. |
| design_mistakesC | Report validation defects this design corrected or still carries. |
| design_gear_sizeA | Size a spur gear drive: ratio, teeth, module, forces, stresses, shaft, bearings. Preliminary sizing evidence, not a strength certification. See the result's limitations for what is not evaluated. |
| design_confirmC | Confirm the model, evaluate lessons, or revise its pending review. |
| design_lesson_decideC | Approve all or selected review-card lessons, or decline publication. |
| standard_part_providers_getC | List standard-part sources in configured trust order. |
| standard_part_sources_statusB | Inspect the configured standard-part catalog binding. |
| standard_part_download_registerC | Register a validated downloaded standard part with full provenance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct action or resource: readiness checks, lifecycle management, knowledge retrieval, evidence recording, gear sizing, and standard-part management are clearly separated. Even closely related tools like design_confirm and design_lesson_decide have non-overlapping responsibilities (model confirmation vs. lesson publication).
All tools follow a consistent domain prefix (design_ or standard_part_), but the suffix pattern mixes verb-first (design_start, design_confirm) with noun-first (design_status, design_mistakes) forms. The readability is high and the prefix convention provides strong predictability, so the minor deviations are not confusing.
13 tools is well within the ideal 3-15 range and matches the server's broad but focused scope—covering design workflow, knowledge, validation, and standard-part integration. Each tool offers a distinct function and none feel redundant or extraneous.
The tool surface covers the core design lifecycle (start, status, list, confirm, record, mistakes) and standard-part management (providers, sources, register). Minor gaps exist, such as no explicit design update/delete or a standard-part search/download tool, but the existing tools allow agents to work around these via design_start/confirm and the provider/source inspection tools.