|
Documentation
Book a DemoPlatform
PlatformMCPCLI
APIWorkflows
GuidesChangelog

Lingo.dev CLI

  • How it works
  • Setup
  • Quick Start
  • Monorepos

Configuration

  • Supported Formats
  • i18n.json
  • i18n.lock
  • Supported Locales

Features

  • Existing Translations
  • Adding Languages
  • Overrides
  • Translator Notes
  • Translation Keys
  • Key Renaming
  • Key Locking
  • Key Ignoring
  • Key Preserving
  • Extract Keys with AI

Performance

  • Large Projects
  • Parallel Processing

Retranslation

  • Automatic Retranslation
  • Retranslation
  • Remove Translations

Extract Keys with AI

Max PrilutskiyMax Prilutskiy·Updated 30 days ago·2 min read

The Lingo.dev React MCP gives AI coding assistants the tools to set up internationalization in your React codebase — locale-aware routes, language switcher, and locale detection — from a single prompt. Inspired by the Sequential Thinking MCP, it breaks i18n setup into a guided checklist the agent follows step by step, so keys and translation infrastructure are extracted and wired up automatically.

Not to be confused with the Lingo.dev MCP

The Lingo.dev React MCP is focused on scaffolding i18n in React codebases. The separate Lingo.dev MCP is for working with localization engines (glossaries, brand voices, scorers, model configs). This page is about the React MCP.

How it works#

The Lingo.dev React MCP server exposes four tools to the agent:

ToolPurpose
i18n_checklistA step-by-step implementation guide that coordinates the entire setup. The agent calls it at each step to know what to do next.
get_project_contextCaptures the project's architecture — framework, router, directory structure — to inform the implementation strategy.
get_framework_docsRetrieves official framework documentation for the detected framework (Next.js, React Router, TanStack Start).
get_i18n_library_docsRetrieves documentation for i18n libraries (e.g., react-intl) used during provider and component setup.

The i18n_checklist tool is the coordinator. It walks the agent through 13 steps — from project analysis through locale routing, translation setup, language switcher, and build validation.

What gets implemented#

A typical Lingo.dev React MCP-guided setup produces:

  • Locale-aware routes - URLs prefixed with the active locale (/en/about, /es/about)
  • Language switcher - A UI component for switching between supported locales
  • Locale detection - Automatic detection of the user's preferred language
  • Translation infrastructure - Provider setup, translation files, and helper functions with keys extracted from your components

Supported frameworks#

FrameworkVersions
Next.js App Routerv13-16
Next.js Pages Routerv13-16
TanStack Startv1
React Routerv7

Usage#

Once the Lingo.dev React MCP is connected to your AI coding assistant, prompt it:

Set up i18n

Or specify locales upfront:

Set up i18n with the following locales: en, es, and pt-BR. The default locale is "en".

The agent calls i18n_checklist to start, then follows the guided steps — calling the other tools as needed. The result is a working i18n setup tailored to your framework and project structure.

AI-assisted coding is inherently non-deterministic. The Lingo.dev React MCP improves consistency through its checklist-driven approach, but exact results may vary between runs.

Next Steps#

React MCP overview
How the Lingo.dev React MCP works and what it implements
Setup
Connect the Lingo.dev React MCP to your AI coding assistant
Claude Code
Set up in Claude Code
Cursor
Set up in Cursor

Was this page helpful?