Connect LiquidLM in Codex
Codex setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
Native OAuth — default
Register the remote endpoint and complete browser authorization. If replacing an existing server, remove that registration first with codex mcp remove liquidlm.
codex mcp add liquidlm --url https://mcp.liquidlm.com/v1/mcp
codex mcp login liquidlm
codex mcp listCLI-managed OAuth — preferred fallback
After login, register the local command. Codex starts the CLI proxy over stdio.
npm install -g @liquidlm/cli@latest
unset LIQUIDLM_API_TOKEN LIQUIDLM_TOKEN
liquidlm login
liquidlm whoamicodex mcp add liquidlm -- liquidlm mcp servePAT — last fallback
Use a PAT only when native OAuth and CLI-managed OAuth are unsuitable. Create a token in LiquidLM with only the required actions and vaults, and inject LIQUIDLM_API_TOKEN through your secret manager or process launcher. Keep the actual value out of config files and shell history.
Codex stores an environment-variable name, not the token value. Inject the variable before launching Codex.
codex mcp add liquidlm --url https://mcp.liquidlm.com/v1/mcp --bearer-token-env-var LIQUIDLM_API_TOKENVerify and recover
Search for a distinctive item in your vault, then call get_knowledge with include_content: true. Check indexing_status and chunks_stale before judging search freshness.
For a failed OAuth refresh, reauthorize once. If failures recur, use CLI-managed OAuth next. Upgrade to CLI 0.1.5 or newer and log in again if an older version lost its refresh token. PAT is the last fallback.
Select one connection mode. Replace the existing liquidlm server entry when switching, preserving unrelated servers. Do not register duplicate connections.