Skip to main content

Install Server

Connect your coding tool to Bezel's MCP server. For the full project setup, start with Quick Start using MCP.

Pro plans and above

MCP access requires a Bezel Pro plan or higher. On Free, use Manual Setup without MCP.

Start with one command​

With Node.js 22.13+, run this from your project's directory:

npx @bezel-labs/bezel-kit@latest install-mcp

Use the arrow keys to choose your coding tool, then press Enter and follow the sign-in instructions.

  • Claude Code, Cursor, and VS Code: configure this project.
  • Codex: configure your user account.
  • Other tools: show manual connection instructions.

To skip the menu, pass --client codex (or claude-code, cursor, vscode, other).

Use the client-specific instructions below if you prefer to configure the connection yourself.

Connect your assistant​

Use this endpoint with Streamable HTTP transport and OAuth authentication:

https://mcp.bezel.new/mcp

Bezel authenticates over OAuth, so there's no API key to generate, paste, or rotate.

Complete the browser sign-in when your client prompts you. The client manages your OAuth credentials.

Claude Code​

claude mcp add --transport http bezel https://mcp.bezel.new/mcp

Then run /mcp, pick bezel, and authenticate.

See the Claude Code MCP documentation for configuration scopes and authentication.

Codex​

codex mcp add bezel --url https://mcp.bezel.new/mcp
codex mcp login bezel

Complete the browser sign-in, then open Codex in the repository you want to configure.

Use codex mcp list or /mcp in the CLI to check the connection.

See the official Codex MCP documentation.

Other compatible clients​

Bezel uses remote Streamable HTTP with OAuth. Clients need support for that transport, OAuth sign-in, and MCP tools. Prompt support is optional.

Local automation also needs file editing and command execution; clients without those capabilities can guide you through manual steps but cannot install packages or verify generated files on your computer.

Cursor​

.cursor/mcp.json in your project, or ~/.cursor/mcp.json globally:

{
  "mcpServers": {
    "bezel": {
      "url": "https://mcp.bezel.new/mcp"
    }
  }
}

VS Code (GitHub Copilot)​

.vscode/mcp.json:

{
  "servers": {
    "bezel": {
      "type": "http",
      "url": "https://mcp.bezel.new/mcp"
    }
  }
}

Windsurf​

{
  "mcpServers": {
    "bezel": {
      "serverUrl": "https://mcp.bezel.new/mcp"
    }
  }
}

Zed​

settings.json:

{
  "context_servers": {
    "bezel": {
      "transport": "http",
      "url": "https://mcp.bezel.new/mcp"
    }
  }
}

Continue​

~/.continue/config.yaml:

mcpServers:
  - name: bezel
    url: https://mcp.bezel.new/mcp

ChatGPT​

ChatGPT connects to remote MCP servers as custom connectors. Developer mode is required and is available on Plus, Pro, Business, Enterprise, and Edu plans.

On Business and Enterprise workspaces an admin must first allow custom MCP connectors under Workspace Settings → Permissions & Roles → Connected Data.

  1. In ChatGPT on the web, open Settings → Apps (labelled Connectors in some workspaces) → Advanced settings and turn on Developer mode.

  2. Back on the same page, click Create. Enter a name (Bezel), a short description, and https://mcp.bezel.new/mcp as the MCP server URL. Leave authentication on OAuth.

  3. Click Create, then complete the sign-in when the browser prompt appears.

  4. In a new chat, click + in the composer, choose More → Developer mode, and select Bezel as a source for the conversation.

Bolt.new​

  1. In a Bolt project, click + in the chat box, select Connectors, then Manage connectors.

  2. Click Custom MCP server and enter a name (Bezel), the URL https://mcp.bezel.new/mcp, transport type HTTP, and authentication OAuth sign-in.

  3. Click Connect and approve the sign-in. A Connected status appears once Bolt can reach the server.

All of Bezel's tools are enabled by default and apply to every project. Trim the list from the connector's ⋯ → Edit menu if you only want a subset.

Check that it worked​

Ask your assistant:

List my Bezel projects.

You should get your project names and IDs back. That verifies authentication and project discovery; then follow Quick Start using MCP to set up your app.

If it doesn't​

Nothing happens, or the tools never appear.

Most editors only read MCP config at startup, so restart it. Then confirm the server is listed as connected in your editor's MCP panel.

"Unauthorized" or a 401.

The OAuth token expired or was never granted. Re-run the authentication step for the server (in Claude Code, /mcp → bezel → authenticate; in Codex, codex mcp login bezel).

"MCP access is not available on your current plan" or a 403.

You authenticated fine, but MCP is available on Pro and higher. Upgrade in the app under Settings → Billing.

Your assistant can't find a project by name.

find-project matches names case-insensitively, and when more than one project matches it lists the candidates and asks rather than guessing. If nothing matches, ask it to list your projects and use the ID instead.

Set up your repository​

Once connected, ask your assistant:

Set up Bezel in this project.

Quick Start using MCP covers project selection, Bezel Kit installation, generated files, and app integration. The assistant needs file and terminal access to perform local setup.

Choose your Crystal setup​

Crystal is optional. The assistant asks separately how you want to install it; see the Crystal choices in Quick Start.