Skip to content

Summary

Official hosted MCP server for the Locize translation management system: check translation progress, translate with glossary context and add keys from your code.

Features

  • Hosted streamable HTTP server, OAuth sign-in or personal access token
  • Finds missing and outdated translations per language and namespace
  • Translates with the project's glossary, style guide, translation memory and screenshots
  • Adds keys from code and updates translations under the project's roles and review rules
  • Destructive tools are flagged so clients confirm before running them

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Locize" tools will be available.
{
  "mcpServers": {
    "locize": {
      "type": "http",
      "url": "https://mcp.locize.app"
    }
  }
}

Description

The Locize MCP server connects AI assistants and coding agents to your projects in Locize, the translation management system from the creators of i18next. It is hosted by Locize at https://mcp.locize.app over streamable HTTP, so there is nothing to install or run, and it acts with your own account, roles and project rules.

What it can do
  • Show projects, languages and translation progress, and find missing or outdated translations before a release.
  • Read translations as your team edits them and as your app receives them from the CDN.
  • Translate and review with project context: glossary terms, style guide, translation memory and screenshots of where a string appears.
  • Add new keys from your code and update translations, with every change recorded in the project history.
  • Start an AI review of existing translations and read its proposals; a person accepts or declines them in Locize.
  • Manage languages, project structure and publishing. Tools that overwrite or remove content are marked destructive, so the client asks before running them.
Who it is for

Development and localisation teams already using Locize (or i18next with Locize as the backend) who want their coding agent to keep translation files in step with code changes, or a translator who wants to work through an assistant.

Requirements

A Locize account with access to at least one project (14-day free trial). Reading works for every project member; writing needs a matching role. Clients sign in with OAuth 2.0 on first connect; clients without OAuth can send a personal access token as Authorization: Bearer <token>. Claude users can also add it from Claude's connector directory.

Related MCP Servers

See all Locize alternatives

MCP: DeepL

by DeepL

DeepL's official MCP server: translate text and whole documents, rephrase copy with a chosen style and tone, and reuse your account's glossaries and style rules.

Featured

Google's official MCP server for the Home ecosystem — let an agent list your homes and devices, read live trait state, run actions and query event history over OAuth.

MCP: Canva

by Canva

Featured

Canva's official remote MCP server — generate and edit designs, search your library, manage assets and brand kits, and export to PDF, PNG, PPTX or MP4.

Featured

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Browse all MCP servers →