MCP
Connect MCP Clients
Connect Claude Code, Codex, Cursor, Claude Desktop, Gemini CLI, Muse Code, ChatGPT, Claude.ai, Muse, and other MCP clients to Wenlan.
At a glance
01
Choose the Claude Code or Codex plugin, a local MCP client, or Web access for a supported web client.
02
Local clients launch a connector on your computer; web clients use the desktop app's authenticated relay while your device is online.
01
Choose a connection
Choose a plugin for Claude Code or Codex when you want its skills. Other local clients can launch the local MCP connector. Web clients cannot launch that connector: use the desktop app's authenticated Web access instead.
For web access your computer must stay online; requests and results pass through the relay and the connected AI provider.
02
Set up the local runtime
Install Wenlan and complete the first setup before connecting another local client. Web clients need the desktop app and Web access instead of a local stdio connector.
03
Add a client
After setup, ask the Wenlan CLI to write a local client's MCP configuration with wenlan connect <client>. It uses the local wenlan-mcp binary installed beside the CLI, with npm as a fallback when needed.
~/.wenlan/bin/wenlan connect claude-code
# or: codex, cursor, claude-desktop, vscode, gemini04
Manual config fallback
If a client only accepts a raw JSON configuration, point it at the local MCP connector that setup installed. Use wenlan connect --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": {
"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.
wenlan-mcp --origin-url http://127.0.0.1:787906
Claude Code
Install the Claude Code plugin and run /wenlan to check the connection; if it cannot connect, follow the setup prompts.
07
Codex plugin (recommended)
Install Wenlan's Codex plugin with the Codex CLI, then start a new task and run $wenlan. This is the primary Codex path and includes Wenlan's Codex skills.
codex plugin marketplace add wenlan-app/wenlan
codex plugin add wenlan@7xuanlu-wenlan08
Codex MCP-only
After completing setup, use this path when you want MCP tools without the Codex plugin skills.
~/.wenlan/bin/wenlan connect codex09
ChatGPT, Claude.ai, and Muse
1. Web access is experimental. In the desktop app, open Settings > Connections > Web access and turn it on. Choose the whole library or one Space when prompted.
2. Use Add to Claude, Add to ChatGPT, or Other apps. For a custom connector such as Muse, use https://relay.wenlan.app/mcp in the client's MCP connection flow.
3. Start authorization in the client. In Wenlan, check the pairing request and its scope. Search only lets the app search; Search and write also lets it add, edit, and delete memories and pages in the shared scope. Choose a permission and approve only a request you initiated, then finish authorization in the client.
4. Search for an existing item within the shared scope to check the connection. Your device must remain online; revoke the grant or stop Web access to end it.
10
Other local clients
Cursor, Claude Desktop, Gemini CLI, VS Code, and other supported local MCP clients use wenlan connect <client>.
The settings screen differs by client. The important part is that the client launches the Wenlan MCP connector installed by setup.
11
Muse Code
Muse Code, Meta's coding agent CLI, is in the desktop app's tool list. When muse is installed, open Settings > Connections > Add a tool and connect Muse Code with one click. Wenlan writes the entry for you and keeps the other servers in the file, then restart Muse Code.
Without the desktop app, add the entry by hand. Muse Code reads MCP servers from ~/.config/muse/settings.json, under mcp_servers rather than mcpServers. mode: optional lets Muse Code start even when Wenlan is not running. Run /mcp in muse to check that wenlan is connected.
{
"schema_version": 1,
"mcp_servers": {
"wenlan": {
"transport": "stdio",
"mode": "optional",
"command": "npx",
"args": ["-y", "wenlan-mcp", "--agent-name", "muse-code"]
}
}
}12
Verify the connection
In a local client with write access, save a small non-sensitive fact and recall it in a new session. For Search only Web access, search for an existing item within the approved scope. Finding the expected item confirms that the client can reach that shared material.
Next
Wenlan Agent Profiles and Client Attribution
See which AI client wrote a Wenlan memory, inspect source_agent attribution, and manage trust or enabled state.
Read next