Cloud MCP

Connect your AI coding agent to Bit Cloud. Once connected, your agent can search, browse, and understand your components — their APIs, dependencies, source code, and documentation.

Connect your agent

Add the Bit Cloud MCP server to your agent. Authentication is handled automatically via OAuth — when you first use an MCP tool, your browser opens for you to log in to Bit Cloud.

Claude CodeRun in your terminal:claude mcp add --transport http bit-cloud https://mcp.bit.cloud/mcp

CodexAdd to your Codex config:

# ~/.codex/config.toml
[mcp_servers.bit-cloud]
url = "https://mcp.bit.cloud/mcp"

CursorAdd to your project or global config:

// .cursor/mcp.json
{
  "mcpServers": {
    "bit-cloud": {
      "url": "https://mcp.bit.cloud/mcp"
    }
  }
}

WindsurfAdd to your Windsurf MCP config:

// ~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "bit-cloud": {
      "serverUrl": "https://mcp.bit.cloud/mcp"
    }
  }
}

GitHub CopilotAdd to your VS Code workspace:

// .vscode/mcp.json
{
  "servers": {
    "bit-cloud": {
      "type": "http",
      "url": "https://mcp.bit.cloud/mcp"
    }
  }
}

Any MCP client that supports HTTP transport can connect using https://mcp.bit.cloud/mcp

Access tokens

For CI pipelines, service accounts, and shared team configurations, use an access token instead of OAuth.

Organization token (recommended for teams)Go to Organization Settings > Access Tokens in Bit Cloud. Create a new token and select the scopes it should have access to. Leave scopes empty to grant access to all scopes.

User tokenGo to User Settings > Access Tokens. A user token grants full access to everything you can see in Bit Cloud, including write operations.

// .cursor/mcp.json — with access token
{
  "mcpServers": {
    "bit-cloud": {
      "url": "https://mcp.bit.cloud/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Learn more about access tokens

Verify the connection

Restart your editorFully quit and reopen your editor to pick up the new MCP configuration.

Ask a test questionAsk your agent: "List the scopes in my Bit Cloud organization"

Add reuse instructions

Add these guidelines to your project's AI instructions (e.g., CLAUDE.md, .cursorrules) to encourage component reuse:

## Bit Cloud component reuse

When building features, always check Bit Cloud for existing components
before writing new code.

1. **Orient first** — Use `orientation` to get a high-level map of the
   organization's scopes and domains. This tells you where components live.
2. **Search before building** — Before implementing a feature, UI element, or utility,
   use `search_components` to check the Bit Cloud registry.
3. **Read before installing** — Use `read_components` to review the API
   reference, dependencies, and usage examples before adding a component.
4. **Reuse over rewrite** — Bit components are versioned, tested packages.
   Installing an existing component is faster and more reliable than
   writing from scratch.
5. **Install as packages** — Components are standard npm packages. Install
   with your package manager: `npm install @org/scope.component-name`.
6. **Check for design systems** — If the project needs a theme or design
   system, search for one first to ensure UI consistency.

Full instructions guide

Connect your agent

Access tokens

Verify the connection

Add reuse instructions

Next steps