Skip to main content

For AI Coding Agents, and the People Driving Them

You let Claude Code, Codex, Cursor, VS Code, claude.ai, ChatGPT or an agent of your own write the 3D code, or produce the geometry outright. Bitbybit treats that agent as a first-class user: the API is published in the form it can read at the moment it needs it.

Give the agent the API​

Connect the free Bitbybit CAD MCP. In Claude Code that is one command:

claude mcp add --transport http bitbybit https://mcp.bitbybit.dev/mcp

From then on the agent describes every function it is about to call: the exact parameters, defaults and examples of the version your project has installed. Assistants that cannot speak MCP get the same knowledge from a context file.

Let the agent run geometry​

When the agent has to produce a file or an answer rather than code, connect the Bitbybit CAD Cloud MCP with an API key from a CAD Cloud plan. It runs operations, pipelines, parametric models and STEP conversions on CAD Cloud and returns download links. "What is the volume of this STEP file?" becomes an upload and a two-step pipeline, with no backend of yours.

Know where geometry should run​

Read Agentic CAD once. The open-source packages are the complete answer wherever public code and your users' compute are acceptable; CAD Cloud is for the Pro algorithms that exist only there and for compute you cannot provide. The agent reads the same page through the docs server, so its advice matches ours.

Start a project the agent can iterate on​

npm init @bitbybit-dev/app my-project

The scaffolder gives you a working app on the packages for three.js, Babylon.js or PlayCanvas; point the agent at the MCP server and ask for changes.