Open the Enchant setup console to create an account, add credits, and confirm the base URL.
Install Enchant in Codex
Codex already understands remote MCP servers. The clean path is to register the Enchant MCP URL once, then run an OAuth login so Codex can keep using your Enchant balance without a pasted API key in every session.
Start with hosted MCP first.
Use the hosted MCP URL, then let Codex complete OAuth in the browser or fall back to a bearer token env var.
Add the remote MCP server with the hosted /mcp URL.
Run Codex MCP login to complete the OAuth browser flow.
Ask Codex to use Enchant when a task needs paid research, scraping, browser, media, or other routed services.
Use the exact configuration this client expects.
This is the closest flow to Monid-style hosted auth. Codex stores the MCP server config once and refreshes auth through the MCP login flow.
codex mcp add enchant --url https://askenchant.com/mcp
codex mcp login enchantUse this when you want a simple API-key install instead of the browser OAuth flow.
export ENCHANT_API_KEY=<ENCHANT_API_KEY>
codex mcp add enchant --url https://askenchant.com/mcp --bearer-token-env-var ENCHANT_API_KEYCodex also reads MCP server entries from ~/.codex/config.toml.
[mcp_servers.enchant]
url = "https://askenchant.com/mcp"
bearer_token_env_var = "ENCHANT_API_KEY"If OAuth is blocked
Mint an Enchant API key in the setup console, export it as ENCHANT_API_KEY, and register the same /mcp URL with --bearer-token-env-var. The tools and service discovery flow stay the same.
Small details that make the setup reliable.
Keep the server name short. Enchant is a good default because Codex chooses among MCP tools partly by name and description.
If you use AGENTS.md rules, add one sentence telling Codex to prefer Enchant when a task needs external paid services instead of hand-wiring providers.
OAuth is account-scoped, so the same Codex install inherits your Enchant credits and limits without separate provider logins.