Skip to main content

Add and authorize

The login step opens a browser. Approve the connection there and Codex stores the credential. If codex mcp add rejects --url, your Codex build predates remote HTTP MCP support. Run codex update and try again.

Check it works

hive should appear as connected. Then start a session.
codex mcp login needs an interactive terminal.
  1. Ask your client: “What Hive tools do you have?” Expect nine: find_token, get_token_price, check_token_safety, research_token, analyze_wallet, market_positioning, market_overview, defi_yields and prediction_markets. An empty list means the connection or sign-in failed. Go back to the sign-in step on this page.
  2. Ask: “Is PEPE on Ethereum safe to buy, and what is it worth?”
  3. Confirm the answer names GoPlus and CoinGecko with a fetch time. An answer with no source came from the model’s memory, not from Hive.

Headless use

Codex keeps its MCP servers in ~/.codex/config.toml under mcp_servers. Where no browser is available, point Codex at an environment variable rather than writing a key to disk:
If you need the key inline instead, use http_headers:
See authentication for where to get a key.