Server facts
i18next-mcp-server
Project
- Author
- gtrias
- Repository
- github.com/gtrias/i18next-mcp-server
- License
- Not specified
- Category
- Files & Documents
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 12
- Last commit
- Data as of
Tags
- ai tools
- i18next
- l10n
- mcp server
- translations
Overview
For i18next projects, translation maintenance involves both the keys referenced in source code and the resources stored for each language. i18next-mcp-server exposes tools that let assistants such as Cursor inspect that work through MCP. Project information and file listings provide context, while health checks and JSON validation examine translation resources. Coverage reports, quality analysis, and key usage analysis offer separate views of the translation data. A code scanner identifies missing translation keys, and another tool lists gaps by language and namespace for targeted work.
Updates can focus on a single key or on broader synchronization. The key-creation tool accepts values for selected languages and namespaces. Synchronization tools support copying selected missing keys from a source language to target languages, synchronizing missing entries across languages with sorted structure, or adding all missing keys. Translation data can also be exported in multiple formats. Configuration covers the project root, locale directory, source language, and supported language codes. The documented Cursor setup uses these settings, and the server communicates over stdio.
i18next-mcp-server setup notes
- i18next-mcp-server records stdio only; confirm a network transport upstream before planning remote access.
- i18next-mcp-server has no recorded license; confirm reuse terms in its repository.