# Bitbybit CAD MCP (remote · mcp.bitbybit.dev)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.bitbybit.dev`: 72/100 (this document), [markdown](https://verifymcp.io/servers/dev-bitbybit-cad/mcp.md), [page](https://verifymcp.io/servers/dev-bitbybit-cad/mcp)
- npm · `@bitbybit-dev/mcp`: 49/100, [markdown](https://verifymcp.io/servers/dev-bitbybit-cad/bitbybit-dev-mcp.md), [page](https://verifymcp.io/servers/dev-bitbybit-cad/bitbybit-dev-mcp)

## Channel facts

- Endpoint: `https://mcp.bitbybit.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 931 tokens (~133/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Bitbybit CAD MCP server?

Bitbybit CAD MCP is a hosted endpoint at https://mcp.bitbybit.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-bitbybit-cad 'https://mcp.bitbybit.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-bitbybit-cad": {
      "url": "https://mcp.bitbybit.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-bitbybit-cad": {
      "type": "http",
      "url": "https://mcp.bitbybit.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-bitbybit-cad]
url = "https://mcp.bitbybit.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-bitbybit-cad": {
      "type": "remote",
      "url": "https://mcp.bitbybit.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-bitbybit-cad --url 'https://mcp.bitbybit.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-bitbybit-cad:
    url: "https://mcp.bitbybit.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-bitbybit-cad": {
      "Transport": "http",
      "Url": "https://mcp.bitbybit.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-bitbybit-cad -t streamable-http -u 'https://mcp.bitbybit.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-bitbybit-cad": {
      "type": "http",
      "url": "https://mcp.bitbybit.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 72)

First indexed and scored.

## MCP tools (7)

### `search_api` (~175 tokens)

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

Input parameters:

- `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
- `limit` (integer): How many results, 10 by default
- `query` (string, required): Keywords, a phrase, or a partial dotted path
- `version` (string): The API version to search; omit for the version the server holds

### `describe` (~126 tokens)

Describe an API member

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. An unknown path is reported as not found together with the nearest existing paths; nothing is guessed.

Input parameters:

- `path` (string, required): The dotted path of the member, for example occt.shapes.solid.createBox
- `version` (string): The API version to describe; omit for the version the server holds

### `list_namespace` (~96 tokens)

List a 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.

Input 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

### `get_examples` (~151 tokens)

Get code 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.

Input parameters:

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

### `get_guide` (~120 tokens)

Read the integration guide

Sections 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.

Input parameters:

- `topic` (string): A section id or a short name such as integrate, browser, backend, server-side, pro, start; omit to list the sections

### `search` (~47 tokens)

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.

Input parameters:

- `query` (string, required): Search terms

### `fetch` (~54 tokens)

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.

Input parameters:

- `id` (string, required): A dotted API path returned by search

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-bitbybit-cad/mcp#diagnostics

## Score history

- 2026-09-20: 72

## Common questions

### What is the Bitbybit CAD MCP server?

Bitbybit CAD MCP is listed in the public MCP registry as dev.bitbybit/cad. Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide. This page covers its hosted endpoint (https://mcp.bitbybit.dev/mcp).

### Is the Bitbybit CAD MCP server safe to use?

Bitbybit CAD MCP scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Bitbybit CAD MCP server expose?

Bitbybit CAD MCP exposes 7 tools: search_api, describe, list_namespace, get_examples, get_guide, and 2 more. Their descriptions and schemas cost roughly 769 tokens of context every time the server is loaded.

### Does the Bitbybit CAD MCP server require authentication?

No. We connected to Bitbybit CAD MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Bitbybit CAD MCP server still maintained?

Bitbybit CAD MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.bitbybit.dev/mcp
- Repository: https://github.com/bitbybit-dev/bitbybit
- Website: https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/mcp/bitbybit-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-bitbybit-cad/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-bitbybit-cad/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-bitbybit-cad/mcp