Skip to main content
Connect Hoard to the OpenAI Codex CLI so you can drive your store from the terminal.

​
What you’ll need

​
Pick your path

Codex authenticates against remote MCP servers in two ways depending on how you use it. Pick the one that matches your setup.
If you’re using…Use this section
The Codex plugin / marketplace UI (browser sign-in)OAuth
The codex mcp CLI (terminal-only)Bearer token
The bearer-token path works for both. The OAuth path does not work for the CLI runner — it currently reports Auth: Unsupported for OAuth-only servers in codex mcp list.

​
OAuth (plugin UI)

1

Edit your Codex config

Open ~/.codex/config.toml (create it if it doesn’t exist) and add:
[mcp_servers.hoard]
url = "https://mcp.tryhoard.com/mcp"
2

Run Codex

Start a Codex session:
codex
The first time you use a Hoard tool, Codex opens your browser to sign in. Sign in to Hoard and click Allow.
3

Try it out

Ask Codex:
“use hoard: what’s my repricing scope set to?”
Codex calls Hoard via the connector and reports back.

​
Bearer token (CLI)

The codex mcp CLI does not support OAuth for remote MCP servers. Use your Hoard API key as a bearer token instead.
1

Grab your API key

Open Settings → Account and copy your API key. It’s a 64-character hex string.
2

Register Hoard with Codex

Export the key and register the server in one shot:
export HOARD_API_KEY="<your 64-char key>"
codex mcp add hoard \
  --url https://mcp.tryhoard.com/mcp \
  --bearer-token-env-var HOARD_API_KEY
Make HOARD_API_KEY permanent by adding the export line to your shell rc file (~/.zshrc, ~/.bashrc).
3

Verify

codex mcp list
The hoard entry should now show Auth: Bearer (env) instead of Auth: Unsupported.
4

Try it out

Ask Codex:
“use hoard: what’s my repricing scope set to?”

​
Revoking access

  • OAuth path: Open Settings → Assistants in Hoard and click Revoke next to the Codex entry.
  • Bearer-token path: API keys can’t be rotated or revoked from Settings today — email support@tryhoard.com to rotate or revoke your key.