io.github.fabkho/nuxt-i18n-mcp

Official

by fabkho · TypeScript

MCP server for managing i18n translations in Nuxt projects.

This MCP server provides functionality for managing i18n translations in Nuxt projects. It is positioned as an i18n toolkit intended for AI agents and large monorepos, focusing on tasks related to translation keys across multiple locales.

🛠️ Key Features

Manage i18n translations for Nuxt projects
Find missing translation keys
Remove dead translation keys
Rename translation keys across locales and layers

🚀 Use Cases

i18n maintenance in Nuxt applications
AI agent workflows that need translation key validation
Monorepo-wide i18n updates across multiple locales

⚡ Developer Benefits

Helps keep locale files consistent by addressing missing and dead keys
Supports bulk renaming across every locale and layer at once

⚠️ Limitations

The available description does not specify supported locales, configuration details, or available MCP tools and methods.

Topics

i18nmcp-servernuxtlaravelai-agentclaudeclicursordeveloper-toolslocalizationmcptranslationvue

README.md3 KBView 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

Package	Version	What it is
@the-i18n-kit/cli		The CLI, and the library every other surface is built on
@the-i18n-kit/mcp		MCP server, for AI coding agents
@the-i18n-kit/nuxt		Publishes the layer graph Nuxt already resolved

A GitHub Action and a GitLab CI template ship from this repository too.

Quick Start

bash

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 yet

For an AI agent, point your MCP host at the server:

json

{
  "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.


Why this toolkit	Who it is for, and who it is not
Monorepos and layers	The consumer graph, shared libraries, misplaced usages
Frameworks	Nuxt, Laravel, Vue, React/Next, generic
Configuration	Where it lives, precedence, every field
CI/CD	The Action and the GitLab template
CLI · MCP tools	Generated reference

Development