Connect a client.

One remote MCP server over streamable HTTP with a static Bearer key — any client that can POST with a header connects unmodified.

ONE SERVER · ONE KEY · 40 CLIENTS DOCUMENTED BELOW

THE ENDPOINT — EVERY RECIPE BELOW USES EXACTLY THIS

Server    https://realcut.ai/api/mcp
Transport streamable HTTP (POST)
Auth      Authorization: Bearer <KEY>   (mint in /console/keys)

One paste

The primary clients. Paste the block, and the server lands under the name realcut. Sign in, and the console fills every block with a freshly minted key.

CLAUDE CODE

PLACEHOLDER <KEY> — MINT YOURS IN THE CONSOLE

claude mcp add --transport http realcut https://realcut.ai/api/mcp --header "Authorization: Bearer <KEY>"

CONFIGOne paste in any terminal — the server lands under the name realcut. Team distribution: --scope project writes a shareable .mcp.json at the repo root.

AUTHStatic Bearer header on every call; .mcp.json supports env-var expansion for the key.

VERIFYInside a session, run /mcp — realcut shows connected; a bad key shows failed.

DOCScode.claude.com/docs/en/mcp ↗

CURSOR

PLACEHOLDER <KEY> — MINT YOURS IN THE CONSOLE

{
  "mcpServers": {
    "realcut": {
      "url": "https://realcut.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <KEY>"
      }
    }
  }
}

CONFIG.cursor/mcp.json (project) or ~/.cursor/mcp.json (global). With a real key, the button below installs it in one click.

AUTHheaders.Authorization carries the Bearer key; ${env:NAME} interpolation is supported.

VERIFYCursor Settings → MCP lists realcut; the first tool call flips the strip below.

DOCScursor.com/docs/context/mcp ↗

VS CODE

PLACEHOLDER <KEY> — MINT YOURS IN THE CONSOLE

{
  "servers": {
    "realcut": {
      "type": "http",
      "url": "https://realcut.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <KEY>"
      }
    }
  }
}

CONFIG.vscode/mcp.json (workspace) — the top-level key is servers, not mcpServers. User-level: the MCP: Open User Configuration command.

AUTHheaders.Authorization carries the Bearer key. Secret-safe option: an inputs[] promptString entry with password:true, referenced as "Bearer ${input:realcut-key}" — VS Code prompts once and stores it hidden.

VERIFYChat view → agent mode: the tools icon lists realcut.

DOCScode.visualstudio.com/docs/copilot/customization/mcp-servers ↗

CHATGPT DESKTOP + CODEXDEVELOPER MODE

PLACEHOLDER <KEY> — MINT YOURS IN THE CONSOLE

[mcp_servers.realcut]
url = "https://realcut.ai/api/mcp"
http_headers = { "Authorization" = "Bearer <KEY>" }

CONFIG~/.codex/config.toml — one paste covers ChatGPT desktop, Codex CLI, and the IDE extension (officially shared config). UI door: ChatGPT Settings → MCP servers → Add server.

AUTHhttp_headers carries the Bearer value; bearer_token_env_var = "REALCUT_KEY" keeps the key out of the file.

VERIFYAsk ChatGPT or Codex to list realcut tools; the first call flips the strip below.

DOCSlearn.chatgpt.com/docs/extend/mcp ↗

CLAUDE DESKTOPPROXY · NEEDS NODE

PLACEHOLDER <KEY> — MINT YOURS IN THE CONSOLE

{
  "mcpServers": {
    "realcut": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://realcut.ai/api/mcp",
        "--header",
        "Authorization:${RC_MCP_AUTH}"
      ],
      "env": {
        "RC_MCP_AUTH": "Bearer <KEY>"
      }
    }
  }
}

CONFIGSettings → Developer → Edit Config — merge into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/ · Windows: %APPDATA%\Claude\), then restart. Needs Node.

AUTHDesktop custom connectors are OAuth-only today, so the key rides the mcp-remote bridge — Authorization via an env var (the documented Windows workaround).

NOTEClaude is rolling out Request-headers auth — when your Add-custom-connector dialog shows REQUEST HEADERS, paste the server URL and Bearer rc_live_YOUR_KEY there instead. No Node needed.

VERIFYAfter restart, the tools menu lists realcut.

DOCSclaude.com/docs/connectors/custom/remote-mcp ↗

JSON / CURL

PLACEHOLDER <KEY> — MINT YOURS IN THE CONSOLE

curl -X POST https://realcut.ai/api/mcp \
  -H "Authorization: Bearer <KEY>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

CONFIGAny shell, any HTTP client — this is the wire itself.

AUTHStatic Bearer header on a stateless POST — streamable HTTP MCP.

VERIFYA JSON tools/list result is the proof; the strip below flips on the first authorized call.

DOCSrealcut.ai/developers ↗

More clients

Every row is doc-verified and connects today — unmodified, or over the documented mcp-remote bridge where flagged. The full paste block for each lives on the console connect page.

IDES & CLIS

CLIENT	WHERE IT GOES	FLAGS	DOCS
WINDSURF	~/.codeium/windsurf/mcp_config.json — the key is serverUrl, not url. Refresh from the Cascade MCP panel after editing.	—	docs ↗
CLINE	Cline panel → MCP Servers → Configure tab (CLI: ~/.cline/mcp.json). The type is streamableHttp — camelCase.	—	docs ↗
ROO CODE	Project .roo/mcp.json (or global mcp_settings.json via the MCP settings UI; project overrides global). The type is streamable-http — hyphenated, unlike Cline.	—	docs ↗
ZED	settings.json (the zed: open settings command) — the top-level key is context_servers. Settings hot-reload; no restart.	—	docs ↗
JETBRAINS · JUNIE	Junie: project .junie/mcp/mcp.json or user ~/.junie/mcp/mcp.json — one file shared by the Junie CLI and the IDE plugin.	—	docs ↗
GEMINI CLI	~/.gemini/settings.json (or project .gemini/settings.json) — the key is httpUrl; plain url means SSE there. Gemini Code Assist agent mode reads the same file.	—	docs ↗
GITHUB COPILOT AGENT	github.com → your repo → Settings → Copilot → Coding agent → MCP configuration. The tools allowlist is required (["*"] for all).	—	docs ↗
OPENCODE	opencode.json at the project root or ~/.config/opencode/opencode.json — the top-level key is mcp.	—	docs ↗
AMAZON Q CLI	~/.aws/amazonq/mcp.json (global) or .amazonq/mcp.json (workspace); manage with qchat mcp add / list / status.	PROXY · NEEDS NODE	docs ↗

CHAT & DESKTOP

CLIENT	WHERE IT GOES	FLAGS	DOCS
GOOSE	~/.config/goose/config.yaml (Windows: %APPDATA%\Block\goose\config\config.yaml) — an extensions map with uri, not url. UI: Extensions → Add custom extension → Streamable HTTP. Applies to new sessions.	—	docs ↗
LM STUDIO	Right sidebar → Program tab → Install → Edit mcp.json — the in-app editor saves live; no restart.	—	docs ↗
LIBRECHAT	librechat.yaml, then restart — servers initialize at startup. ${VAR} plus per-user {{LIBRECHAT_USER_ID}} placeholders make it a clean multi-tenant self-host.	—	docs ↗
OPEN WEBUI	Admin Settings → External Tools → + Add Server (admin-only — users cannot add MCP servers themselves). Native MCP since v0.6.31, streamable-HTTP only.	—	docs ↗
RAYCAST	Run the Install MCP Server command (Mac; Windows beta) — Raycast connects and pulls the tool list immediately; no restart.	—	docs ↗
WARP	Settings → Agents → MCP servers → + Add, paste the entry (file alternative: ~/.warp/.mcp.json global or .warp/.mcp.json project). Start it from the MCP panel.	—	docs ↗

AUTOMATION

CLIENT	WHERE IT GOES	FLAGS	DOCS
N8N	Workflow → AI Agent node → add tool → MCP Client Tool. Self-hosted needs ≥ 1.104.0 (HTTP Streamable; SSE is deprecated legacy).	—	docs ↗
ZAPIER MCP CLIENT	Zapier → Apps → + Add connection → MCP Client → Add connection. Distinct from Zapier-MCP-as-server (zapier.com/mcp) — that is the other direction.	BETA	docs ↗

SDKS & API

CLIENT	WHERE IT GOES	FLAGS	DOCS
CLAUDE API	Messages API request body — both halves required: the mcp_servers entry AND its mcp_toolset reference in tools.	—	docs ↗
CLAUDE AGENT SDK	TS or Python: options.mcpServers plus an allowedTools entry for mcp__realcut__*.	—	docs ↗
OPENAI AGENTS SDK	Client-side MCPServerStreamableHttp (shown), or OpenAI-hosted HostedMCPTool with the same url + headers.	—	docs ↗
VERCEL AI SDK	createMCPClient from @ai-sdk/mcp (v7; pre-v7: experimental_createMCPClient from ai).	—	docs ↗
LANGCHAIN	langchain-mcp-adapters’ MultiServerMCPClient — works in LangChain and LangGraph.	—	docs ↗
MCP-USE	Python or TS: MCPClient.from_dict over the generic mcpServers shape.	—	docs ↗
FAST-AGENT	fast-agent.yaml → mcp.servers.realcut.	—	docs ↗
GOOGLE ADK	Python: McpToolset over StreamableHTTPConnectionParams.	—	docs ↗
PYDANTIC AI	Python: the MCP toolset takes the server URL plus a headers argument.	—	docs ↗
AUTOGEN	Python: StreamableHttpServerParams passed to the MCP workbench/adapter.	—	docs ↗

EVERY PASTE BLOCK, KEY-FILLED → /console/connect

Documented — not yet one-paste

Rows below state their unlock instead of a paste block, or serve a niche audience — documented here so nothing on this page overclaims.

ChatGPT webAuthenticated remote servers require an OAuth 2.1 flow (PKCE) — a static Bearer key cannot connect.ARRIVES WITH THE OAUTH WAVE

claude.ai · Claude mobile · CoworkCustom connectors are OAuth-only until the static_headers beta lands on the account; no proxy exists for a hosted surface.ARRIVES WITH THE OAUTH WAVE — OR THE DAY THE REQUEST-HEADERS BETA REACHES YOUR ACCOUNT

Microsoft Copilot StudioWhether the key value must include the Bearer prefix is undocumented — untested detail, so no paste block ships until it is.ENTERPRISE PATH — ONE CUSTOMER ASK PLUS A BEARER-PREFIX TEST

BoltAI~/.boltai/mcp.json — the official FAQ path is the mcp-remote bridge; native remote headers are not documented.docs ↗

Cherry StudioSettings → MCP Servers → Add (or Import JSON) — streamableHttp type.docs ↗

ChatWiseTools → add an MCP server — streamable HTTP with custom headers. Does not listen for server-initiated messages (fine for our stateless POST).docs ↗

Msty StudioStudio → Toolbox → Tools — HTTP (streamable; SSE explicitly unsupported). MCP lives in Msty Studio, not classic Msty.docs ↗

AUTH TODAY: STATIC BEARER KEYS · OAUTH CONNECT IS NOT ENABLED YET — THE OAUTH-WAVE ROWS ABOVE OPEN WHEN IT ARMS

ONE KEY, BOTH FRONTS — REST + MCP

CALLS RETURN 503 MODEL_NOT_DEPLOYED UNTIL RCM 1 CLEARS OUR QUALITY BAR. KEYS MINT TODAY; THE CONTRACT IS LIVE.

FULFILLMENT: EARLY ACCESS — EDIT JOBS ARE FULFILLED BY THE REAL CUT BENCH, THE SAME QUEUE THE APP USES, WHILE RCM 1 TRAINS.

EVERY RECIPE VERIFIED AGAINST ITS CLIENT’S OFFICIAL DOCS · LAST PASS 2026-07-19 · RE-CHECKED QUARTERLY