Model Context Protocol

i18nexus MCP

Give AI coding agents a direct, structured way to manage your i18nexus source strings while keeping them available in a user-friendly dashboard for your whole team.

Set up MCP View package

AI agent edits app code

MCP creates and updates source strings in i18nexus

i18nexus organizes strings and translates with context

What the MCP does

The i18nexus MCP connects AI coding tools to your project so they can manage copy through i18nexus while they work in your app.

Writes to i18nexus, not local JSON files

Agents create, search, update, move, and delete source-language strings through the i18nexus API instead of hand-editing generated translation files.

Adds app-specific context

New strings include notes like where the text appears and how it is used, giving i18nexus AI translation better context than an isolated phrase.

Fits your existing workflow

Your team still gets dashboard review, namespaces, plural handling, and AI translation in i18nexus. If your app stores translation files locally, the i18nexus CLI handles that syncing.

Source of truth stays clear

The MCP manages source-language base strings in i18nexus. Generated app translation JSON is output, not the place where source copy should be maintained.

Setup

The recommended setup runs the official package with npx. You need an i18nexus project API key and a personal access token for write operations.

{
  "mcpServers": {
    "i18nexus": {
      "command": "npx",
      "args": ["-y", "@i18nexus/mcp"],
      "env": {
        "I18NEXUS_API_KEY": "<PROJECT_API_KEY>",
        "I18NEXUS_PERSONAL_ACCESS_TOKEN": "<PERSONAL_ACCESS_TOKEN>"
      }
    }
  }
}

Project API key

Identifies the i18nexus project your app is connected to. Project-scoped setup is usually best so each repository points at the right project.

Personal access token

Authorizes membership-protected reads and write tools. Use scopes to choose whether an agent can create, update, or delete strings and namespaces.

Recommended agent instruction

Add this guidance so your AI coding assistant knows that i18nexus is the source of truth for app text. Place it in your project's agent instruction file, such as AGENTS.md or CLAUDE.md. Feel free to edit, add, or remove details to match your team's specific workflow.

Recommended project instruction

AGENTS.md or CLAUDE.md

## i18nexus i18nexus is the source of truth for translations. Do not edit local translation JSON files directly. For user-facing text changes, use the i18nexus MCP to add or update source-language strings. Call `get_i18nexus_mcp_guidance` for detailed rules. If the MCP is unavailable or lacks the required token scope, stop and tell the user instead of editing translation files. Before running `i18nexus pull` after MCP string changes, check package.json for an `i18nexus listen` script. `i18nexus listen` automatically pulls translation JSON updates when strings change, so a manual pull is usually unnecessary while it is running. If `listen` is configured, do not pull unless the user explicitly asks. If `listen` is not configured, ask whether they are already running `i18nexus listen` in another shell and whether they want you to pull automatically after changes.

Use the MCP alongside the dashboard, API, and CLI

The MCP is the agent-friendly layer for source string management. Your team can still review and edit content in the dashboard, fetch generated translation JSON through the API, and run the CLI to pull local files before builds or during development.

Read API docs Open npm package

Level up your localization

It only takes a few minutes to streamline your translations forever.

Get started