build69
Get started with build69

Use build69 in three steps.

Get a key, connect the agent you already use, then prompt normally. build69 writes the resolved source into your project.

1. Get your API key 2. Connect your agent
01

Get your API key

Create a free account and copy the key from your dashboard.

02

Connect your agent

Add one MCP endpoint to the client you already use.

03

Prompt and ship

Ask for a screen; build69 writes the source into your repo.

1–3
The whole setup

Get a key. Connect. Prompt.

The shortest path from a new account to source code in your repository.

01

Get your API key

Create a free account and copy the key from your dashboard.

02

Connect your agent

Add one MCP endpoint to the client you already use.

03

Prompt and ship

Ask for a screen; build69 writes the source into your repo.

terminal
$ npx @build69/connect --key b69_live_••••

Create the key in your account dashboard, connect your agent, then prompt: “add a build69 data table.”

02
Connect your agent

One endpoint, every build69 tool

Point any MCP-aware client at the hosted registry and authenticate with your API key.

mcp.json
{
  "mcpServers": {
    "build69": {
      "url": "https://mcp.build69.com",
      "headers": { "Authorization": "Bearer b69_live_…" }
    }
  }
}

The protocol is shared, but config keys differ by client. Use the exact guide below to avoid a silent setup failure.

02
Connect your agent

Choose your agent and copy its config

Claude, Codex, Cursor, Antigravity, VS Code, and Windsurf each spell MCP setup a little differently.

Claude Code

CLI

No file to edit — register it with the CLI. Use -s user to make it available in every project instead of just the current one. Without a key, the first connection opens your browser to sign in to build69 and approve Claude Code; run /mcp in a session to sign in again.

terminal
# sign in through the browser
claude mcp add --transport http build69 https://mcp.build69.com -s user

# or, on CI and headless machines, a key from /account/keys
claude mcp add --transport http build69 https://mcp.build69.com \
  --header "Authorization: Bearer b69_live_…" \
  -s user

# verify
claude mcp get build69

MCP servers are picked up when a session starts, so open a new session before looking for the tools.

Claude (desktop, web & mobile)

App

Settings → Connectors → Add → Add custom connector, then paste the registry URL.

connector URL
https://mcp.build69.com

Claude opens build69 in your browser to sign in and approve the connector; no key is needed. You can disconnect it from /account/keysunder Connected apps. Claude connects from Anthropic's cloud, not from your machine — the server must be reachable on the public internet. A registry on localhost will not work here; use Claude Code for that.

ChatGPT Codex

CLI

~/.codex/config.toml — TOML, not JSON. A project-local .codex/config.toml takes precedence over the global one.

~/.codex/config.toml
[mcp_servers.build69]
url = "https://mcp.build69.com"
bearer_token_env_var = "BUILD69_API_KEY"

Or skip the file: codex mcp add build69 --url https://mcp.build69.com. bearer_token_env_var names the env var to read — Codex sends it as Authorization: Bearer …, so the key never sits in the file.

Google Antigravity

IDE + CLI

~/.gemini/config/mcp_config.json, or per-workspace in .agents/mcp_config.json (which wins). The IDE, the CLI and the SDK share this one file. In the UI: Manage MCP Servers → View raw config.

mcp_config.json
{
  "mcpServers": {
    "build69": {
      "serverUrl": "https://mcp.build69.com",
      "headers": { "Authorization": "Bearer b69_live_…" }
    }
  }
}

Antigravity requires serverUrl for remote servers — url and httpUrl are rejected. Saving the file reloads the server automatically.

Cursor

IDE

.cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.

.cursor/mcp.json
{
  "mcpServers": {
    "build69": {
      "url": "https://mcp.build69.com",
      "headers": { "Authorization": "Bearer ${env:BUILD69_API_KEY}" }
    }
  }
}

${env:VAR} reads from your shell, so the key stays out of a file you might commit.

VS Code — Copilot agent mode

IDE

.vscode/mcp.json in the workspace.

.vscode/mcp.json
{
  "servers": {
    "build69": {
      "type": "http",
      "url": "https://mcp.build69.com",
      "headers": { "Authorization": "Bearer b69_live_…" }
    }
  }
}

Two VS Code specifics: the root key is servers, not mcpServers, and type is required. Tools only run in Agent mode — not Ask mode.

Windsurf

IDE

~/.codeium/windsurf/mcp_config.json (%USERPROFILE%\.codeium\windsurf\mcp_config.json on Windows).

mcp_config.json
{
  "mcpServers": {
    "build69": {
      "serverUrl": "https://mcp.build69.com",
      "headers": { "Authorization": "Bearer ${env:BUILD69_API_KEY}" }
    }
  }
}

Like Antigravity, Windsurf wants serverUrl rather than url.

The differences, side by side

These are the fields that change when you move a config between clients.

ClientRoot keyURL fieldAuth field
Claude Code— (CLI)positional argbrowser sign-in, or --header
Claude app— (UI)connector URLbrowser sign-in
ChatGPT Codex[mcp_servers.*]urlbearer_token_env_var
AntigravitymcpServersserverUrlheaders
CursormcpServersurlheaders
VS Codeserversurl (+ type)headers
WindsurfmcpServersserverUrlheaders
Security · Authentication

Keep the key out of source

Requests use a bearer token. Keys are shown once, hashed at rest, and can be rotated from the dashboard. Browsing and token reads are unmetered.

03 · Prompt and ship

Resolved source, ready to write

get_registry_item returns source, sub-components, npm dependencies, and resolved tokens.

get_registry_item({ name: "DataTable" })
→ files: data-table.tsx, table.tsx
→ deps: @tanstack/react-table
→ tokens: resolved
REF
Design tokens

One semantic layer for every surface

Components read from a shared OKLCH token system, so changing an accent recolours the whole interface without editing component code.

--primary
--success
--warning
--danger
--info
Reference · Theming

Twelve accents. Light and dark.

Set data-theme on the root and use the shared dark-mode class. The controls in this site use the same tokens your components receive.

Orange
Blue
Green
Violet
Rose
Teal
Amber
Indigo
Slate
Cyan
Fuchsia
Lime
FAQ
Questions

Before you connect

The practical details about compatibility, dependencies, and support.

Which agents are supported?

Any MCP-compatible client. Use the client guides above for Claude, Codex, Cursor, Antigravity, VS Code, or Windsurf.

Do I need to install a package?

No. Components arrive as source. Install only the npm dependencies each component actually uses.

Where do I get support?

Visit the support page; Pro and Team also include email support.

Ready for the first tool call?

Create a key and connect the client you already use.

Get your API key