Nuxt I18n MCP server
io.github.fabkho/nuxt-i18n-mcp·v1.0.1·11 starsMCP server for managing i18n translations in Nuxt projects.
11 stars52 downloads/wk
Reviews
Write oneNobody has reviewed Nuxt I18n yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Nuxt I18n tools (13, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
add_translationsAdd new translation keys to the specified layer. Provide translations per locale file name. Keys are inserted in alphabetical order. Fails if a key already exists (use update_translations instead).
cleanup_unused_translationsFind translation keys not referenced in source code and remove them. Combines find_orphan_keys + remove_translations in one step. Always does a dry run first unless dryRun is explicitly set to false.
detect_i18n_configDetect the Nuxt i18n configuration from the project. Returns locales, locale directories, default locale, and fallback chain. Call this first before using other tools.
find_orphan_keysFind translation keys that exist in locale JSON files but are not referenced in any Vue/TS source code. Scans a specific layer or all layers. Reports keys that can potentially be removed.
get_missing_translationsFind translation keys that exist in the reference locale but are missing in other locales. Scans a specific layer or all layers.
get_translationsGet translation values for given key paths from a specific locale and layer. Use "*" as locale to read from all locales.
list_locale_dirsList all i18n locale directories in the project, grouped by layer. Shows file count and top-level key namespaces per layer.
remove_translationswrite actionRemove one or more translation keys from ALL locale files in the specified layer. Use dryRun to preview changes before applying them.
rename_translation_keyRename/move a translation key across ALL locale files in a layer. Preserves the value in every locale. Use dryRun to preview changes before applying them.
scan_code_usageScan Vue/TS source files to find where translation keys are referenced. Shows file paths and line numbers for each key. Useful for understanding where a key is used before renaming or removing it.
search_translationsSearch translation files by key pattern (glob/regex) or value substring. Useful for finding existing translations before adding duplicates.
translate_missingFind keys missing in target locales and translate them. Uses the host LLM via MCP sampling if available, otherwise returns context for the agent to translate inline. Uses project config (glossary, translation prompt, locale notes, examples) if available.
update_translationswrite actionUpdate existing translation keys in the specified layer. Provide new values per locale file name. Fails if a key does not exist (use add_translations instead).
Public scan report
scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Nuxt I18n compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Tools
- 13
- the typical server has 7
- Tools that change things
- 15%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 11
- more than 88% of 28,688 servers
- Downloads a week
- 52
- more than 43% of 12,191 servers with a package
What its tools let an agent do: 9 read · 1 create · 2 change · 1 delete
Install Nuxt I18n in Claude Code, Cursor or VS Code
Runs npx -y nuxt-i18n-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add nuxt-i18n-mcp -- npx -y nuxt-i18n-mcp
What the publisher says
From the Nuxt I18n repository's README, as published. We do not edit it. Read it on GitHub
the-i18n-kit
The i18n toolkit for AI agents and large monorepos. Find missing keys, remove dead ones, and rename across every locale and layer at once — from your agent, your terminal, or your pipeline.
📖 Documentation
Packages
A GitHub Action and a GitLab CI template ship from this repository too.
Quick Start
npm install -g @the-i18n-kit/cli
the-i18n-cli init # write a config from what it detects
the-i18n-cli status # coverage per locale and per layer
the-i18n-cli missing # what is not translated yetFor an AI agent, point your MCP host at the server:
{
"mcpServers": {
"the-i18n-mcp": {
"command": "npx",
"args": ["@the-i18n-kit/mcp@latest"]
}
}
}→ Getting started · MCP setup · CLI reference
Documentation
Everything lives on the documentation site. The reference sections are generated from the source they describe, so they cannot drift from it.
Development
pnpm install
pnpm build
pnpm test
pnpm lint
pnpm typecheckDEBUG=1 enables verbose logging to stderr. See CONTRIBUTING.md.
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Nuxt I18n: common questions
- Is Nuxt I18n MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Nuxt I18n safety report
- How do I install Nuxt I18n?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Nuxt I18n need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Nuxt I18n maintained?
- The last commit was 40 days ago (2026-09-25). The latest release is v1.0.1.
- How does Nuxt I18n compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); tools 13 (the typical server has 7); tools that change things 15% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.