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

If the client cannot add an MCP server, or you would rather not, stop
here: any agent that can make HTTP requests builds the same apps through
Charming's HTTP API. Read `https://charm.ing/docs/build-http.md` and follow
it instead. Microsoft 365 Copilot is the one exception, where MCP is the
only path.

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://charm.ing/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)

Inline rendered apps via ext-apps, same as Claude Desktop. Native
custom-connector UI. 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://charm.ing/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 has a public listing in
ChatGPT, so installing it is one click — no Developer mode needed.

**Steps:**
1. Open the Charming listing in ChatGPT:
   `https://chatgpt.com/plugins/plugin_asdk_app_6a56c533cd7c8191b9a16cb7973a65e6`
2. Click "Install plugin" and approve the one-time OAuth consent screen.
3. Start a new chat and ask Charming to build something.

*Fallback — if your workspace hides the listing:* go to Settings →
Security and login → 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://charm.ing/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://charm.ing/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 charming https://charm.ing/mcp
```

## Claude Code (desktop app)

Inline rendered apps via ext-apps, same as Claude Desktop. Distinct from
the CLI above, which is terminal-only and has no inline rendering.

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

**Paste-string:**
```
https://charm.ing/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. Fastest: open the one-click installer, which fills the name and URL in:
   `https://cursor.com/en/install-mcp?name=charming&config=eyJ1cmwiOiJodHRwczovL2NoYXJtLmluZy9tY3AifQ%3D%3D`
   Otherwise open Settings → Tools & MCP → "New MCP Server", or edit
   `.cursor/mcp.json` (per project) or `~/.cursor/mcp.json` (global) and
   paste the JSON below.
2. Save. On first tool call, follow the OAuth prompt.

**Paste-string:**
```json
{ "mcpServers": { "charming": { "url": "https://charm.ing/mcp" } } }
```

## Codex (App or CLI)

The Codex app renders Charming apps inline. Codex CLI opens each app in the browser.
Both use the same Charming tools.

The Codex app shares its listing with ChatGPT, so installing from there is the
shortest path on the app:
`https://chatgpt.com/plugins/plugin_asdk_app_6a56c533cd7c8191b9a16cb7973a65e6`

For the CLI, 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.

*No plugin?* One command adds the MCP server directly, then restart Codex and start a new thread:

```sh
codex mcp add charming --url https://charm.ing/mcp
```

**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/charming-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.charming]
url = "https://charm.ing/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
{ "charming": { "url": "https://charm.ing/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": { "charming": { "url": "https://charm.ing/mcp" } } }
```

## Continue.dev

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

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

**Paste-string:**
```yaml
name: charming
version: 0.0.1
schema: v1
mcpServers:
  - name: charming
    type: streamable-http
    url: https://charm.ing/mcp
```

## Zed

Tools-only. Zed supports remote MCP servers and standard MCP OAuth.

**Steps:**
1. Open Settings → AI → MCP Servers.
2. Click "Add Server", then "Add Remote Server".
3. Name it Charming and paste the URL below.
4. Save. On first tool call, follow the OAuth prompt in the browser.

**Paste-string:**
```
https://charm.ing/mcp
```

## Gemini CLI

Tools-only.

**Steps:**
1. Run the command below.
2. Start Gemini CLI and run `/mcp auth charming`.
3. Approve access in the browser.

**Paste-string:**
```sh
gemini mcp add --transport http charming https://charm.ing/mcp
```

## Perplexity

Tools-only. Custom remote connectors must be enabled by the
organization's admin.

**Steps:**
1. Open Account settings → Connectors.
2. Click "+ Custom connector", then choose "Remote".
3. Name it Charming and paste the URL below.
4. Choose OAuth and Streamable HTTP.
5. Add the connector, open its card, and approve sign-in.

**Paste-string:**
```
https://charm.ing/mcp
```

## Microsoft 365 Copilot

Inline rendered apps via MCP Apps. Organization setup uses a declarative
agent built with Microsoft 365 Agents Toolkit.

**Steps:**
1. Create a Declarative Agent project in Microsoft 365 Agents Toolkit.
2. Add an action and choose "Start with an MCP Server".
3. Paste the URL below and choose OAuth with dynamic registration.
4. Provision and sideload the agent, then approve Charming sign-in.

**Paste-string:**
```
https://charm.ing/mcp
```

Full guide: `https://charm.ing/docs/clients/microsoft-365-copilot`

## Notion Custom Agents

Tools-only. Requires a Notion Business or Enterprise workspace and an admin
who allows custom MCP servers.

**Steps:**
1. In the agent's Settings, open Tools & Access.
2. Choose Add connection → Custom MCP server.
3. Name it Charming and paste the URL below.
4. Connect, approve sign-in, and choose the Charming tools the agent may use.

**Paste-string:**
```
https://charm.ing/mcp
```

## n8n

Tools-only. The MCP Client Tool uses a `chrm_user_*` bearer token. Follow the
pairing and token steps in the full guide before adding the node.

**Steps:**
1. Open `https://charm.ing/docs/clients/n8n` and pair n8n with Charming.
2. Add an AI Agent node and attach an MCP Client Tool node.
3. Paste the endpoint below into "SSE Endpoint".
4. Choose Bearer Auth and use the paired token.

**Paste-string:**
```
https://charm.ing/mcp
```

## Amazon Bedrock AgentCore

Tools-only. Requires an AgentCore Gateway, an API key credential provider,
and a paired `chrm_user_*` token.

**Steps:**
1. Open `https://charm.ing/docs/clients/agentcore` and pair AgentCore with Charming.
2. Add an MCP server target to the gateway.
3. Paste the endpoint below.
4. Use API key authorization with the `Authorization` header and `Bearer ` prefix.
5. Synchronize the target and test `list_apps`.

**Paste-string:**
```
https://charm.ing/mcp
```

## Grok

Tools-only. Grok supports public remote MCP servers as custom connectors.

**Steps:**
1. Open `https://grok.com/connectors`.
2. Click "New Connector", then choose "Custom".
3. Name it Charming and paste the URL below.
4. Complete sign-in when Grok asks.

**Paste-string:**
```
https://charm.ing/mcp
```