Skip to main content

Install Server

One endpoint, one sign-in:

https://mcp.bezel.new/mcp

Bezel authenticates over OAuth, so there's no API key to generate, paste, or rotate. The first time your editor calls the server it opens a browser window, you approve, and the token is stored by the editor.

Claude Code​

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

Then run /mcp, pick bezel, and authenticate.

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.

Figma Make​

Custom connectors are available on paid Figma plans. Full seats can use them in any Make file; View, Dev, and Collab seats can try them in Drafts.

  1. In the Make prompt box, click Add context, hover Connectors, and choose Manage.
  2. Open the Created by you tab and click Create.
  3. Enter a name (Bezel) and https://mcp.bezel.new/mcp as the MCP server URL, then click Create. Leave Advanced settings empty so Figma uses Bezel's OAuth flow.
  4. Click Connect on the new connector and approve the sign-in.
  5. Enable the tools you want, then reference the connector in a prompt with @Bezel or just ask for your Bezel projects.

Check that it worked​

Ask your assistant:

List my Bezel projects.

You should get your project names and IDs back. If that works, everything else will.

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

"MCP access is not available on your current plan" or a 403. You authenticated fine, but MCP is a Pro and Enterprise feature. 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.