Phrase API MCP. Manage keys, locales, and projects without leaving your editor.

Phrase API MCP Server: Your localization workflow, handled.

You don't wanna open the Phrase web UI just to tweak a few strings or set up a new project. This server hooks your AI client right into your entire software translation lifecycle. You manage everything—from creating brand-new keys that live in your codebase all the way through downloading final XLIFF files.

Your agent handles complex localization tasks using natural language, so you never leave your IDE.

Project Management: Setting Up and Tearing Down Workspaces

create_project: You can set up an entirely new localization project under your Phrase account when you need one. list_projects: Need to see what projects are active? This tool gives you a simple list of every single thing you've got running. get_project: If you know the ID, this fetches all the full status and metadata for that project.

You can modify core settings using update_project, like renaming it or changing its primary scope. Conversely, if a project is dead weight, delete_project wipes out the entire thing—it's permanent, so be careful.

Target Language (Locale) Control: Managing Supported Languages

The server gives you total control over your supported languages. list_locales: This tool shows every language setting configured for a specific project. get_locale: Need the details on just one language? Use this to fetch all the info for that single locale. You can add new target languages using create_locale, or you can use update_locale if you need to change its settings, maybe renaming it or updating its default status.

If a language is totally unnecessary, delete_locale removes the whole setting and cleans out all associated translations.

Key Management: The Source Code Strings

list_keys: This tool lets you pull up every single translation key tied to a project. get_key: You can retrieve all details for one specific, existing translation key if you need them. When your codebase adds a brand-new string that needs translations, create_key generates it as a unique key ready for action.

If a key is obsolete or wrong, delete_key removes it—remember, this one's tricky.

Translation Data: Inputting and Manipulating Text

You don't have to manually type everything in. create_translation: This lets you input a brand-new translated value for a specific key/locale combo. You can change that actual text later using update_translation. If the source data changes, you modify it with update_key to update the key's metadata or definition. To keep your translations fresh from outside sources, use upload_file to ingest external localization files, like spreadsheets, into a project.

Retrieval and Export: Getting What You Need

list_translations: This shows you all the current translation strings available for a specific key and project. download_file: When it’s time to deploy, this tool pulls down all translations into specified formats like JSON or XLIFF. get_locale also helps pull detailed info about one language setting within a project.

The Bottom Line: Core Capabilities in Action

Your agent can list every active software localization project you own. It'll add brand-new, unique strings—the keys—to your codebase that need translations. You manage the supported languages by creating or updating the list of locales for any given project. When text changes, it updates existing localized string values for a key and locale.

Finally, when development needs files, it pulls down all translations for a project into specific file formats needed for deployment.