Connect LiquidLM in Claude Code
Claude Code setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
Native OAuth — default
Add the remote server, open Claude Code, and use /mcp to complete OAuth authorization. Remove an existing registration before changing modes: claude mcp remove liquidlm --scope user.
claude mcp add --transport http --scope user liquidlm https://mcp.liquidlm.com/v1/mcpclaude
# In the interactive session: /mcpCLI-managed OAuth — preferred fallback
Log in with LiquidLM and configure Claude Code to launch the local proxy.
npm install -g @liquidlm/cli@latest
unset LIQUIDLM_API_TOKEN LIQUIDLM_TOKEN
liquidlm login
liquidlm whoamiclaude mcp add --transport stdio --scope user 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.
For a project-scoped setup, merge this entry into .mcp.json. Claude Code expands ${LIQUIDLM_API_TOKEN} in headers. Remove any conflicting user-scoped entry before using it.
{
"mcpServers": {
"liquidlm": {
"type": "http",
"url": "https://mcp.liquidlm.com/v1/mcp",
"headers": {
"Authorization": "Bearer ${LIQUIDLM_API_TOKEN}"
}
}
}
}Verify 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.