Install Guide

Install Enchant in Codex

Register the Enchant MCP URL once, then complete OAuth so Codex can use your Enchant balance without a pasted API key in every session.

Open setup console All guides

Setup

Open Enchant agent setup to create an account, add credits, and confirm the base URL.

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.

Configuration

Recommended install

Codex stores the MCP server configuration and refreshes authorization through MCP login.

codex mcp add enchant --url https://askenchant.com/mcp
codex mcp login enchant

Manual bearer token fallback

Use 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_KEY

Config file example

Codex also reads MCP server entries from ~/.codex/config.toml.

[mcp_servers.enchant]
url = "https://askenchant.com/mcp"
bearer_token_env_var = "ENCHANT_API_KEY"

Fallback Option

If OAuth is blocked

Create an Enchant API key in agent setup, export it as ENCHANT_API_KEY, and register the same /mcp URL with --bearer-token-env-var. The available tools and service discovery do not change.

Notes

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.