Nuxt I18n Mcp
Manage Nuxt i18n translation files and keys from your agent instead of hand-editing locale JSON across the repo.
Overview
io.github.fabkho/nuxt-i18n-mcp is a Build-phase MCP server for managing i18n translations in Nuxt projects from your agent.
What is this MCP server?
- MCP tooling focused on Nuxt i18n translation management
- stdio nuxt-i18n-mcp npm package v1.0.1
- Keeps locale work inside agent-driven edits on Nuxt repos
- Open source at fabkho/nuxt-i18n-mcp on GitHub
- Server version 1.0.1
- Transport: stdio
- registryType: npm nuxt-i18n-mcp
What problem does it solve?
Nuxt locale files sprawl across keys and languages, making agent-assisted edits error-prone without i18n-aware MCP tools.
Who is it for?
Solo builders shipping Nuxt apps who localize in-repo and want MCP help for keys, locales, and i18n file hygiene.
Skip if: React/Next-only codebases, teams using external TMS-only workflows with no Nuxt i18n in git, or non-MCP editors.
What do I get? / Deliverables
Your agent can manage Nuxt i18n translations through a dedicated stdio MCP aligned with your project structure.
- Agent-driven updates to Nuxt locale/translation files
- Consistent i18n key changes across languages in repo
Recommended MCP Servers
Journey fit
How it compares
Nuxt-specific i18n MCP, not a general database or cloud deploy server.
Common Questions / FAQ
Who is io.github.fabkho/nuxt-i18n-mcp for?
Solo and indie developers building Nuxt sites or SaaS who maintain @nuxtjs/i18n or equivalent locale files in the repository.
When should I use io.github.fabkho/nuxt-i18n-mcp?
Use it during build when adding languages, refactoring translation keys, or syncing locale JSON with feature work in Nuxt.
How do I add io.github.fabkho/nuxt-i18n-mcp to my agent?
Install npm package nuxt-i18n-mcp, add a stdio MCP server block in your agent config, and point it at your Nuxt project workspace.