Developer Tools

bitbybit.dev

MCP server that helps developers explore the Bitbybit API by searching members, describing contracts, listing namespaces, and retrieving TypeScript examples and build guides.

2 endpoints7 known toolsFirst detected September 21, 2026Last detected September 21, 2026

ENDPOINT 1

https://mcp.bitbybit.dev/mcp

No auth detected

MCP server metadata

Name: bitbybit
Version: 1.3.2

Capabilities

tools.listChanged

Server instructions

This is the Bitbybit CAD MCP: it documents the Bitbybit 3D CAD API (OpenCascade, JSCAD and Manifold kernels, with Babylon.js, three.js and PlayCanvas renderers) for one exact version. Always describe a member before using it: names, parameters and defaults come from the index, not from memory. Tiers matter: oss members are in the MIT npm packages and run anywhere; platform-pro members exist only inside bitbybit.dev; cloud-pro members run only on Bitbybit CAD Cloud with an API key. When asked where geometry should run, read get_guide("integrate") first: the packages alone are the default, and CAD Cloud is the answer only for algorithms that exist only there or for compute the caller cannot provide.

Known tools 7

search_api

Find Bitbybit API members (methods, namespaces, cloud operations) by keywords, for example "box solid" or "fillet edges".

Inferred read-only

describe

The exact contract of one member by dotted path, for example occt.

Inferred read-only

list_namespace

The members one level below a namespace path, for example occt.

Inferred read-only

get_examples

Working TypeScript examples for a member path, for a namespace, or for a topic given as keywords.

Inferred read-only

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

Inferred read-only

search

Searches the Bitbybit API documentation and returns a list of results with id, title and url.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bitbybit]
url = "https://mcp.bitbybit.dev/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: bitbybit
Remote MCP URL: https://mcp.bitbybit.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bitbybit": {
      "url": "https://mcp.bitbybit.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "bitbybit",
  "transport": "streamable-http",
  "url": "https://mcp.bitbybit.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://api.bitbybit.dev/mcp

Auth required

Known tools 0

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bitbybit-dev]
url = "https://api.bitbybit.dev/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Code

.mcp.json

{
  "mcpServers": {
    "bitbybit-dev": {
      "type": "http",
      "url": "https://api.bitbybit.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Desktop

Settings → Connectors → Add custom connector

Name: bitbybit-dev
Remote MCP URL: https://api.bitbybit.dev/mcp

Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bitbybit-dev": {
      "url": "https://api.bitbybit.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Visual Studio Code

.vscode/mcp.json

{
  "servers": {
    "bitbybit-dev": {
      "type": "http",
      "url": "https://api.bitbybit.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${input:mcp-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-token",
      "description": "bitbybit-dev bearer token",
      "password": true
    }
  ]
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Generic MCP

Client-specific MCP configuration

{
  "name": "bitbybit-dev",
  "transport": "streamable-http",
  "url": "https://api.bitbybit.dev/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_BEARER_TOKEN"
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.