Supported hosts
Use this matrix to choose the setup guide for your MCP host. REST API and CLI paths are available separately when you control the API-key call path.
| Host | Recommended path | Auth model |
|---|---|---|
| Claude Desktop | /mcp/install/claude-desktop/ | OAuth through the desktop host. |
| Claude.ai | /mcp/install/claude-web/ | OAuth through the web connector flow. |
| ChatGPT | /mcp/install/chatgpt/ | OAuth through ChatGPT connectors where available for the workspace. |
| Cursor | /mcp/install/cursor/ | OAuth through Cursor MCP. |
| Cline | /mcp/install/cline/ | OAuth through the VS Code extension host. |
| Codex CLI | /mcp/install/codex-cli/ | OAuth through the CLI MCP bridge. |
| Gemini CLI | /mcp/install/gemini-cli/ | OAuth through the CLI MCP configuration. |
| curl or direct HTTP | /mcp/install/curl/ | API key for REST API; OAuth token for MCP calls. |
| Custom agents | Use the MCP endpoint and OAuth metadata. | Dynamic client registration where supported. |
Auth summary
Section titled “Auth summary”- REST API and CLI:
Authorization: Bearer $HOIST_API_KEY(aha_live_key). - MCP: OAuth consent at
https://mcp.assets.hoistai.com— no key to paste. - Human account pages: browser sessions.
Host not listed
Section titled “Host not listed”If a host supports remote MCP over streamable HTTP or SSE and OAuth, use:
MCPhttps://mcp.assets.hoistai.com/mcp
If the host only supports local subprocess MCP servers, use an MCP bridge that can proxy to a remote OAuth server.