Add LiquidLM to your assistant
Connect verified MCP clients with OAuth. See tested status before you install.
Start here: verified setup guides
Three clients passed a fresh-account production walkthrough. Open the guide for yours and follow the numbered steps — each one lists prerequisites, the exact commands, how to confirm tool discovery, a harmless known-item search, and the headless PAT alternative.
- Connect LiquidLM in ChatGPT — Developer-mode MCP setup with OAuth, tool discovery, and search/fetch verification.
- Connect LiquidLM in Codex — Remote MCP OAuth for Codex CLI with version-specific compatibility notes.
- Connect LiquidLM in Claude Code — User-scoped HTTP MCP with pinned OAuth scopes, search verification, and restart persistence.
OAuth by default
The production MCP endpoint is https://mcp.liquidlm.com/v1/mcp. In an interactive assistant, paste that URL and sign in with your LiquidLM account when the browser opens. You do not need to create or paste an API token.
The OAuth connection inherits your account and active-workspace access. LiquidLM still applies tool scopes and vault permissions on every call, so a client cannot search or change a vault you cannot access.
- Human on web, desktop, or mobile: paste the MCP URL and use OAuth.
- CI or a truly headless process: create a narrowly scoped API token and send it only in the Authorization header.
- Never put a LiquidLM token in a URL, prompt, repository, or checked-in client configuration.
MCP endpoint
https://mcp.liquidlm.com/v1/mcpTested status (2026-08-16)
LiquidLM publishes only clients that passed a fresh-account production walkthrough. Last-tested date and client version are recorded in docs/E2E-Test-Plan.md (MCP OAuth section). Directory approval is separate — custom MCP connections work without a listing.
- ChatGPT web — Works now. OAuth, ten-tool discovery, search, and fetch passed on 2026-07-29.
- Codex CLI — Works now on @openai/codex@0.142.5 (2026-07-26). 0.145.0 was blocked upstream and 0.146.0 is untested; retest before claiming a newer release.
- Claude Code — Works now. OAuth, search_knowledge, and restart persistence passed on Claude Code 2.1.220 (2026-07-26).
- Claude web — Not yet verified. Connecting and tool discovery work; the grounded search and reconnect checks this page requires are still open, so there is no setup guide yet.
- Claude Desktop (remote connector) — Not yet tested with LiquidLM. Anthropic documents account remote connectors; a pass requires a real Desktop walkthrough, not inference from Claude Code.
- Claude mobile — Not yet tested with LiquidLM. It uses the same account connector as Claude web; a pass requires a real walkthrough on a phone.
- Perplexity remote connector — Not yet tested on an eligible account; no working claim.
Clients without a working guide
Claude web completes LiquidLM OAuth and consent and lists the tools. Between 2026-07-26 and 2026-08-05 it failed before any tool call, which we traced to a rule at our own edge blocking requests from AI-client user agents rather than to anything in Claude; that rule is off. What is still missing is evidence, not function: a grounded search inside a real conversation and a disconnect/reconnect check. A setup guide goes up here when both pass.
Perplexity rolls remote connectors out by plan and organization. When an eligible account exposes Settings → Connectors → Add custom connector → Remote, the flow mirrors other OAuth MCP clients: paste the endpoint, choose OAuth and Streamable HTTP, consent, then verify search before enabling write tools.
Directory vs direct MCP
Custom connections work independently of directory review. Claude and ChatGPT marketplace listings are discoverability improvements, not availability gates.