Featured · Built-in

MCP Server

Give AI agents direct access to your translation keys via the Model Context Protocol.

Setup

Get MCP Server running

Three steps, no migration. Point it at your project and the first keys land in the dashboard.

InstallAdd the package or the config block. Nothing else in your build changes.
Connect your projectUse the org/project identifier from your dashboard. Keys and languages come from there, not from a local file you have to keep in sync.
ShipPublish once and every locale is a static file on the edge. Copy changes go live without a new deploy.

mcp-config.json

{
  "mcpServers": {
    "better-i18n": {
      "command": "npx",
      "args": ["@better-i18n/mcp"],
      "env": {
        "BETTER_I18N_API_KEY": "your-api-key"
      }
    }
  }
}

Install integration

Surface

What MCP Server gives you

The exact commands, tools and paths you get. Names are what you type, not marketing labels.

listProjects · getProject

Find the project and read its languages, namespaces and coverage before touching anything.

listKeys · getTranslations · getTranslationContext

Read keys, their translations, and the project glossary plus tone rules the agent should follow.

createKeys · updateKeys · setTranslations · deleteKeys

Create keys, edit source text, and write whole translation batches in one call.

proposeLanguages · proposeLanguageEdits

Propose adding or retiring a target language, for a human to approve.

getPendingChanges · publishTranslations

Review pending changes first, then deploy them to the CDN or to GitHub.

getSyncs · getSync · cancelSync

Follow a publish job to completion, or cancel one that is still queued.

Where it fits

How MCP Server works inside Better

Detect

Pull source strings from your codebase or connect your MCP Server repository. Keys arrive in Better with structure and context intact.

Review

Run AI translation, assign human reviewers, and gate approval before any change reaches production. Everything auditable in one place.

Ship

Publish to the CDN edge or push translations back to MCP Server. Copy changes go live without triggering a new app deploy.

Developer-first workflow

Localization lives close to your code — reviewable in pull requests, version-controlled, and part of your existing CI and deploy pipeline.

Less operational drift

Centralize translation updates, review sign-off, and delivery in one workflow instead of spreading work across separate tools and scripts.

Controlled rollout

Decouple translation publishing from code releases. Ship copy changes on your schedule without waiting for the next deploy window.

Questions

Before you connect it

Connect MCP Server today

Free to start. Add the integration, publish once, and see the copy change without a release.

Install integration Read the guide