Skip to content

MCP

Connect MCP Clients

Use one local Wenlan memory layer from Claude Code, Codex, Cursor, Claude Desktop, Gemini CLI, and other MCP clients.

Qi-Xuan LuUpdated 4 min read

At a glance

01

Wenlan's daemon is the local source of truth; wenlan-mcp is the bridge MCP clients launch.

02

Claude Code users should start with the plugin. Other clients should run Wenlan setup first, then let the CLI add the MCP server config.

01

How the pieces connect

The daemon runs locally and owns memory. wenlan-mcp is the connector MCP clients spawn when they need Wenlan tools.

Once connected, a client can load context, capture, recall, distill, confirm, forget, and diagnose memory.

02

Set up the local runtime

Run this once before wiring another MCP client. It prepares the local Wenlan runtime that wenlan-mcp talks to.

Terminal

npx -y wenlan setup

03

Add a client

After setup, ask the Wenlan CLI to write the client-specific MCP configuration. It uses the local wenlan-mcp binary installed beside the CLI, with npm as a fallback when needed.

Terminal

~/.wenlan/bin/wenlan mcp add claude-code
# or: codex, cursor, claude-desktop, vscode, gemini

04

Manual config fallback

If a client only accepts a raw JSON configuration, point it at the local MCP connector that setup installed. Use wenlan mcp add --dry-run to see the exact path for your machine.

If the daemon is running on a non-default local URL for development, wenlan-mcp also accepts --origin-url. Keep normal users on the default 127.0.0.1:7878 path.

mcpServers

{
  "mcpServers": {
    "wenlan": {
      "command": "/Users/you/.wenlan/bin/wenlan-mcp"
    }
  }
}

05

Non-default daemon URL

Most users should not need this. It is for development or isolated testing when wenlan-server is intentionally running on a different local port.

Use it together with isolated data so an MCP client does not accidentally talk to the wrong daemon.

MCP connector

wenlan-mcp --origin-url http://127.0.0.1:7879

06

Claude Code

The Claude Code plugin is the most complete path because it includes slash commands, setup checks, and the daily workflow around the MCP server.

After installing the plugin, restart Claude Code if prompted, then run /init.

Claude Code

/plugin marketplace add 7xuanlu/claude-plugins
/plugin install wenlan@7xuanlu
/init

07

Other clients

Codex, Cursor, Claude Desktop, Gemini CLI, and other MCP clients can use wenlan mcp add when the client is supported.

The settings screen differs by client. The important part is that the client launches the Wenlan MCP connector installed by setup.

08

Verify the connection

After connecting a client, run its available Wenlan doctor or recall tool. Then capture one small durable fact and recall it from another session or client.

If that round trip works, the client is using the same local memory layer.

Next

Agent Profiles

Inspect the AI clients and local tools that write to Wenlan, then manage source attribution, enabled state, and trust from the CLI.

Read next