Problem
The web UI (launched via --ui=true) has all labels, tooltips, and navigation text hardcoded in English. For non-English-speaking developers — especially in China, where MCP tooling is rapidly growing — this creates an unnecessary friction layer.
Proposal
Add basic i18n support to the embedded HTTP server:
- Language detection: auto-detect via
Accept-Language header, fallback to en
- Config override: allow
codebase-memory-mcp config set ui-lang zh to pin a language
- Scope: start with UI chrome only — sidebar labels, search placeholder, tooltips, button text. Node labels remain as-is (source-derived metadata)
Motivation
- China has one of the largest developer populations globally
- MCP tooling adoption is accelerating in the Chinese AI coding community
- The graph data is language-agnostic — the UI shouldn't be the bottleneck
Willing to contribute
If you're open to this, I can help with the Chinese translation file — just point me to the template.
Problem
The web UI (launched via
--ui=true) has all labels, tooltips, and navigation text hardcoded in English. For non-English-speaking developers — especially in China, where MCP tooling is rapidly growing — this creates an unnecessary friction layer.Proposal
Add basic i18n support to the embedded HTTP server:
Accept-Languageheader, fallback toencodebase-memory-mcp config set ui-lang zhto pin a languageMotivation
Willing to contribute
If you're open to this, I can help with the Chinese translation file — just point me to the template.