Chamfer
Related Servers
Alternatives to Chamfer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for AI-driven CAD operations, enabling parametric modeling, build, inspection, measurement, rendering, and diff comparison with STEP, DXF, and GLB export.MIT
- AlicenseBqualityDmaintenanceMCP server that lets AI draw in AutoLISP-capable CAD (reference BricsCAD on Linux) via a file bridge, enabling 2D drafting, 3D solid modeling, and verification with 100 tools.1283Apache 2.0
- AlicenseAqualityCmaintenanceModern CAD CLI + MCP Server: 2D/3D drawing, editing, measurement, validation, batch automation, real-time collaboration (CRDT + WebSocket).222Apache 2.0
- FlicenseAqualityBmaintenanceCAD-engineering MCP tool server for parametric modeling, DFM validation, mechanical calculations, and more. Enables code-CAD builds (build123d/CadQuery), model inspection, meshing, and mechanical calculators via MCP stdio.11-
- AlicenseAqualityBmaintenanceEnables MCP clients to inspect and measure native B-rep geometry, create and edit CAD models, export results, and optionally review models or prepare print jobs locally.111MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to automate 2D architectural drafting and CAD file management, including DXF/DWG parsing, SVG/PNG/PDF rendering, wall extrusion to 3D STL meshes, room and beam analysis, block/script library access, and persistent depot storage via a REST API and MCP tools.18MIT
TDQS
Scored across 8 tools
Most tools have clear distinct roles across drafting, modification, linting, import/export, CAM reporting, and 3D extrusion. However, chamfer_execute is a broad catch-all that includes editing operations overlapping with chamfer_modify_entity, and verification appears in get_drawing, execute, and lint, creating some potential misselection.
All tool names use a consistent chamfer_ prefix and snake_case formatting. The pattern is mostly verb_noun, but a few names deviate as bare verbs (execute, lint) or noun phrases (cam_report), preventing a perfect score.
Eight tools are well-scoped for a 2D CAD/CAM server, covering state access, command execution, entity modification, validation, DXF I/O, manufacturing telemetry, and 3D extrusion. Each tool has a clear reason to exist without excessive granularity.
The surface covers the full lifecycle: read state, execute drawing commands, modify entities, import/export DXF, lint geometry and manufacturing issues, compute CAM metrics, and extrude to 3D. No obvious gaps remain for the stated CAD/CAM domain.