Connect LiquidLM in Claude Code

User-scoped HTTP MCP with pinned OAuth scopes, search verification, and restart persistence.

Prerequisites

  • Claude Code installed (2.1.220 verified on 2026-07-26).
  • A LiquidLM account with indexed vault content.
  • This guide is for Claude Code only — Claude web reaches the same endpoint but has no verified walkthrough yet (see the hub status table).

Add the HTTP MCP server

Register a user-scoped server with pinned OAuth scopes so the connection follows you across projects:

claude mcp add-json --scope user liquidlm '{"type":"http","url":"https://mcp.liquidlm.com/v1/mcp","oauth":{"scopes":"mcp profile email"}}'

Sign in with OAuth

  • Claude appends offline_access for token refresh automatically.
  • claude mcp list shows the server once the browser flow completes.
claude mcp login liquidlm

Verify search_knowledge

Ask Claude Code to search a distinctive item you own:

  • Inspect the tool call: search_knowledge should return grounded results with knowledge IDs and excerpts.
  • Restart Claude Code and repeat the search — OAuth persistence passed on 2026-07-26.

Example prompt

Search LiquidLM for the incident review from last quarter.

Write tools and alternatives

For Cursor and other clients, the managed CLI path stays the shortest route:

  • put_knowledge and forget_knowledge require write grants on the target vault.
  • Use a PAT only for headless CI; never embed secrets in claude config files.
liquidlm login
liquidlm mcp install --client cursor

Assistants hub

CLI setup