> ## Documentation Index
> Fetch the complete documentation index at: https://developer.lofty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your client

> Install the Lofty app in ChatGPT or the Lofty connector in Claude, or connect Lofty to Claude Code, Cursor, VS Code, Codex CLI, and any other Streamable HTTP MCP client.

In ChatGPT and Claude, Lofty is published in the app directory — add it and there is nothing to configure. Everywhere else you point a client at the endpoint yourself.

Any Streamable HTTP MCP client works. Two ways to authenticate: **OAuth 2.0 + PKCE**, where the client signs the user in through the browser and discovers the flow from the endpoint's own `401` challenge, or an **API key** passed as a header, which every client supports. Lofty does not support Dynamic Client Registration, so an OAuth client needs a `client_id` registered in the vendor portal; see [Authentication](https://developer.lofty.com/mcp/authentication.md).

> [tab] ChatGPT
>
> Lofty is published in the ChatGPT app directory, so there is no URL to paste, no `client_id`, and no API key. Search for **Lofty** in the app directory and install it, or open it directly:
>
> [Install the Lofty app in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6aa1121df1b08191b5d69ef142b9ee42?q=Lofty)
>
> The first time you use it, ChatGPT sends you to Lofty to sign in and authorize; after that it stays connected.
>
> Underneath it is the same MCP server as every other tab on this page — the same tools, and the same permissions. The app acts as whoever authorized it, so it can only read and change what that Lofty user could themselves.

> [tab] Claude.ai & Desktop
>
> Lofty is published in the Claude connector directory, so there is no URL to paste, no `client_id`, and no API key. The quickest way in is the direct link:
>
> [Add the Lofty connector in Claude](https://claude.ai/directory/lofty)
>
> Or find it in Claude yourself:
>
> **1. Open the Connectors settings**
>
> Click your name in the bottom-left corner and choose **Settings**. Type `Connectors` in the settings search box and select **Connectors**. You can also go to **Settings → Customize → Connectors**.
>
> **2. Find Lofty**
>
> Switch to **Discover** and search for `Lofty`. Select the **Lofty** connector by Lofty, marked **Community**.
>
> ![Connectors tab on Discover with 'Lofty' in the search box and the Lofty Community connector highlighted under More you can add](https://mintcdn.com/lofty-23bfa97a/X4cI5ctNq5df96te/images/mcp/claude-connectors-discover-lofty.png?fit=max\&auto=format\&n=X4cI5ctNq5df96te\&q=85\&s=a6bef99b129b02e5cad817da9b1629a2)
>
> **3. Connect**
>
> Click **Connect**, sign in to Lofty in the browser and click **Authorize**. After that it stays connected.
>
> Once connected, Lofty is available wherever you use Claude: web, desktop, mobile, Cowork, and Claude Code on the web. It acts as the Lofty user who authorized it, with that user's permissions.
>
> On Team and Enterprise plans, only an admin can add the connector; each member then signs in with their own Lofty account.
>
> > [accordion] Add it as a custom connector instead
> >
> > If the directory isn't available to you, add the server by hand:
> >
> > 1. **Settings → Connectors → Add custom connector**
> > 2. Remote MCP server URL: `https://mcp.lofty.com/mcp`
> > 3. Under **OAuth client** choose **Use your own OAuth client** (in some versions this is under *Advanced settings*). Client ID: `1wzhz7fnrr8qo`. Leave Client Secret empty — Claude then acts as a public client with PKCE.
> > 4. **Add**, then **Connect**. Sign in to Lofty in the browser and click **Authorize**.
> >
> > The other two OAuth options — *Register automatically* (Dynamic Client Registration) and *Use Claude's published identity* — are not supported by Lofty's authorization server and fail; see [Authentication](https://developer.lofty.com/mcp/authentication.md).
>
> Headless alternative: an admin can instead set a fixed request header `Authorization: Bearer <API key>` on the connector. Everyone in the organization then acts as the one Lofty user who owns that key, so prefer OAuth for anything beyond a demo.

> [tab] Claude Code
>
> **Already connected in Claude.ai? Nothing to set up.** If you sign in to Claude Code with a claude.ai account, the Lofty connector from the **Claude.ai & Desktop** tab is available automatically. Run `/mcp` and look for `claude.ai Lofty`. If it doesn't appear, run `/status`: Claude Code fetches connectors only with a claude.ai subscription login, not with an API key, `apiKeyHelper`, or a third-party provider such as Amazon Bedrock. Don't also add `lofty` with `claude mcp add` — a server you add yourself at the same URL hides the connector.
>
> If you use Claude Code with an API key or a third-party provider, add the server yourself:
>
> **OAuth 2.0 + PKCE.** Lofty publishes a public OAuth client for Claude Code, so you don't register anything. Use the client id and callback port exactly as shown — the port is part of the registered redirect URI, so a different port fails with a redirect mismatch. No secret is needed; Claude Code is a public client.
>
> ```bash theme={null}
> claude mcp add --transport http \
>   --client-id 1wzhz7fnrr8qo --callback-port 8765 \
>   lofty https://mcp.lofty.com/mcp
> ```
>
> Run `/mcp` inside a session, pick `lofty`, sign in to Lofty in the browser and click **Authorize**. Or from the shell: `claude mcp login lofty` (`--no-browser` over SSH prints the URL and lets you paste the redirect back). Tokens are stored in the keychain and refreshed automatically. Without `--client-id`, Claude Code tries Dynamic Client Registration and fails with *"does not support dynamic client registration"*.
>
> **API key (headless / CI).** Skips the browser entirely. Note that once any `Authorization` header is set the server never sends the `401` discovery challenge, so OAuth is not attempted.
>
> ```bash theme={null}
> claude mcp add --transport http lofty https://mcp.lofty.com/mcp \
>   --header "Authorization: Bearer $LOFTY_CUSTOMER_KEY"
> ```
>
> Verify with `claude mcp list`, then `/mcp` inside a session.

> [tab] Cursor
>
> `~/.cursor/mcp.json` — or `.cursor/mcp.json` for one project
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "lofty": {
>       "url": "https://mcp.lofty.com/mcp",
>       "headers": { "Authorization": "Bearer YOUR_KEY" }
>     }
>   }
> }
> ```

> [tab] VS Code
>
> `.vscode/mcp.json` — prompts for the key
>
> ```json theme={null}
> {
>   "inputs": [
>     { "id": "lofty-key", "type": "promptString",
>       "description": "Lofty API key", "password": true }
>   ],
>   "servers": {
>     "lofty": {
>       "type": "http",
>       "url": "https://mcp.lofty.com/mcp",
>       "headers": { "Authorization": "Bearer ${input:lofty-key}" }
>     }
>   }
> }
> ```
>
> The `inputs` block makes VS Code prompt for the key and store it in its secret store, so the token never lands in a file you might commit.

> [tab] Codex CLI
>
> `~/.codex/config.toml`
>
> ```toml theme={null}
> [mcp_servers.lofty]
> url = "https://mcp.lofty.com/mcp"
> bearer_token_env_var = "LOFTY_CUSTOMER_KEY"
> ```
>
> Reads the key from the environment rather than the config file — the same variable the Lofty CLI already uses.

> [tab] Other clients
>
> Follow your client's MCP setup instructions with:
>
> * Transport: **Streamable HTTP** (not SSE, not stdio)
> * URL: `https://mcp.lofty.com/mcp`
> * Header: `Authorization: Bearer <your key>`
>
> To test with no client at all, the endpoint is plain JSON-RPC over HTTP:
>
> ```bash theme={null}
> curl https://mcp.lofty.com/mcp \
>   -H "Content-Type: application/json" \
>   -H "Accept: application/json, text/event-stream" \
>   -H "Authorization: Bearer $LOFTY_CUSTOMER_KEY" \
>   -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
> ```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.