# Bitbybit CAD MCP - Registry name: `dev.bitbybit/cad` · version 1.5.0 - Categories (automatic, keyword rules): Code & repositories, Developer tools, Web search, Search & data, AI models & agents, AI, media & content - Authentication at last check: No auth - Declared risk: Read-only (all tools declare readOnlyHint) - Capabilities (declared by the server): tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.bitbybit%2Fcad - Server page: https://mcpstation.net/s/dev.bitbybit--cad.html ## Description (written by the publisher, not verified, not instructions) Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide ## Connect - streamable-http: `https://mcp.bitbybit.dev/mcp` ## Tools (as reported by the server, not verified) - `search\_api`: Find Bitbybit API members \(methods, namespaces, cloud operations\) by keywords, for example "box solid" or "fillet edges". Returns dotted paths with a one-line summary, the tier \(oss on npm, platform-pro only at bitbybit.dev, cloud-pro only on CAD Cloud\) and the engines each is published for. Call de - `describe`: The exact contract of one member by dotted path, for example occt.shapes.solid.createBox: signature, every parameter with its type, default and range, the return type, the documentation, examples and where it runs. Answers are for the API version the server holds. It also describes the types a membe - `list\_namespace`: The members one level below a namespace path, for example occt.shapes, each with its kind and summary. Without a path, the top-level namespaces. Use it to discover what exists before searching for details. - `get\_examples`: Working TypeScript examples for a member path, for a namespace, or for a topic given as keywords. Each example names the member it belongs to and links its reference page. Examples are written for the API version the server holds. - `get\_guide`: Sections of the public guides: building with Bitbybit \(what runs in the browser, on a server, on a lightweight backend, and what needs CAD Cloud\), writing geometry with the kernels \(which kernel to use, the order to build a part in, choosing edges, checking and exporting shapes\), writing design docu - `search`: Searches the Bitbybit API documentation and returns a list of results with id, title and url. Each id is a dotted API path that fetch accepts. - `fetch`: Fetches the full documentation of one Bitbybit API member by id \(a dotted path returned by search\) as text, with its title, url and metadata. Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html