Bitbybit CAD Cloud MCP

dev.bitbybitPublished by bitbybit.devOfficial publisherv1.6.0Updated Oct 29, 2026

Run 3D CAD operations, pipelines, parametric models and STEP conversions on CAD Cloud with a key

The publisher's own server: Bitbybit CAD MCP

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant run 3D CAD operations, pipelines, parametric models and STEP conversions on Bitbybit CAD Cloud.

What you can do
  • Run 3D CAD operations on the CAD Cloud service
  • Execute pipelines and parametric models
  • Convert models to or from STEP
  • Use whichever CAD Cloud tools the supplied API key is scoped for
When to use it
Useful when you want an assistant to drive 3D CAD work — geometry operations, parametric model runs or STEP conversion — on Bitbybit's hosted CAD Cloud instead of a local CAD tool.
Requirements
A remote streamable HTTP endpoint at api.bitbybit.dev; no local package or runtime. Requires a Bitbybit CAD Cloud account and an API key sent in the X-API-Key header, with scopes covering the tools you intend to use. Network access is needed.
Before you install
The API key is a secret sent in the X-API-Key header; keep it out of logs and shared transcripts. The key's scopes determine which CAD tools are available, so grant only what is needed. Models and geometry data are processed on Bitbybit's cloud service, so consider whether your designs may leave your machine.

Installation

In SourceWeft

  1. Open Bitbybit CAD Cloud MCP in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.bitbybit%2Fcad-cloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bitbybit-cad-cloud": {
      "type": "http",
      "url": "https://api.bitbybit.dev/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

5
  1. v1.6.0LatestOct 29, 2026
  2. v1.5.0Oct 12, 2026
  3. v1.4.1Oct 2, 2026
  4. v1.4.0Sep 30, 2026
  5. v1.3.2Sep 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Bitbybit integrations