Connect your client

In ChatGPT, Lofty is a published app — install 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.

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

One connector covers claude.ai web, the Claude desktop and mobile apps, Cowork, and Claude Code on the web: remote MCP servers are brokered through your Claude account, so a connector added once shows up everywhere you are signed in. (claude_desktop_config.json is for local stdio servers only and cannot point at a remote server.) Lofty publishes a public OAuth client, so you don’t register anything and there is no secret to paste.

Settings → Connectors → Add custom connector
Remote MCP server URL: https://mcp.lofty.com/mcp
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.
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.On Team and Enterprise plans only an organization Owner can add the connector; members then each sign in with their own Lofty account. On Free, Pro and Max plans you add it yourself.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.

OAuth 2.0 + PKCE (recommended). 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.

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.

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.

~/.cursor/mcp.json — or .cursor/mcp.json for one project

{
  "mcpServers": {
    "lofty": {
      "url": "https://mcp.lofty.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

.vscode/mcp.json — prompts for the key

{
  "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.

~/.codex/config.toml

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

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:

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"}'

Get Started

Read Tools

Write Tools

Guides