PluginBench
MCP Server
Active
MIT

io.github.fabkho/nuxt-i18n-mcp MCP Server

io.github.fabkho/nuxt-i18n-mcp

AI-powered i18n translation management for Nuxt projects—find missing keys, remove dead ones, rename across locales.

What is the io.github.fabkho/nuxt-i18n-mcp MCP server?

The i18n-kit MCP server is a translation management tool for Nuxt projects that helps AI agents find missing translation keys, remove unused ones, and rename keys across all locales and layers simultaneously. It integrates with AI coding agents via the Model Context Protocol to automate i18n maintenance tasks in monorepos.

This MCP server exposes translation management capabilities for Nuxt i18n projects. It detects missing translations, identifies dead keys, and enables bulk renaming operations across multiple locales and layers—useful for maintaining consistency in large monorepos and automating translation workflows through AI agents.

How to install io.github.fabkho/nuxt-i18n-mcp

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "nuxt-i18n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "nuxt-i18n-mcp"
      ]
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • status — Check translation coverage per locale and per layer
  • missing — Identify translation keys that are not yet translated
  • find — Locate missing keys across the project
  • remove — Remove dead/unused translation keys
  • rename — Rename translation keys across all locales and layers at once

Use cases

  • Identify missing translations before deployment to catch incomplete i18n coverage
  • Remove dead translation keys to clean up and reduce bundle size
  • Bulk rename translation keys across all locales simultaneously in large monorepos
  • Audit translation status per locale and per layer to track localization progress
  • Automate i18n maintenance tasks via AI agents integrated with your development pipeline

io.github.fabkho/nuxt-i18n-mcp MCP server FAQ

What does the i18n-kit MCP server do?

It provides AI agents with tools to manage translations in Nuxt projects: finding missing keys, removing dead ones, renaming keys across locales, and checking translation coverage per locale and layer.

Is it free?

Yes, the i18n-kit is open source under the MIT license.

How do I install it for use with Claude or Cursor?

Add it to your MCP configuration: {"mcpServers": {"the-i18n-mcp": {"command": "npx", "args": ["@the-i18n-kit/mcp@latest"]}}}

Does it require authentication?

No, it operates locally on your project files and does not require external authentication.

What frameworks does it support?

It is designed for Nuxt but also supports Vue, React/Next, Laravel, and generic i18n setups.

Can it work with monorepos?

Yes, it is built to handle monorepos with multiple layers and understands the consumer graph and shared libraries.

README (reference)

Source of truth, from the repository.

the-i18n-kit

CI License Glama score

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

PackageVersionWhat it is
@the-i18n-kit/clinpmThe CLI, and the library every other surface is built on
@the-i18n-kit/mcpnpmMCP server, for AI coding agents
@the-i18n-kit/nuxtnpmPublishes the layer graph Nuxt already resolved

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 yet

For 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.

Why this toolkitWho it is for, and who it is not
Monorepos and layersThe consumer graph, shared libraries, misplaced usages
FrameworksNuxt, Laravel, Vue, React/Next, generic
ConfigurationWhere it lives, precedence, every field
CI/CDThe Action and the GitLab template
CLI · MCP toolsGenerated reference

Development

pnpm install
pnpm build
pnpm test
pnpm lint
pnpm typecheck

DEBUG=1 enables verbose logging to stderr. See CONTRIBUTING.md.

License

MIT

Related MCP servers

Inspect, validate and surgically edit Tiled map files (.tmx/.tmj) — byte-preserving, 12 tools.

Read-only MCP connector for Facehunch saved reports, access status and available source links.

0
JavaScript
MIT
View repository →

Renamed to FactReason. Now published as io.github.factreason/factreason — please use that entry.

0
MIT
View repository →
FAFactReason logo

Check exact npm/PyPI upgrades for evidence-backed breaking changes; query APIs and components.

0
JavaScript
MIT
View repository →
FAFactum logo

Factum

Active

Auditable memory for AI agents: provenance, cascade retraction, conflict refusal

3
Rust
MIT
View repository →

Search academic expert insights, papers and contributions from Faculti

0
TypeScript
View repository →