Manage translation projects, phrases, locales, dictionaries, and team data with secure, organization-scoped tools and interactive translation views.
Scored across 18 tools
Most tools have clearly distinct purposes, but a few overlaps exist: get_project and show_project_overview both retrieve project details, and open_multilocale conceptually overlaps with list_projects/list_phrases as a browsing entry point. Descriptions help differentiate, but an agent may still hesitate on these pairs.
All tool names follow a consistent snake_case verb_noun pattern (e.g., add_project, list_phrases, update_phrase, find_missing_translations). Even multi-word objects like locale_dictionary and project_overview are handled uniformly.
With 18 tools, the set is on the heavier side for a localization API. While most tools serve a purpose, several feel niche or redundant (show_project_overview, open_multilocale, export_locale_dictionary), pushing the count into borderline-heavy territory.
Core CRUD for phrases and projects is present, but there is no delete_project operation, team management is read-only (no invite/remove), and removing a locale requires replacing the entire language list via update_project. These are notable gaps that could cause agent failures for common cleanup tasks.
Use this when someone asks to add a new language to a project and translate their strings into it. Returns the updated language list and how many strings were machine-translated, one per key, all before anything is saved, so a very large project can time out. Not for a language the project already has.
Inputs: locale (required), project (required), model, context. Returns: locale, status, locales, project, +1 more
Use this when someone asks to add a new string or key to their app's translations. Returns the created key with one machine translation per configured locale, made from the source text in the default locale. A key that already exists returns already-exists and is left unchanged. Not for changing an existing translation.
Inputs: key (required), project (required), model, value, +1 more. Returns: key, status, locales, project, +2 more
Use this when someone asks to create a new localization project with a given name and languages. Returns the new project with its default locale and locales; if the name is taken it returns already-exists and creates nothing. Not for adding a language to an existing project.
Inputs: name (required), defaultLocale (required), locales. Returns: status, project
Use this when someone asks to remove a key from their translations. Returns how many language rows were deleted and which other projects shared them; a shared string is deleted permanently for those projects too. Not for removing only one language's translation.
Inputs: key (required), project (required). Returns: key, status, project, sharedProjects, +1 more
Use this when someone wants the key and value pairs of one language, for example to review or copy a translation file. Returns up to 50 entries per call (25 by default) sorted by key, values cut to 500 characters, with nextSkip for the next page. Not for a complete file download, which the MultiLocale CLI provides.
Inputs: project (required), language (required), skip, limit. Returns: skip, status, entries, hasMore, +6 more
Use this when someone wants to clean up a project by finding keys that repeat the same default-language text. Returns up to 25 repeated values with the keys that share them, scanning 1,000 default-locale strings by default and at most 2,000. Not for untranslated strings.
Inputs: project (required), scanLimit. Returns: status, project, scanLimit, duplicates, +5 more
Use this when someone asks which strings are not translated yet, or how complete each language is. Returns completion percentages and up to 25 missing keys per locale, for one locale or up to 10, compared with the default locale. Nothing is translated or written. Not for filling in the missing translations.
Inputs: project (required), language, scanLimit, localeLimit. Returns: status, locales, project, scanLimit, +4 more
Use this when someone asks how one exact key is translated, in every language or in one. Returns that key's text per locale, up to 24 locales and 2,000 characters each, with machine-translation flags and the projects sharing it, and renders a phrase card. Not for searching keys by text.
Inputs: key (required), project (required), language. Returns: key, status, project, translations, +2 more
Use this when someone asks about one localization project, such as which languages it has or its default locale. Returns the project's id, name, default locale, configured locales and creation and edit times. Not for how complete its translations are.
Inputs: projectIdOrName (required). Returns: status, project
Use this when someone asks to see the translation strings in a project, optionally in one language or for one key. Returns up to 100 phrases with id, key, language and value, plus the total count. Not for finding strings by the words they contain.
Inputs: project (required), key, language. Returns: status, phrases, phraseCount, phrasesTruncated
Use this when someone asks which localization projects they have in MultiLocale. Returns each project's id, name, default locale, languages and timestamps, up to 100 projects. Not for listing the strings inside a project.
Inputs: no named parameters. Returns: status, projects, projectCount, projectsTruncated
Use this when someone asks who is on their MultiLocale team or what role each person has. Returns each member's display name and role, up to 100 members (no emails, ids or contact details). Not for inviting or removing people.
Inputs: no named parameters. Returns: status, members, memberCount, membersTruncated
Use this when someone wants to open Multilocale and browse their workspace interactively. Localization projects, strings and translations. Starts with up to 100 items. Not for changing data.
Inputs: no named parameters. Returns: items, truncated
Use this when someone asks to find translation strings that contain a word or phrase, in their keys or text. Returns up to 100 matches with id, key, language and value from a case-insensitive match within one project. Not for one exact key.
Inputs: query (required), project (required), language. Returns: status, phrases, phraseCount, phrasesTruncated
Use this when someone wants a quick overview of one of their localization projects. Returns an overview card with the project's default locale, up to 24 configured locales and timestamps. Not for translation completeness.
Inputs: projectIdOrName (required). Returns: project
Use this when someone asks to fix or change the text of one key in one language. Returns the previous and new text and the projects sharing that string; the change applies in all of them and marks the text as human-edited. Not for adding a new key.
Inputs: key (required), value (required), project (required), language (required). Returns: key, value, status, project, +3 more
Use this when someone asks to change a project's default locale, replace its list of languages, or set its translation context. Returns which fields changed. The language list is replaced as a whole, no strings are translated or deleted, and the project name stays fixed. Not for adding a language with its translations.
Inputs: projectIdOrName (required), context, locales, defaultLocale. Returns: status, project, changedFields
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Add one secure layer between your agents and this server.