MultiLocale

Audit and manage localized product copy

Review localization projects, find and inspect phrase keys across locales, audit missing or duplicate translations, export locale dictionaries, and apply approved project, phrase, sharing, or locale changes in your authenticated MultiLocale organization. Inline views summarize a project and one exact phrase key.

MCP connector

Server URL: https://mcp.multilocale.com/mcp
Login: OAuth
Protocol: MCP 2026-07-28 · Skills
Instructions: Localization workspace with multilocale
Interactive workspace
Use with no arguments when the user wants to open the product and browse visually. It is a read-only sidebar entrypoint with up to 100 items, using the same tenant authorization as the other tools. Selection shares bounded entity context with the host; subsequent writes still require their normal approval.
What this connector can and cannot do
Read this before planning any work. The Multilocale connector is remote and OAuth-scoped: it can read and write translation data, but it cannot see or edit the user's codebase.
| It can | It cannot | | ------------------------------------------------------------------------- | ---------------------------------------------------------- | | Read and write translation data — projects, locales, phrases, team roster | Read, search, write or diff any file on the user's machine | | Machine-translate one phrase, or every phrase of a new locale | Extract the strings an app currently hard-codes | | Export a locale dictionary as bounded, paginated JSON | Write a translation file into a repository | | Audit coverage and duplicate source copy inside a project | Run a command, install a package, or open a pull request |
So "localize my app" is not a request this connector can complete on its own. Reading the strings a codebase already contains, and writing translation files back into it, is the job of the multilocale CLI (npx multilocale) — run by the user, or by an agent that does have shell and filesystem access, such as Claude Code, Codex or Cursor. multilocale import uploads a codebase's existing flat JSON or Android strings.xml; multilocale download writes every locale back out.
When a user asks for a whole app to be localized:

Tools

Reads data11

Deletes or can't be undone7

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.multilocale.com/mcp

OAuth

Protocol

MCP 2026-07-28 · Skills

Instructions

Localization workspace with multilocale

Interactive workspace

Use with no arguments when the user wants to open the product and browse visually. It is a read-only sidebar entrypoint with up to 100 items, using the same tenant authorization as the other tools. Selection shares bounded entity context with the host; subsequent writes still require their normal approval.

What this connector can and cannot do

Read this before planning any work. The Multilocale connector is remote and OAuth-scoped: it can read and write translation data, but it cannot see or edit the user's codebase.

| It can | It cannot | | ------------------------------------------------------------------------- | ---------------------------------------------------------- | | Read and write translation data — projects, locales, phrases, team roster | Read, search, write or diff any file on the user's machine | | Machine-translate one phrase, or every phrase of a new locale | Extract the strings an app currently hard-codes | | Export a locale dictionary as bounded, paginated JSON | Write a translation file into a repository | | Audit coverage and duplicate source copy inside a project | Run a command, install a package, or open a pull request |

So "localize my app" is not a request this connector can complete on its own. Reading the strings a codebase already contains, and writing translation files back into it, is the job of the multilocale CLI (npx multilocale) — run by the user, or by an agent that does have shell and filesystem access, such as Claude Code, Codex or Cursor. multilocale import uploads a codebase's existing flat JSON or Android strings.xml; multilocale download writes every locale back out.

When a user asks for a whole app to be localized:

Tools