Connect LiquidLM in Claude Desktop
Claude Desktop setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
Native OAuth — default
In Claude, open Customize → Connectors → Add custom connector. Enter the LiquidLM endpoint and complete OAuth. Organization policy may require an owner to enable custom connectors. Remote connectors also work through Claude web; they are hosted connections.
https://mcp.liquidlm.com/v1/mcpCLI-managed OAuth — preferred fallback
This alternative is for the local desktop application. Run LiquidLM login, then open Claude Desktop Settings → Developer → Edit Config and merge the stdio entry. Restart Claude Desktop. Use an absolute path to liquidlm if the application cannot find it on PATH.
npm install -g @liquidlm/cli@latest
unset LIQUIDLM_API_TOKEN LIQUIDLM_TOKEN
liquidlm login
liquidlm whoami{
"mcpServers": {
"liquidlm": {
"command": "liquidlm",
"args": [
"mcp",
"serve"
]
}
}
}PAT — 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.
Claude Desktop’s remote connector UI does not provide a documented arbitrary bearer-header field. Use the same local proxy configuration instead, launching the application with LIQUIDLM_API_TOKEN in its environment. The proxy accepts LIQUIDLM_TOKEN as an alias. On macOS, quit the app first and launch its executable from a terminal where the secret has already been injected; opening it from Finder does not inherit shell variables. This example assumes the standard application location.
{
"mcpServers": {
"liquidlm": {
"command": "liquidlm",
"args": [
"mcp",
"serve"
]
}
}
}# LIQUIDLM_API_TOKEN must already be injected into this terminal.
/Applications/Claude.app/Contents/MacOS/ClaudeClaude web and mobile limitations
The local CLI and PAT proxy alternatives require Claude Desktop on your machine. Claude web and mobile cannot launch liquidlm mcp serve. Use the remote OAuth connector there; do not paste a PAT into the connector URL or OAuth client-secret field.
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.