cad-mcp-server
This is a local, read-only MCP server for inspecting and measuring STEP CAD geometry with Open CASCADE.
Inspect a STEP file for bounding-box dimensions, volume, surface area, assembly/body structure, B-rep health, and a revision-bound reference.
Find faces, edges, vertices, and bodies with filters by surface/curve type, radius, area, length, and component scope; results are paginated.
Measure distance, wall thickness, draft, ray casts/ray grids, point analysis, planar sections, and edge continuity.
Read declared PMI/GD&T: dimensions, geometric tolerances, datums, and applicable entity IDs, including checking some dimensional callouts against geometry.
Compare two STEP revisions for geometry deltas, PMI counts, and parsed document metadata.
Return values in the file’s declared units and bind results to entity IDs and SHA-256 revisions; it runs locally and does not require CAD software.
Works with the STEP files exported from FreeCAD (as well as SolidWorks, Fusion 360, CATIA, or any other CAD system), inspecting and measuring 3D model geometry locally with deterministic OCCT-backed results.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cad-mcp-server What are the overall dimensions and volume?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ottogeo — CAD MCP Server
Give any AI assistant the ability to measure real CAD geometry. The server opens STEP files with the Open CASCADE kernel and answers the questions an engineer actually asks — overall size and volume, hole and boss diameters, wall thickness, clearance, draft, cross-sections, and what changed between two revisions — with numbers computed from the model's own B-rep, not estimated from a screenshot.

Quick start
Add the server to your MCP client, then point your assistant at a STEP file:
{
"mcpServers": {
"cad": {
"command": "npx",
"args": ["-y", "cad-mcp-server"]
}
}
}Works with any MCP client — Claude Desktop, Cursor, VS Code, and the rest.
Related MCP server: CadKitty
Ask it anything about a part
"What are the overall dimensions and volume of this part?"
"Find the cylindrical faces and list their diameters and axes."
"Measure wall thickness on these faces."
"What is the minimum distance between this hole and the nearest wall?"
"Measure draft relative to the +Z direction and list faces with negative draft."
"Cut a section through this body at X = 40."
"What changed between revision A and revision B?"
More examples, including DFM-style review prompts, are in docs/EXAMPLE_PROMPTS.md.
Tools
Tool | Returns |
| Bounding-box dimensions, volume, surface area, body and assembly structure, B-rep health, and a revision-bound reference. |
| Faces, edges, vertices, and bodies, with filters for surface type, radius, axis, and area. |
| Distance between faces, wall thickness, draft, ray casts, ray grids, point analysis, planar sections, and edge continuity. |
| Declared dimensions (nominal with deviations or bounds), geometric tolerances (value, zone, material modifier, datums), and datums, each with the entity IDs it applies to. |
| Dimension, volume, area, and topology deltas between two STEP revisions, declared PMI counts, and parsed STEP metadata. |
Measurement kinds are distance, thickness, draft, ray, ray_grid,
point_analysis, section, and continuity. Lengths come back in the file's
declared unit, labelled on every result, so an inch model stays in inches and
nothing has to be converted by hand. Angles are in degrees.
Why the numbers hold up
Computed by Open CASCADE, not guessed. The same file and the same query return the same numbers, every time.
Revision-bound and self-verifying. Every result carries the entity IDs and the SHA-256 revision it came from, and stale IDs are rejected when a file changes underneath a session — so an answer can never be attached to the wrong geometry.
Reads the model's own callouts.
describe_pmireports the dimensions, geometric tolerances, and datums a file declares, each bound to the entities it applies to, so declared requirements can be checked against the geometry.Local and private. It runs over stdio and reads files by path. It is read-only and never uploads or writes your CAD data.
Requirements
Node.js 26+
Windows x64, macOS ARM64 (Apple Silicon), or Linux x64
STEP files, as exported by SolidWorks, Fusion 360, Onshape, FreeCAD, CATIA, or any other CAD system
FAQ
Does it need CAD software installed? No. It reads STEP files directly, so it works on a machine without a CAD application or license.
Do my files leave my machine? No. The server runs locally over stdio and reads files by path. It is read-only and never writes to your CAD data.
How is this different from asking an assistant to look at a screenshot? Measurements are computed from the model's B-rep geometry by Open CASCADE, so the same file and query return the same numbers. Each result also carries the entity IDs and revision it came from.
Development
Source setup, checks, packaging, and releases are in docs/DEVELOPMENT.md. The server targets Windows x64, macOS ARM64, and Linux x64, and builds its native sidecar from the pinned OCCT revision.
Packaging
npm pack builds first and includes the compiled server, the native sidecar, this
README, and the third-party notices. Tests and source maps are excluded. Install
the tarball to check the cad-mcp-server executable with a compatible MCP client.
Documentation
Architecture — tools, workflow, and limits
Security — local processing and handling CAD files as sensitive input
License
MIT. Third-party licenses: THIRD_PARTY_NOTICES.md.
Available Tools
5 toolsdescribe_pmiDescribe Model PMI and GD&TARead-onlyIdempotent
Report the dimensions, geometric tolerances, and datums that a STEP artifact declares, as data: nominal, deviations, and tolerance form for each dimension; value, zone shape, material requirement, and datum references for each geometric tolerance; and the entity IDs each annotation applies to. characteristics checks each dimensional callout against the faces it controls, and reports satisfied or violated where that is arithmetic — a diameter read from the cylindrical faces the callout names — and unresolved with a reason everywhere else, so a callout that was not checked cannot be mistaken for one that was. Check value_resolved before comparing anything yourself. It is false when the magnitude could not be read and is reported as 0.0, which is what a genuine zero callout also reports; a location dimension defining a tolerance frame has no value of its own. A basic dimension comes back not-applicable: it defines a tolerance frame and states no limit of its own. An angle or a location callout comes back unresolved with needs-frame, because the angle between two faces and a location dimension direction both depend on the frame the callout is stated in. A datum reference carries the entity IDs of the shapes its datum is attached to. Without them a tolerance naming that datum cannot be evaluated, so report the datum as unlocated rather than treating the tolerance as met. unlocated_datums names those references for you; a tolerance that carries it is not checkable, and saying which datum is missing is the useful answer.Counts report both datum references and distinct datums, because a frame names its references one by one and the same datum appears once per frame. Values are in the declared unit, the same unit this server uses for measurements. Read pmi_kind before describing what a file does or does not declare: semantic means the callouts are readable data; graphical-only means the file does show requirements, drawn rather than encoded, so say they must come from the drawing or the engineer instead of saying the model declares none; none means it declares nothing at all. Use the artifact reference from inspect; entity IDs are valid only for that revision.
Inputs: uri (required), include. Returns: units, counts, datums, artifact, +7 more
diffCompare Step VersionsARead-onlyIdempotent
Compare baseline and candidate STEP artifacts, as filesystem paths or file: URIs. Returns both content revisions, geometry deltas in the baseline declared unit, declared PMI counts (dimensions, geometric tolerances, datums, and how many tolerance values could not be read), and parsed document facts: schema, product names/count, assembly flag, authoring system, and organization. The PMI counts show whether a revision added or dropped callouts; they compare how many callouts exist, not whether any is met. These are file-level facts; they do not explain design intent.
Inputs: baseline (required), candidate (required). Returns: pmi, units, deltas, inputs, +3 more
find_entitiesFind Model EntitiesARead-onlyIdempotent
Find faces, edges, vertices, or solid bodies in the revision-bound artifact returned by inspect, optionally scoped to an assembly component_name. Use this before measure, because every measurement names entity IDs rather than coordinates, and follow pagination until has_more is false whenever a count or a minimum matters. Faces support surface_type, area, and radius filters (e.g. { surface_type: "cylinder", min_radius: 2 }); edges support curve_type, length, and radius; vertices return coordinates and bodies return volume. IDs are producer- and revision-scoped: they are valid only for this server and only for the artifact revision that returned them, so never reuse them after the file changes or in another tool. Occurrence IDs distinguish repeated component instances. distance takes sources/targets; every other measure kind takes entity_ids, and cad://help lists the required fields for each kind.
Inputs: artifact (required), entity_type (required), limit, offset, +10 more. Returns: query, units, artifact, entities, +5 more
inspectInspect Model OverviewARead-onlyIdempotent
Inspect a local STEP artifact by filesystem path or file: URI. Returns its content revision with dimensions, counts, and B-rep validity. Call this first; use the returned artifact reference for entity searches and measurements. Lengths are in the declared unit, which is labelled on every result. Bounding boxes are conservative envelopes, and volume is null when the file has no solid material. Use include to request only size, counts, and/or health sections.
Inputs: uri (required), include. Returns: size, health, artifact, structure, +1 more
measureMeasure GeometryARead-onlyIdempotent
Measure distance, wall thickness, draft, rays/ray grids, point geometry, planar sections, or edge continuity. Use the artifact reference and entity IDs from the same find_entities result. Lengths are in the declared unit, which is labelled on every result. Ray grids report their grid size and can be refined with max_rays up to 20000. Fetch the cad://help resource for the required fields of each kind. Returns geometric measurements only, not engineering acceptance or design recommendations.
Inputs: kind (required), artifact (required), checks, detail, +18 more. Returns: kind, units, artifact, subjects, +2 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
The five tools form a clear pipeline (inspect → find_entities → measure/describe_pmi → diff), and descriptions explicitly state ordering and dependencies. Minor overlap remains: inspect reports dimensions/counts and describe_pmi also reports dimensions, and vertex coordinates/body volume come back from find_entities while measure covers point geometry, which could cause a misselection in edge cases.
All names are lowercase snake_case with verb-led phrasing and no style mixing. Two tools use verb_noun (find_entities, describe_pmi) while three are bare verbs (inspect, measure, diff), a minor deviation that stays readable and predictable.
Five tools is tightly scoped to the domain: load, query entities, measure, read PMI, and compare revisions. Each tool covers a distinct stage of the workflow with no redundant members.
The surface covers the core lifecycle of STEP inspection: artifact intake, entity discovery, geometry measurement, PMI interpretation, and revision diffing, including scoping by assembly component and pagination. Gaps are minor, such as no export/conversion or assembly-tree browsing as a standalone operation, though component_name scoping partly compensates.
Maintenance
Related MCP Connectors
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
Parametric 3D CAD for AI agents: build print-ready parts, check them, export STL, 3MF or STEP.
Read, query, edit and render DWG drawings with AI. No AutoCAD required.
Text-to-CAD: build exact STEP or 3MF/STL on the server, each stated requirement measured.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables an AI assistant to open 3D model files (STL, 3MF, Bambu Studio and OrcaSlicer projects) in a local browser viewer where the user clicks exact spots to leave feedback. Each note comes back with the part name, millimetre coordinates, surface direction and a numbered screenshot, so the assistant can revise the design and show the new version.2MIT
- 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 gradedqualityCmaintenanceEnables AI agents to drive desktop CAD software through natural language with verified execution, failure recovery, and traceable results across modeling, assemblies, drawings, exports, motion, FEA, and related engineering workflows.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect and convert STL/OBJ meshes into clean prismatic STEP solids with real planes, cylinders, and holes, plus sliced lofts, X-Ray outlines, and drawing-to-parametric CAD workflows locally.404 PyPI11PolyForm Noncommercial 1.0.0