Chris ChengandClaude Opus 5
6e27968bb0
Tool and parameter descriptions were handed to the LLM in Chinese on every runtime regardless of locale: the English metadata table in packages/tools/src/tool-metadata.ts had no caller, the desktop translateTool looked up i18n keys that exist in no locale file, and the MCP server had no locale at all. Fill the table for every tool whose definition text is Chinese (37 entries, only translating what the definitions write in Chinese so the two copies cannot drift), and route the four consumers through getLocalizedToolMetadata: the cross-chat agent adapters, the CLI Web agent adapter, the desktop shared tool adapter (replacing the dead translateTool), and the MCP server, which now resolves its locale from config.locale.lang or the system locale for both the standalone binary and the chatlab mcp subcommand. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
chatlab-mcp
ChatLab MCP Server exposes local ChatLab conversation data to MCP clients such as ClaudeCode, Cursor, Codex, and OpenClaw.
It runs over stdio and provides read-only access to imported ChatLab sessions, including session discovery, keyword search, member statistics, time analysis, SQL queries, and conversation context tools.
Quick Start
Use it directly with npx:
npx -y chatlab-mcp
The command starts an MCP stdio server and waits for an MCP client. It does not print a help screen because stdout is reserved for MCP protocol messages.
MCP Client Configuration
Add this server to your MCP client configuration:
{
"mcpServers": {
"chatlab": {
"command": "npx",
"args": ["-y", "chatlab-mcp"]
}
}
}
If you install the package globally, you can also use:
{
"mcpServers": {
"chatlab": {
"command": "chatlab-mcp"
}
}
}
Data Directory
chatlab-mcp reads the same local data directory as ChatLab:
~/.chatlab/
If you configured a custom ChatLab data directory in ~/.chatlab/config.toml, the MCP server will use that configuration automatically.
The server is read-only. It opens existing ChatLab session databases and does not modify chat data.
Available Capabilities
The server registers ChatLab tools for:
- Listing imported chat sessions
- Reading session metadata and database schema
- Searching messages and keywords
- Loading recent messages and message context
- Listing members and member activity
- Analyzing active hours, response time, interaction pairs, and daily active users
- Running read-only SQL queries
- Producing text or JSON output for tool results
Requirements
- Node.js 22.19 or later
- Existing ChatLab data under
~/.chatlab/
better-sqlite3 is installed as a runtime dependency. On platforms without a matching prebuilt binary, npm may need local build tools for native modules.
@node-rs/jieba is optional and improves Chinese word segmentation for keyword-frequency tools. If it is unavailable, core MCP functionality still works.
Package API
Advanced callers can import the shared server core:
import { startMcpServer } from 'chatlab-mcp'
Most users should prefer the npx -y chatlab-mcp command.
Links
- ChatLab: https://github.com/ChatLab/ChatLab
- Model Context Protocol: https://modelcontextprotocol.io/