sketchflow-mcp
Related Servers
Alternatives to sketchflow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables AI hosts to interact with a browser CAD workbench through model-neutral local stdio or authenticated remote MCP tools, supporting command discovery, design-health analysis, and scoped previews while never reading local files or taking over open sessions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.1Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control supported CAD applications through natural-language instructions and unified MCP tools for drawing, layers, blocks, entities, files, and data export.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants like Claude Desktop or Cursor to control supported CAD applications through MCP, supporting drawing, layers, entities, blocks, files, exports, and complex multi-step CAD tasks via direct tool calls or natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables AI clients such as Claude Desktop, Cursor, and Copilot to connect over MCP STDIO to CAD/CAE/CAM tooling for natural-language parametric shape synthesis, CSG script generation, solid watertightness validation, error analysis, and autonomous correction.MIT
TDQS
Scored across 24 tools
The set has a strong conceptual split: unprefixed 2D sketching tools (draw, edit_items, layers, look, export) versus a model_* prefix for the 3D workspace (model_build, model_view, model_export, model_check). A few boundaries blur: board's 'open (id)' action overlaps with the separate open_board tool, 'say' exists both as a standalone tool and as a model_session action, and board.model undo/redo mirrors model_session undo/redo. These are mostly clarified by descriptions, so misselection is unlikely but possible.
A clear, predictable scheme is at work: everything 3D is model_* (model_build, model_describe, model_query, model_mass...), plus open_board/open_model and wait_for_sketch. The 2D side is less uniform, mixing bare nouns/verbs (board, layers, mechanism, export, say, look) with verb_noun forms (edit_items, place_image), but it remains readable and the domain grouping is consistent.
24 tools is on the heavy side, but the server covers two large domains (2D sketching and parametric 3D CAD) plus kinematics, import/export, mass properties, interference checks and add-ons. Heavy front-end action-multiplexing in board, edit_items, model_build and model_session keeps many operations folded into fewer tools, so most entries earn their place.
Lifecycle coverage is broad: create/edit/delete/transform for 2D items, full layer management, drawing-space/guides, image placement, many export formats, and for 3D a full build/describe/query/check/mass/import/export/version/sharing surface. Minor gaps remain, such as no explicit delete or duplicate action for saved boards and no PDF engineering-drawing export.