Bitbybit MCP server

Which servers in the official MCP registry are Bitbybit's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Bitbybit

Whose server it is

Registry namedev.bitbybit/cadverified in the MCP registry

The registry name sits under bitbybit.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools7
Server calls itselfbitbybit
Server version1.5.0
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 279 ms.

Tools it offers7 tools · read 2026-10-14

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Also shipped through: npm

Other servers listed as Bitbybit's

dev.bitbybit/cad-cloudanswers, requires sign-inverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.