
Nuxt I18n Mcp
io.github.fabkhoPublished by GitHub account fabkhov1.0.1Updated Oct 24, 2026
MCP server for managing i18n translations in Nuxt projects.
Overview
A local MCP server that lets an AI coding agent manage i18n translations in Nuxt and other projects: find missing keys, remove dead ones, and rename across all.
- What you can do
- Inspect translation coverage per locale and per layer, and list keys that are not translated yet, from the agent or terminal workflow it wraps. Find missing translation keys across locales and layers. Detect dead keys and remove them. Rename keys across every locale and layer at once. Work with the layer graph Nuxt resolves, including shared libraries and misplaced usages.
- When to use it
- Use it when maintaining translations in a Nuxt project or a large monorepo with multiple locales and layers, and you want an agent to report coverage, find missing or dead keys, or perform bulk renames.
- Requirements
- Runs locally over stdio, typically launched with npx from the npm package. The README's quick start installs a CLI globally and runs an init step to write a config from what it detects; a config file is expected. Node.js and npm are needed. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Nuxt I18n Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
For an AI agent, point your MCP host at the server:
→ 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
DEBUG=1 enables verbose logging to stderr. See CONTRIBUTING.md.
License
Source: README.md at commit 253bed0
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts