ParaShape documentation
ParaShape is an open format and engine for parametric 3D models. A model is a JSON document: named parameters, objects built from chains of geometry steps, and expressions that tie them together. A kernel written in Rust and compiled to WebAssembly evaluates the document, in the browser and in Node, with the same code and therefore the same result.
The schema, the engine and the MCP server for agents are open source in the repository. These pages are the front door for two audiences: developers who build on the format or the engine, and CAD and product professionals who describe products as parametric definitions.
What is in the system
| Part | What it is | Where |
|---|---|---|
| Schema | The persisted model JSON, defined once as Rust serde structs; the TypeScript types are generated from them. | crates/model/src/document |
| Engine | The evaluator and every operation on a model: geometry, validation, expressions, edits, history, export. Compiled to wasm and committed. | crates/, packages/model/wasm |
| Client | A thin TypeScript mirror of the engine: EngineClient for the doors, ModelView for a reflected document. No geometry runs in JavaScript. | packages/model |
| MCP server | A stdio server through which an agent loads, edits, measures and renders a model on the in-process engine. | packages/mcp |
| Builder | The browser editor for definitions. | /builder |
| Hub | Public models you can configure in the browser and download as GLB, STL or OBJ. | /models/ |
| SketchUp plugin | Places library models into a SketchUp model and edits their parameters in place. | Download page |
The model, in one paragraph
A document lists root parameters (a width, a count, a finish) and objects. An object is a chain of steps: a producer such as a rectangle or a circle, then transforms such as an extrusion or a boolean. Every argument is an expression that may read parameters, so changing a parameter re-evaluates only what depends on it. Objects are placed by instance properties (translate, rotate, scale, copies, material, visibility) and may cut each other through behaviors. A document can place other published documents as components. Units are millimetres and Z is up.
The SketchUp plugin and the hub
The plugin is a host for the same engine and the same builder. A library panel lists public models by product line and places the pick at the click point; an edit panel changes the parameters of the selected instance and the geometry updates in place. Placing a library model needs no account. The plugin is downloaded from its page.
The hub at /models/ lists every public model. A model page is a viewer of the same document: value-only parameters, a description, and downloads as GLB, STL and OBJ.
Properties of the design
- One pure pull graph: no network, clock or randomness in evaluation, so one document always yields one result.
- The kernel is the whole engine. JavaScript mirrors a door's result and never computes geometry, validates or evaluates an expression.
- Every mesh is a closed solid, enforced where meshes are born, so volume, section and boolean results are well defined.
- The catalog is the single source for method and argument names, types and defaults; the catalog reference is generated from it.
- No compatibility layer: a shape is current or it is gone, and an unknown key fails validation.
Where to go next
- Getting started: run the engine from Node, author a first model, connect an agent through the MCP server.
- Model JSON: the document shape and the node law.
- Parameters and expressions: values, domains and the expression language.
- Objects and components: objects, properties, behaviors, components, materials, layers, patterns and views.
- Catalog reference: every node and expression function, generated from the engine.
- Engine API: the wasm doors,
EngineClient,ModelViewand theChangescontract. - Laws for contributors: the rules a change must respect.