Bitbybit CAD MCP

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Bitbybit CAD MCP": {
      "url": "https://mcp.bitbybit.dev/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (7)

• search_api read-only

  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 describe with a path before writing code that uses it.

  Parameters:

  • query (required) — string — Keywords, a phrase, or a partial dotted path
  • limit — integer — How many results, 10 by default
  • engine — string — Only members published for this engine, plus the cloud operations, which run on CAD Cloud rather than in an engine; omit for every engine
  • version — string — The API version to search; omit for the version the server holds

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• describe read-only

  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 member returns or takes by their name, for example Inputs.IFC.SpaceInfoDto, field by field, and a member's answer lists those types. An unknown path is reported as not found together with the nearest existing paths; nothing is guessed.

  Parameters:

  • path (required) — string — The dotted path of the member, for example occt.shapes.solid.createBox, or the name of a type a member returns or takes, for example Inputs.IFC.SpaceInfoDto
  • version — string — The API version to describe; omit for the version the server holds

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_namespace read-only

  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.

  Parameters:

  • path — string — A namespace path such as occt or occt.shapes; omit for the top level
  • version — string — The API version to list; omit for the version the server holds

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_examples read-only

  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.

  Parameters:

  • path — string — A member or namespace path, for example occt.shapes.solid.createBox or occt.fillets
  • limit — integer — How many examples, 5 by default
  • topic — string — Keywords to find examples by, when no path is known
  • engine — string — Prefer members published for this engine when searching by topic
  • version — string — The API version; omit for the version the server holds

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_guide read-only

  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 documents (parametric models as JSON: parameters, sketches, features, references, parts and assemblies), and writing IFC building models (storeys, walls and their joins, doors, windows, slabs, roofs, rooms, properties and quantities). Without a topic it lists the sections. Read "integrate" before recommending where geometry should run: the npm packages are the default, and CAD Cloud is for algorithms that exist only there or compute the caller cannot provide. Read "geometry" before writing geometry code, "design" before writing a design document, and "ifc" before writing an IFC model.

  Parameters:

  • topic — string — A section id or a short name such as integrate, browser, backend, server-side, pro, start, geometry, part-order, geometry-mistakes, design, references, assembly, ifc, ifc-order, ifc-mistakes; omit to list the sections

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• search read-only

  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.

  Parameters:

  • query (required) — string — Search terms

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• fetch read-only

  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.

  Parameters:

  • id (required) — string — A dotted API path returned by search

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.