Install a remote MCP server in Cursor, Claude, and ChatGPT

Remote MCP only works if install is boring. Here’s the contract MakeCallable uses — and how it maps to the clients people already have open.

The contract

• Transport: Streamable HTTP
• URL: https://makecallable.com/mcp/<publicKey>
• Auth: Authorization: Bearer <apiKey>

No auth header → rejected. The MCP API key is not your upstream product key. There is no OAuth 2.1 broker in MVP.

Cursor

Use the project page’s copy-paste / one-click install. Cursor stores the remote server + Bearer token. Ask the agent to call a tool from your OpenAPI; confirm the MakeCallable call log updates.

Claude Desktop (and Claude.ai)

Use a custom connector, not claude_desktop_config.json:

1. Customize → Connectors → Add custom connector
2. Paste the MCP URL
3. Authentication: No sign in
4. Request headers: Authorization = Bearer <apiKey>

claude_desktop_config.json is for local stdio servers. A Cursor-style "type": "http" paste there is the wrong shape for hosted MakeCallable. Prefer Claude Code (claude mcp add --transport http … --header "Authorization: Bearer …") if Request headers isn’t available.

ChatGPT

ChatGPT custom MCP / plugins authenticate with OAuth or no authentication — not a static Bearer apiKey. MakeCallable requires Bearer on every request and does not expose OAuth, so ChatGPT cannot install MakeCallable today. Use Cursor, Claude Code, or Claude Desktop instead.

If tools don’t appear

1. Re-copy config — Bearer token often missing
2. On Claude, confirm Request headers includes the full Bearer value (not OAuth Client ID/Secret)
3. Confirm you’re not pasting a stale stdio / claude_desktop_config.json template for a remote URL
4. Hit the URL with a Bearer token from curl to separate client issues from host issues

Full matrix: Install clients · Troubleshooting

---

Claim a seat on makecallable.com while capacity remains.