GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.bitbybit.dev/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cad": {
"command": "npx",
"args": [
"-y",
"@bitbybit-dev/mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http cad https://mcp.bitbybit.dev/mcpclaude mcp add cad -- npx -y @bitbybit-dev/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cad": {
"url": "https://mcp.bitbybit.dev/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cad": {
"command": "npx",
"args": [
"-y",
"@bitbybit-dev/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"cad": {
"type": "http",
"url": "https://mcp.bitbybit.dev/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"cad": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@bitbybit-dev/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.bitbybit.dev/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 9, 2026. The maker wrote them, not us; we show them as plain text.
search_apiFind 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 pu
describeThe 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 describ
list_namespaceThe 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_examplesWorking 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_guideSections 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),
searchSearches 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.
fetchFetches the full documentation of one Bitbybit API member by id (a dotted path returned by search) as text, with its title, url and metadata.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified against the domain bitbybit.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 157 ms (HTTP 200)
No sign-in needed
Read 7 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.6.1) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server that documents the Bitbybit 3D CAD API for AI coding agents: every function, its parameters, defaults, return type and examples, for the exact version your project uses. Bitbybit has 2205 functions across three CAD kernels - more than any model holds in memory - so an agent working from memory invents plausible names that do not exist. An agent with this server looks each one up instead, and writes code that compiles the first time.
It answers from the API index Bitbybit publishes with every release (https://git-cdn.bitbybit.dev/v /ai-context/index.json), never from memory, and never from a moving "latest".
The diagram shows what an agent is writing code *for*. The MIT-licensed npm packages run the CAD kernels in your users' browsers or in your own Node process; script runners load the same engine from one file; the CAD Cloud REST API runs the work on managed servers. This server knows all of them, and every answer carries a tier - oss, platform-pro or cloud-pro - so an agent never sends you to a paid service for something the free packages already do.
The same server runs two ways. Hosted at https://mcp.bitbybit.dev/mcp over Streamable HTTP, which needs nothing installed and serves the newest release; or locally over stdio with npx, which needs Node 20 and serves the version your project has installed. Start with the remote.
Claude Code
claude mcp add --transport http bitbybit https://mcp.bitbybit.dev/mcp
or the local server:
claude mcp add --transport stdio bitbybit -- npx -y @bitbybit-dev/mcp
For a project, commit a .mcp.json at its root so every collaborator's Claude Code finds it:
{ "mcpServers": { "bitbybit": { "type": "http", "url": "https://mcp.bitbybit.dev/mcp" } } }
Cursor (.cursor/mcp.json)
{ "mcpServers": { "bitbybit": { "url": "https://mcp.bitbybit.dev/mcp" } } }
VS Code (.vscode/mcp.json) - the type is required, or VS Code tries to start the URL as a program:
{ "servers": { "bitbybit": { "type": "http", "url": "https://mcp.bitbybit.dev/mcp" } } }
Either form takes the local server instead: { "command": "npx", "args": ["-y", "@bitbybit-dev/mcp"] }, with "type": "stdio" in VS Code.
Codex
codex mcp add bitbybit --url https://mcp.bitbybit.dev/mcp
or codex mcp add bitbybit -- npx -y @bitbybit-dev/mcp for the local server. In ~/.codex/config.toml that is [mcp_servers.bitbybit] with url = "https://mcp.bitbybit.dev/mcp".
Gemini CLI (gemini mcp add -t http bitbybit https://mcp.bitbybit.dev/mcp), Windsurf (serverUrl in ~/.codeium/windsurf/mcp_config.json), Zed (context_servers in its settings) and the JetBrains IDEs (AI Assistant, MCP, a JSON entry with url) take the same address. claude.ai, ChatGPT and the Claude API connect to the remote as a custom connector - every configuration is documented here.
The server documents one exact version of the API. It picks it in this order:
--version on the command line;BITBYBIT_VERSION= in the environment;@bitbybit-dev packages installed around the working directory (core, then the renderer packages, then occt); packages that disagree are reported on stderr and the first wins;Indexes are cached in $XDG_CACHE_HOME/bitbybit-mcp (or ~/.cache/bitbybit-mcp); --no-cache skips the cache. Everything the program prints goes to stderr; stdout is the protocol.
| Tool | What it answers |
|---|---|
search_api | members by keywords, with path, summary, tier and engines |
describe | the full contract of one member by dotted path, naming the types it returns or takes; such a type by its name, field by field; an unknown path is reported with the nearest existing ones |
list_namespace | the members one level below a namespace |
get_examples | code examples for a member, a namespace or a topic |
get_guide | sections of the public guides: where geometry should run, how to build, check and export parts with the kernels, how to write design documents, and how to write IFC building models |
search, fetch | the same lookups in the shape ChatGPT connectors require |
Every tool is read-only. Tiers in the answers: oss (in the npm packages, MIT), platform-pro (only when scripting inside bitbybit.dev), cloud-pro (only on CAD Cloud, with an API key).
This server answers questions; it never runs geometry. When you want the agent to *produce* geometry - measure a STEP file, run a pipeline, unfold a sheet-metal part, convert to glTF - connect the Bitbybit CAD Cloud MCP alongside it, with a CAD Cloud API key:
claude mcp add --transport http bitbybit-cloud https://api.bitbybit.dev/mcp --header "X-API-Key: <your key>"
In Codex the same is [mcp_servers.bitbybit-cloud] with url = "https://api.bitbybit.dev/mcp" and env_http_headers = { "X-API-Key" = "BITBYBIT_API_KEY" }, the key read from the environment.
The two are designed to work together: the agent learns a member here and calls it there with the same dotted path and the same argument object.
The package exports the tool registry and the index reader, so another server can serve the same tools:
import { createDocsRegistry, contextForIndex, GUIDES, GUIDE_PAGE_URL } from "@bitbybit-dev/mcp";
import { loadIndex } from "@bitbybit-dev/mcp/index-loader"; import { createMcpServer } from "@bitbybit-dev/mcp/server";
const version = " "; const index = await loadIndex({ version }); const context = contextForIndex(index, GUIDES, GUIDE_PAGE_URL); const server = createMcpServer(createDocsRegistry(), context, { name: "bitbybit", version });
toHttp(registry, context) renders the same tools for a plain HTTP endpoint, and guarded(registry, report) is the error boundary every server puts around a registry: a handler that throws answers a generic error result and the throw goes to report, so no internal message reaches a client. Registry.map(wrap) re-wraps every handler for such concerns of your own. The package root imports no Node built-in, so a bundler can take it into an edge runtime; the loader and the version detector, which read the file system, are the separate index-loader and installed-version entries, and the $ref inliner the tool schemas go through is the dependency-free json-schema entry.
The stdio server sends nothing anywhere except one request to the CDN for the index of the version it serves.
| Resource | URL |
|---|---|
| Using AI with Bitbybit | https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/intro |
| This server, documented | https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/mcp/bitbybit-mcp |
| CAD Cloud MCP | https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/mcp/cad-cloud-mcp |
| Agentic CAD - where geometry should run | https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/agentic-cad |
| Context files, for hosts without MCP | https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/prompt-contexts |
| GitHub | https://github.com/bitbybit-dev/bitbybit/tree/master/packages/dev/mcp |
| Monorepo | https://github.com/bitbybit-dev/bitbybit |
| TypeScript API Reference | https://docs.bitbybit.dev |
Beyond NPM packages, Bitbybit offers:
This package is part of the open-source Bitbybit ecosystem. Your subscription helps fund continued development.
⭐ [Subscribe - Silver or Gold plan](https://bitbybit.dev/auth/pick-plan) | [Get API Key for CAD Cloud](https://bitbybit.dev/auth/pick-plan?api-keys=true)
MIT © Bit By Bit Developers