MCP Integration
larkx MCP Server for Claude Code
Connect once, get 6 instant code navigation tools — no file reading required.
What is MCP?The Model Context Protocol (MCP) is an open standard that lets AI clients like Claude Code connect to external tool servers. larkx implements MCP so Claude Code, Cursor, Continue, and any MCP-compatible client can query your codebase index without reading source files.
How it works
Claude Code's VS Code extension reads a file called .mcp.json in your project root. Each entry tells the extension how to spawn an MCP server. When you open the project, Claude Code asks for approval, then connects.
- 1
Make sure larkx is installed
bashnpm install -g larkx larkx --version - 2
Create .mcp.json (or let init do it)
If you ran
larkx init, this file already exists. Otherwise create it manually in the project root:.mcp.json{ "mcpServers": { "larkx": { "command": "larkx", "args": ["mcp"] } } }If
larkxis not on your PATH, point at the bin directly:json{ "mcpServers": { "larkx": { "command": "node", "args": ["C:\\path\\to\\larkx\\bin\\larkx.js", "mcp"] } } } - 3
Reload VS Code
bashCtrl+Shift+P → Developer: Reload Window(macOS: Cmd+Shift+P)
- 4
Approve the server
Claude Code will show a prompt asking you to approve the larkx MCP server for this project. Click Allow. Once approved it auto-connects in future sessions.
- 5
Verify
Open the Claude Code chat and ask:
"Which MCP servers do you have?"
The response should include
larkxwith 6 tools listed.
Common scopes
| Scope | File | When to use |
|---|---|---|
| Per project | .mcp.json in repo root | Different MCP servers per project (recommended) |
| Global (CLI only) | claude mcp add | Terminal Claude Code, all projects |
| Global (VS Code) | Not supported as of v0.1 | Use per-project .mcp.json instead |
Next steps
- Global setup for terminal Claude Code
- Set up Cursor, Copilot, Codex, Gemini
- UserPromptSubmit hook, make Claude always use MCP first