Install Guides

Choose the client you want to configure.

Every client handles the final setup step a little differently. These guides keep the connection flow specific, consistent, and easy to verify.

Codex

Install Enchant in Codex

Use the hosted MCP URL, then let Codex complete OAuth in the browser or fall back to a bearer token env var.

Hosted OAuth over MCP, with bearer token fallback.

Claude Code

Claude Code supports remote HTTP MCP servers well, including browser OAuth and a manual Authorization header fallback.

Hosted OAuth over MCP, with header-based bearer token fallback.

Cursor

Cursor supports remote Streamable HTTP MCP servers and OAuth, with mcp.json as the common install surface for editor and CLI.

Hosted OAuth over MCP, with mcp.json fallback for manual token auth.

VS Code

VS Code can connect to remote MCP servers from `.vscode/mcp.json`, which makes Enchant easy to share at repo scope.

Hosted OAuth over MCP, with bearer token fallback when the client supports explicit headers.

Copilot CLI

GitHub Copilot CLI can read `.mcp.json`, which makes Enchant a good fit for repo-local or user-local MCP installs.

Hosted OAuth over MCP, with bearer token fallback.

ChatGPT

ChatGPT can connect to remote MCP servers through its custom connector flow when workspace settings allow developer-mode MCP installs.

Hosted OAuth over MCP.