Quick start guide

Turn your existing i18n setup into a team workflow

Run npx i18nexus-cli init to create or connect an i18nexus project for apps using i18next, next-intl, and other popular i18n libraries.

$npx i18nexus-cli init
Account and project setup
Existing translation JSON import
Dashboard workflow for the team
MCP setup for AI coding agents
One command setup

Run the init command

Run this from the root of your app. Follow the prompts to sign up or sign in, create the i18nexus project, import existing strings, and finish the recommended local setup.

npx i18nexus-cli init

What init gives you

Creates your i18nexus project

Init creates the i18nexus project for this app. If you do not have an account yet, the authentication flow lets you sign up; if you do, just sign in.

Detects existing translation files

Whether your app uses i18next, next-intl, or another supported library, init can read your local JSON, infer languages and namespaces, and import your existing translations.

Sets up local sync

Init can add scripts for pulling translations before builds and listening for updates from both dashboard edits and MCP changes.

Configures the MCP

Add project-scoped MCP config and agent instructions for Claude, Codex, or both, with an access token scoped for your workflow.

What you get when it finishes...

Your app's translations are now organized in i18nexus, with automatic AI translation that uses your string context. Your team can edit, review, verify, and track changes from one dashboard. Edits made in i18nexus will now sync live to local development environments. Production builds will pull the latest translations automatically at build time....and that's it! No further configuration needed.

Local sync

How does i18nexus sync translations?

Init installs i18nexus-cli as a dev dependency and updates your package.json so local translation files stay current during development and every build starts with the latest translations.

"scripts": {
  "dev": "concurrently -p none \"next dev\" \"i18nexus listen\"",
  "prebuild": "i18nexus pull",
  "build": "next build",
  "start": "next start",
  "lint": "next lint"
}

During development

i18nexus listen runs next to your dev server and opens a live connection to i18nexus. When strings are added, edited, or deleted from the dashboard or through the MCP, your local JSON files are refreshed automatically.

During builds

i18nexus pull downloads the latest generated translation files. Init adds it as prebuild, so npm runs it automatically before npm run build.

Keep the source of truth clear

Do not maintain source copy by editing generated JSON files. Use the dashboard or MCP to change source-language strings in i18nexus, then sync the generated output your app needs.

Team workflow

Use the dashboard and MCP together

These workflows are complementary. Both write to i18nexus, which stays the source of truth for source strings and translations.

Use the dashboard for team editing and review

The dashboard is the shared workspace for source strings, languages, namespaces, descriptions, and translation review.

  • Add and edit source-language strings without touching app code.
  • Review AI-generated translations and confirm what is ready.
  • Use descriptions as translator notes and AI context when the project setting is enabled.
  • Invite teammates who should manage copy without working in a code editor.

Use the MCP while AI agents edit code

The MCP gives AI coding agents a structured way to create, search, and update i18nexus source strings while they work in your app.

  • Agents add user-facing text to i18nexus instead of editing generated local JSON.
  • String descriptions can include where text appears and how the UI uses it.
  • Project-scoped config keeps the agent pointed at the right i18nexus project.
  • Token scopes let you decide whether agents can add, update, move, or delete strings.
Read the MCP guide

Related references

Level up your localization

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

Get started