Search / dev.bitbybit/cad
protogridR0· no sign-inBitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide
v1.5.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"cad": {
"type": "http",
"url": "https://mcp.bitbybit.dev/mcp"
}
}
}claude mcp add --transport http cad https://mcp.bitbybit.dev/mcp[mcp_servers.cad]
url = "https://mcp.bitbybit.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cad": {
"type": "remote",
"url": "https://mcp.bitbybit.dev/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"cad": {
"type": "http",
"url": "https://mcp.bitbybit.dev/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=cad&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmJpdGJ5Yml0LmRldi9tY3AifQ%3D%3D"
}{
"servers": {
"cad": {
"type": "http",
"url": "https://mcp.bitbybit.dev/mcp"
}
}
}{
"mcpServers": {
"cad": {
"httpUrl": "https://mcp.bitbybit.dev/mcp"
}
}
}extensions:
"cad":
enabled: true
name: "cad"
type: streamable_http
uri: "https://mcp.bitbybit.dev/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations7 of 7 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 1,563 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes2 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvabledeps.dev does not know @bitbybit-dev/[email protected]get_guidechangedtitle, description, input schema, annotationsSections of the public guide on building with Bitbybit: what runs in the browser, on a server, on a lightweight backend, and what needs CAD Cloud. 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.
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.
describechangeddescription, input schemaThe 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. An unknown path is reported as not found together with the nearest existing paths; nothing is guessed.
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.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-94% +updated-7d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
@bitbybit-dev/[email protected] npmthis version is not known to the dependency resolver
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://mcp.bitbybit.dev/mcp streamable-http | none | yes | 95% | 406 ms | 2026-07-28 | 2026-10-19 |
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
@bitbybit-dev/mcp | npm | 1.5.0 | npx |
describeread-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. |
fetchread-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. |
get_examplesread-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. |
get_guideread-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. |
list_namespaceread-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. |
searchread-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. |
search_apiread-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. |
Schemas: list_tools.
{
"name": "dev.bitbybit/cad",
"icons": [
{
"src": "https://learn.bitbybit.dev/img/favicon-192x192.png",
"sizes": [
"192x192"
],
"mimeType": "image/png"
}
],
"title": "Bitbybit CAD MCP",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://mcp.bitbybit.dev/mcp",
"type": "streamable-http"
}
],
"version": "1.5.0",
"packages": [
{
"version": "1.5.0",
"transport": {
"type": "stdio"
},
"identifier": "@bitbybit-dev/mcp",
"runtimeHint": "npx",
"registryType": "npm",
"registryBaseUrl": "https://registry.npmjs.org"
}
],
"repository": {
"url": "https://github.com/bitbybit-dev/bitbybit",
"source": "github",
"subfolder": "packages/dev/mcp"
},
"websiteUrl": "https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/mcp/bitbybit-mcp",
"description": "Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide"
}