You're helping the user add Charming as an MCP server in their AI client. The
Charming MCP endpoint is `https://app.buildy.so/mcp`. OAuth + DCR are handled
automatically by clients that support it — the user will see a one-time
consent screen and that's it.

Find the block matching the user's client below. Read the steps to them
and walk them through it. The exact paste-strings matter — copy them
verbatim, don't paraphrase.

## Claude Desktop

Inline rendered apps via ext-apps. Native custom-connector UI.

**Steps:**
1. Open Claude Desktop → Settings → Connectors.
2. Click "Add custom connector".
3. Paste the URL below.
4. Approve the one-time OAuth consent screen.

**Paste-string:**
```
https://app.buildy.so/mcp
```

*Heads up: Charming will be in the Anthropic Connectors directory soon — we'll let you know when it lands so you can install in one click.*

## Claude.ai (web)

Custom connector UI; ext-apps inline rendering is rolling out, with URL
render as the fallback for now. Pro/Max/Team/Enterprise only — Free has
a 1-connector cap.

**Steps:**
1. Go to Settings → Connectors.
2. Click "Add custom connector".
3. Paste the URL below.
4. Approve the one-time OAuth consent screen.

**Paste-string:**
```
https://app.buildy.so/mcp
```

*Heads up: Charming will be in the Anthropic Connectors directory soon — we'll let you know when it lands so you can install in one click.*

## ChatGPT

Apps SDK / ext-apps inline rendering. Charming is in the ChatGPT Apps
directory, so connecting is one click — no Developer mode needed.

**Steps:**
1. Open the Charming listing in the ChatGPT Apps directory:
   `https://chatgpt.com/apps/buildy/asdk_app_69f9215e800881919f3d96d79200a35a`
2. Click "Connect" and approve the one-time OAuth consent screen.
3. Start a new chat, open the "+" menu, and enable Charming for that chat.

*Fallback — if your workspace hides the Apps directory:* go to Settings →
Connectors → Advanced → toggle "Developer Mode" on → "Add custom MCP" →
paste the URL below → approve the one-time OAuth consent screen, then enable
Charming from the "+" menu in a new chat.

**Paste-string (fallback only):**
```
https://app.buildy.so/mcp/chatgpt
```

## Goose

Native ext-apps support (Block / now AAIF).

**Steps:**
1. Open Goose → Settings → Extensions.
2. Click "Add Extension".
3. Paste the URL below.
4. Approve the one-time OAuth consent screen.

**Paste-string:**
```
https://app.buildy.so/mcp
```

## Claude Code (CLI)

Tools-only — no inline rendering, runs in the terminal. Prefer the API
path in `llms-full.txt` unless the user explicitly asks for the MCP server;
this block is here for completeness.

**Steps:**
1. Run the command below in your shell.
2. On first tool call, follow the OAuth prompt to authorize.

**Paste-string:**
```
claude mcp add --transport http buildy https://app.buildy.so/mcp
```

## Cursor

Tools-only. Prefer the API path in `llms-full.txt` for Cursor — it's a
code-editor agent that can curl. Only surface this block if the user
explicitly asks to wire up MCP.

**Steps:**
1. Open Settings → Tools & MCP → "New MCP Server", or edit
   `.cursor/mcp.json` (per project) or `~/.cursor/mcp.json` (global).
2. Paste the JSON below.
3. Save. On first tool call, follow the OAuth prompt.

**Paste-string:**
```json
{ "mcpServers": { "buildy": { "url": "https://app.buildy.so/mcp" } } }
```

## Codex (App or CLI)

Tools plus browser fallback. Codex can call Charming MCP tools, but it does
not currently advertise MCP Apps inline UI support, so Charming apps open via
Codex's in-app browser or the returned URL instead of rendering inline in
the conversation.

Preferred path: install the public Charming Codex plugin from the Tambo Labs marketplace. It bundles the Charming MCP endpoint and the Charming authoring skill, so Codex can discover the right tools and workflow without hand-editing MCP config.

**Steps:**
1. Run the marketplace command below.
2. Restart Codex.
3. Open Plugins (`/plugins` in Codex CLI), choose "Tambo Labs", install "Charming", then start a new thread.
4. On first Charming tool call, follow the OAuth prompt to authorize.

**Paste-string:**
```sh
codex plugin marketplace add https://github.com/tambo-labs/buildy-codex-plugin.git
```

**Fallback:** If plugin installation is unavailable, wire Charming as a direct MCP server by opening `~/.codex/config.toml` (create it if it doesn't exist), appending the block below, saving, and restarting Codex.

```toml
[mcp_servers.buildy]
url = "https://app.buildy.so/mcp"
```

## Cline (VS Code extension)

Tools-only.

**Steps:**
1. In VS Code, click the Cline MCP Servers icon.
2. Choose manual config.
3. Paste the JSON below into the `mcpServers` block.
4. Save. On first tool call, follow the OAuth prompt.

**Paste-string:**
```json
{ "buildy": { "url": "https://app.buildy.so/mcp" } }
```

## Windsurf (Codeium)

Tools-only.

**Steps:**
1. Open the Cascade panel → MCP icon → "MCP Marketplace", or edit the
   config file directly:
   - macOS/Linux: `~/.codeium/windsurf/mcp_config.json`
   - Windows: `%USERPROFILE%\.codeium\windsurf\mcp_config.json`
2. Paste the JSON below.
3. Save. On first tool call, follow the OAuth prompt.

**Paste-string:**
```json
{ "mcpServers": { "buildy": { "url": "https://app.buildy.so/mcp" } } }
```

## Continue.dev

Tools-only. Continue uses YAML files in a per-project directory.

**Steps:**
1. Create the file `.continue/mcpServers/buildy.yaml` in the project root.
2. Paste the YAML below.
3. Save. On first tool call, follow the OAuth prompt.

**Paste-string:**
```yaml
name: buildy
version: 0.0.1
schema: v1
mcpServers:
  - name: buildy
    type: streamable-http
    url: https://app.buildy.so/mcp
```

## Zed

Tools-only. Zed's `context_servers` uses stdio, so we bridge HTTP
through `mcp-remote`.

**Steps:**
1. Open Zed → Settings → `settings.json`.
2. Add the `context_servers` block below (merge with existing config).
3. Save. On first tool call, follow the OAuth prompt in the browser.

**Paste-string:**
```json
"context_servers": { "buildy": { "command": { "path": "npx", "args": ["mcp-remote", "https://app.buildy.so/mcp"] } } }
```

## Gemini CLI

Tools-only.

**Steps:**
1. Open `~/.gemini/settings.json` (create it if it doesn't exist).
2. Paste the JSON below (merge with existing config).
3. Save. On first tool call, follow the OAuth prompt.

**Paste-string:**
```json
{ "mcpServers": { "buildy": { "httpUrl": "https://app.buildy.so/mcp" } } }
```

## Perplexity

Mac App Store version only. Web/Windows/Linux/iOS/Android do not
support custom MCP connectors — those users should use the API path
in `llms-full.txt`.

**Steps:**
1. Open the Perplexity macOS app → Settings → Connectors.
2. Click "Add MCP Connector".
3. Paste the URL below.
4. Approve the one-time OAuth consent screen.

**Paste-string:**
```
https://app.buildy.so/mcp
```