ClassCAD

What ClassCAD MCP server does

The ClassCAD MCP server connects agent hosts to the ClassCAD engine for creating and checking parametric CAD models. Its repository is organized around four related pieces: a skill package that documents the CAD API, a script package that executes model programs, a renderer for visual output, and an MCP package that exposes the workflow to agent hosts.

The engine supports both parts and assemblies. The documented API contains 264 methods across parts, assemblies, sketches, common operations, curves, solids, and 2D drawings. Six recipes show how individual operations can be combined, while a semantic search function handles CAD terminology such as treating a hole as a bore or a round as a fillet.

How it works

An agent can use the ClassCAD MCP server to request model operations from a local ClassCAD process. Model construction is expressed as a script: the repository example creates a plate, adds an 80 by 50 by 10 box, calculates mass properties, and returns a volume result of 40,000.

The workflow also supports verification. Numerical results include computed properties such as volume and mass properties, while the renderer produces views of the resulting geometry. The repository illustrates rendered engineering views for a flanged bushing, including section, left, plan, and projection views. This makes the ClassCAD MCP server relevant when a result needs more than generated geometry alone.

The MCP layer is intended to work through one daemon per machine and can receive requests from supported agent hosts. The repository also describes an in-app assistant and a relay package for joining a session from another location, but the provided material does not specify the relay protocol or deployment commands.

Setup and configuration

The repository provides the relevant packages under these names:

• @classcad/skill for the documented API and search capability
• @classcad/script for executable CAD scripts
• @classcad/renderer for generated views
• @classcad/mcp for the MCP server
• @buerli.io/ai for the in-app agent integration
• @classcad/relay for shared sessions

The available description says the engine runs locally and that the MCP layer uses a daemon per machine. It does not provide installation commands, startup arguments, transport details, configuration files, or required environment variables. Consult the repository for those operational details before deployment.

Tools and capabilities

The ClassCAD MCP server is suited to workflows that need to:

• Create parametric parts and assemblies.
• Work with parts, assemblies, sketches, curves, solids, and 2D drawings.
• Search the CAD API using domain terminology and synonyms.
• Execute model scripts.
• Calculate mass properties and volume.
• Render model views for visual inspection.
• Send requests from Claude Code, Codex, Claude Desktop, VS Code, or Cursor.

Limitations and notes

The supplied material documents capabilities and package roles, but not the complete MCP tool schema. It does not list individual MCP tool names, authentication settings, supported operating systems, installation steps, or environment variables. The repository describes local execution and an optional relay, so users should verify the intended deployment model and client configuration in the source before relying on remote access.