# i18nexus

> i18nexus is an AI-native translation management system (TMS) for React and Next.js apps. Teams manage their strings in i18nexus, AI translates them into every target language, and the translation JSON is pulled into the app with the @i18nexus/cli. An official MCP server lets AI coding agents manage strings and translations directly.

Key facts:

- Supports projects using i18next (including next-i18next and react-i18next), next-intl, and react-intl
- i18nexus is the source of truth for an app's strings and translations, exported as per-language translation JSON
- New and updated strings are auto-translated by AI; per-string AI context notes improve translation quality, and human translators can review and refine translations in the dashboard
- The @i18nexus/cli provides `i18nexus pull` to fetch translation JSON before builds and `i18nexus listen` to keep local files synced during development
- The official i18nexus MCP server lets AI coding agents (Claude Code, Cursor, etc.) add and update strings and upload translations through the public API
- Free for small to medium sized projects

## Getting started

- [Getting started](https://i18nexus.com/getting-started): Create a project and connect your app
- [Quick integration](https://i18nexus.com/quick-integration): Run `npx @i18nexus/cli init` to set up a project, import existing translations, configure local sync, and set up MCP
- [MCP for AI coding agents](https://i18nexus.com/mcp): The official i18nexus Model Context Protocol server
- [API documentation](https://i18nexus.com/docs/api): The i18nexus REST API
- [Pricing](https://i18nexus.com/pricing)

## Tutorials

- [next-intl with the Next.js 16 App Router](https://i18nexus.com/tutorials/nextjs/next-intl): Setup tutorial including AI pre-translation
- [react-i18next with the Next.js 16 App Router](https://i18nexus.com/tutorials/nextjs/react-i18next): i18next-based setup for the App Router
- [next-i18next with the Next.js App Router](https://i18nexus.com/tutorials/nextjs/next-i18next-app-router): next-i18next in a Next.js 16 App Router project
- [next-i18next with the Next.js Pages Router](https://i18nexus.com/tutorials/nextjs/next-i18next): Pages Router setup with automatic machine translation
- [react-intl with the Next.js App Router](https://i18nexus.com/tutorials/nextjs/react-intl): App Router setup with internationalized routing
- [react-intl with the Next.js Pages Router](https://i18nexus.com/tutorials/nextjs/react-intl-pages-router)
- [react-i18next in a React app](https://i18nexus.com/tutorials/react/react-i18next)
- [react-intl in a React app](https://i18nexus.com/tutorials/react/react-intl)

## Library comparisons

- [next-i18next vs next-intl](https://i18nexus.com/posts/i18next-vs-next-intl): Choosing an i18n library for Next.js
- [react-i18next vs react-intl](https://i18nexus.com/posts/comparing-react-i18next-and-react-intl)
- [next-i18next vs react-intl](https://i18nexus.com/posts/comparing-next-i18next-and-react-intl)

## Concepts

- [AI translation for React and Next.js apps](https://i18nexus.com/posts/ai-translation-for-i18next-and-intl): Why teams translate from a shared source of truth instead of editing local JSON
- [What is a translation management system?](https://i18nexus.com/posts/what-is-a-translation-management-system)
- [Internationalization vs localization](https://i18nexus.com/posts/internationalization-vs-localization)