FeatureBoardby Lewis Valentine

NativeCAD for Software Teams: A CAD Kernel You npm install

If your product has to reason about a real part, you need a CAD kernel. NativeCAD is one you npm install: pure JavaScript, real B-rep, STEP in and out, running in your process with no per-call bill.

You are building a quoting bot, a configurator, a design-review agent or a generative loop. At some point it has to open a customer's STEP file, measure it, change it and write it back. That used to mean licensing a C++ kernel and building a geometry team, or calling a hosted API and paying per request. NativeCAD is a solid modelling kernel you npm install. It runs in your process: in Node, in the browser, and inside the agent.

A folded L-bracket with four holes
An L-bracket from the text-to-CAD prompt set.

What software teams build on NativeCAD

  • Instant-quote and DFM tools that read the customer's file and return findings with geometry.
  • Product configurators that emit a real STEP file for every option set.
  • AI design agents that call CAD tools over MCP and get refusals they can act on.
  • Browser viewers and editors that never upload the model.
  • Their own MCP servers, certified against the kernel.

A dependency, not a service

The AI-native kernel page states the design: the CAD kernel is a dependency of your product, not a service your product calls. It is pure JavaScript with zero runtime dependencies. No WASM, no native module, no Python sidecar, no build toolchain, which is also why an agent can install it for itself. Your customers' geometry never leaves your infrastructure, and your bill does not grow with your traffic.

0
runtime dependencies
200
MCP tools an agent can call
94.2%
of 86 text-to-CAD prompts accepted

From install to a watertight solid in under a second

Time to first boolean measures the whole path from npm install to a watertight boolean solid: well under a second on a stock Node install with no toolchain. The page publishes the script, so you can run the same measurement on your own machine before you commit to anything.

An API reference generated from the shipped types

The SDK API reference covers the two packages you build on, export by export, 147 exports in all, with the signatures the TypeScript compiler hands your editor. It is generated from the type declarations that ship in each package, so it cannot drift from what you install. The MCP tool reference does the same for the agent surface: 200 tools, each with the input schema the server validates against, units and bounds included.

Built for agents: scored prompts and named refusals

The text-to-CAD scorecard runs 86 prompts across 25 sectors, each with an acceptance block the finished solid has to satisfy: watertight, a volume band, a bounding box and a DFM verdict. 94.2% are accepted (81 of 86), at a mean of 3.8 tool calls per part. When the kernel cannot do something it refuses by name with an error code, which is what lets an agent recover instead of shipping a wrong part. A Wrong Answer That Looked Right 98 Times explains why that matters.

A registry of certified MCP servers

If you ship your own MCP server on the kernel, the certified MCP registry lists servers that passed the fixed conformance suite over their own stdio: primitives, boolean volume identity, a blend, a STEP round trip that has to come back watertight, a refusal vocabulary and a tool-schema lint. Each entry carries the hash of a signed conformance manifest anyone can verify offline.

Real files in, real files out

The kernel reads STEP, IGES, Parasolid, SolidWorks parts, SAT, 3MF and meshes, and writes STEP AP242. On export, 150 of 150 STEP files were read exactly by an independent CAD kernel. For display it writes glTF and GLB in one call.

One price for embedding

The Kernel SDK is $9,995 per year: one self-serve price for embedding, with no developer count to declare and no per-product ladder. Licence validation is fully offline. Details are on the pricing page. For background on what you are embedding, read What a CAD Kernel Is Actually Made Of.

Questions software teams ask

Is there a JavaScript CAD kernel that runs in Node and the browser?

Yes. NativeCAD is a pure JavaScript B-rep kernel with zero runtime dependencies. It runs in Node and in the browser with no WASM and no native module, and reads and writes STEP.

How do I give an AI agent CAD tools?

Install the NativeCAD MCP server. It exposes 200 tools with validated input schemas, units and bounds, and it refuses by name with an error code when an operation cannot be done.

What does it cost to embed NativeCAD in a product?

The NativeCAD Kernel SDK is $9,995 per year, one self-serve price with no developer count and no per-product ladder.

What does NativeCAD cost?

A NativeCAD MCP / Modeler seat is $200 per seat per year, or $20 per seat per month, with no metered usage. The evaluation needs no key and no sign-up; export, save and import need a seat key. See pricing.

Does my geometry leave my computer?

NativeCAD runs on your own machine: the kernel and solvers run locally and licence validation is fully offline. Files opened in the browser modeler are never uploaded. Your AI assistant sees what you ask it to work on, under your agreement with its provider.

NativeCAD in other industries


NativeCAD is CAD, FEA and CFD software your AI assistant drives over MCP, from Claude, Cursor or your own agent, and in the browser. Every part is an exact B-rep solid that exports as STEP AP242. See what it does, browse every demo, check pricing, or install it.

← Previous Post
NativeCAD for Architects and BIM Teams: Ask, Check and Edit IFC Models With an AI Assistant
Next Post →
NativeCAD for Reverse Engineering and Inspection: Scans, STL Files and Old Drawings Back to Solids