Koskamo

Bitbybit CAD Cloud MCP MCP server

An official MCP server provided by Bitbybit that allows AI agents to execute 3D CAD operations on the Bitbybit CAD Cloud platform. It enables agents to perform tasks such as calculating volume, mass, surface area, and center of mass, as well as converting file formats like STEP to glTF, slicing models for 3D printing, and generating parametric variants. The server handles geometry processing and file conversions via API keys, returning results as download links without requiring local hosting.

Endpoint and access

API key: create a key with the vendor first; your client sends it as an authorization header on every request.

API keyEndpoint checked 2026-10-05Operated by Bitbybit
MCP endpoint (Streamable HTTP)
https://api.bitbybit.dev/mcp
Vendor documentation

What you can do with it

  • Calculate volume, mass, and surface area of 3D parts
  • Convert STEP files to glTF for web visualization
  • Slice models for 3D printing or flatten sheet metal
  • Generate parametric variants of gears or other components

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http bitbybit-cad-cloud-mcp https://api.bitbybit.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add bitbybit-cad-cloud-mcp --url https://api.bitbybit.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable bitbybit-cad-cloud-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "bitbybit-cad-cloud-mcp": {
      "url": "https://api.bitbybit.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "bitbybit-cad-cloud-mcp": {
      "type": "streamableHttp",
      "url": "https://api.bitbybit.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start bitbybit-cad-cloud-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "bitbybit-cad-cloud-mcp": {
      "type": "http",
      "url": "https://api.bitbybit.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http bitbybit-cad-cloud-mcp https://api.bitbybit.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "bitbybit-cad-cloud-mcp": {
      "url": "https://api.bitbybit.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "bitbybit-cad-cloud-mcp": {
      "serverUrl": "https://api.bitbybit.dev/mcp"
    }
  }
}

Do you run Bitbybit CAD Cloud MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing