Lingo.dev MCP

Using the Lingo.dev Model Context Protocol (MCP) server

Introduction

Model Context Protocol (MCP) servers enable AI coding assistants, such as Cursor and Claude Code, to integrate with external tools.

Lingo.dev MCP provides tools for setting up i18n features in web apps, including but not limited to:

  • Routes that contain the active locale (e.g., /en, /es, etc)
  • A language switcher for switching between the supported locales
  • Automatic detection of the user's locale

The goal is to make it trivial to set up the foundations of i18n in your codebase. Just set up the MCP, type a single prompt — "Set up i18n" — and watch the magic happen.

Live demo

Watch this short video to see Lingo.dev MCP in action:

Supported frameworks

Lingo.dev MCP currently supports the following React-based frameworks:

  • Next.js App Router (v13-16)
  • Next.js Pages Router (v13-16)
  • TanStack Start (v1)
  • React Router (v7)

Additional framework support is planned for future releases.

Initial setup

To set up the Lingo.dev MCP in your AI coding assistant, see the quickstart guides:

Using the MCP

Once the MCP is enabled, prompt the AI coding assistant to set up i18n in the current codebase.

For example:

Set up i18n

You can also specify the supported locales and the default locale:

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

(If you don't provide this information upfront, the AI should ask you for it.)

Gotchas

  • AI-assisted coding is inherently unpredictable, so exact results may vary. Using the MCP improves results, but can't guarantee flawless execution every single time.