protogrid

Search / dev.bitbybit/cad-cloud

Bitbybit CAD Cloud MCP

R1· needs a key

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

v1.5.0 · active · website · descriptor JSON · versions

An agent can connect on its own if it already holds X_API_KEY.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Quality–not scored
Trust82of 100
Uptime, 30 days94%
Latency p50938 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "cad-cloud": {
      "type": "http",
      "url": "https://api.bitbybit.dev/mcp",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}
claude mcp add --transport http cad-cloud https://api.bitbybit.dev/mcp --header "X-API-Key: ${X_API_KEY}"
[mcp_servers.cad-cloud]
url = "https://api.bitbybit.dev/mcp"
env_http_headers = { "X-API-Key" = "X_API_KEY" }
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cad-cloud": {
      "type": "remote",
      "url": "https://api.bitbybit.dev/mcp",
      "enabled": true,
      "headers": {
        "X-API-Key": "{env:X_API_KEY}"
      }
    }
  }
}
{
  "mcpServers": {
    "cad-cloud": {
      "type": "http",
      "url": "https://api.bitbybit.dev/mcp",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=cad-cloud&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLmJpdGJ5Yml0LmRldi9tY3AiLCJoZWFkZXJzIjp7IlgtQVBJLUtleSI6IiR7WF9BUElfS0VZfSJ9fQ%3D%3D"
}
{
  "servers": {
    "cad-cloud": {
      "type": "http",
      "url": "https://api.bitbybit.dev/mcp",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}
{
  "mcpServers": {
    "cad-cloud": {
      "httpUrl": "https://api.bitbybit.dev/mcp",
      "headers": {
        "X-API-Key": "${X_API_KEY}"
      }
    }
  }
}
extensions:
  "cad-cloud":
    enabled: true
    name: "cad-cloud"
    type: streamable_http
    uri: "https://api.bitbybit.dev/mcp"
    headers:
      "X-API-Key": "${X_API_KEY}"
    timeout: 300

Placeholders to fill from your own secret store: ${X_API_KEY}. The registry never accepts secret values.

Quality – / 100not scored

Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.

protocoln/a · weight 25
  • n/a
    protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygienen/a · weight 30
  • n/a
    tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool list unknown
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

Tool list unknown · checked 2026-10-19 10:20 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 82 / 100

no-repository
provenance55
liveness98
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-94% +updated-7d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://api.bitbybit.dev/mcp streamable-httpapi_key ${X_API_KEY}yes94%938 ms–2026-10-19

Tools (0)

No tools observed. Tools appear once a credential-free probe can list them.

Schemas: list_tools.

Similar MCP servers

More from dev.bitbybit

Official server.json
{
  "name": "dev.bitbybit/cad-cloud",
  "icons": [
    {
      "src": "https://learn.bitbybit.dev/img/favicon-192x192.png",
      "sizes": [
        "192x192"
      ],
      "mimeType": "image/png"
    }
  ],
  "title": "Bitbybit CAD Cloud MCP",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://api.bitbybit.dev/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "X-API-Key",
          "isSecret": true,
          "isRequired": true,
          "description": "A CAD Cloud API key with the scopes of the tools you want to use"
        }
      ]
    }
  ],
  "version": "1.5.0",
  "websiteUrl": "https://learn.bitbybit.dev/learn/using-ai-with-bitbybit/mcp/cad-cloud-mcp",
  "description": "Run 3D CAD operations, pipelines, parametric models and STEP conversions on CAD Cloud with a key"
}