Phrase API MCP for AI. Manage keys, locales, and projects without leaving your editor.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Phrase (Software Localization API) connects your AI agent directly to localization projects. Manage full software translation lifecycles—including creating new projects, adding locales, and updating thousands of translation keys—without opening the Phrase web UI or leaving your IDE.
What AI agents can do with Phrase (Software Localization API) Automation
Create key
Generates a brand-new translation string (key) that must be added to the codebase.
Create locale
Adds a new target language/region setting (locale) to an existing project.
Create project
Sets up an entirely new localization project under your Phrase account.
Retrieves a list of every active software localization project you own in Phrase.
Adds brand-new, unique strings (keys) to your codebase that need translations.
Creates or updates the list of supported human languages for a specific project.
Changes an existing localized string value for a given key and locale.
Pulls down all translations for a project into specific file formats needed for deployment.
Ask an AI about this
Waiting for input…
What AI agents can do with Phrase (Software Localization API) MCP Server: 20 Tools for Localization Management
Use these tools to programmatically interact with your localization data. You can list projects, create keys, update translations, and download files—all through natural language prompts.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Phrase (Software Localization API) on VinkiusCreate Key
Generates a brand-new translation string (key) that must be added to the codebase.
Create Locale
Adds a new target language/region setting (locale) to an existing project.
Create Project
Sets up an entirely new localization project under your Phrase account.
Create Translation
Manually inputs a brand-new translated value for a specific key/locale combination.
Delete Key
Removes a translation key from the system. Use caution with this one.
Delete Locale
Deletes an entire language setting (locale) from a project, removing all associated translations.
Delete Project
Wipes out an entire localization project and all its contents. Permanent action.
Download File
Pulls down the current translation data for a project into a specified file format...
Get Key
Retrieves all details about one specific, existing translation key.
Get Locale
Fetches detailed information for a single target language setting (locale) within a...
Get Project
Gets the full status and metadata for an entire localization project by ID.
List Keys
Lists every translation key currently associated with a specific project.
List Locales
Shows all configured target languages (locales) for a given project.
List Projects
Provides a simple list of every single localization project you have set up.
List Translations
Lists the current translation strings available for a specific key and project.
Update Key
Modifies an existing translation key's metadata or definition.
Update Locale
Changes settings on an existing locale, such as renaming it or updating its default...
Update Project
Applies changes to the main project settings, like changing the name or primary scope.
Update Translation
Changes the actual translated text for a given key and locale combination.
Upload File
Ingests external localization files (like spreadsheets) to populate translations...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Phrase API integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Phrase (Software Localization API), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Phrase. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 20 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually managing localizations is a nightmare of tabs and tokens., Solved with Vinkius AI Gateway
Today, changing or adding a single language involves jumping between the code editor, the project dashboard, and then possibly an admin settings page. You copy key names into one place, navigate to another tab to check locales, and maybe paste data into a third area just to see if everything matches up. It's slow, and you always risk missing a step.
With this MCP server, the entire process happens in chat. Need to add German? Ask for it. The agent runs `create_locale`, confirms the change, and moves on. You get back confirmation that the data is structured correctly—no web UI required.
Phrase (Software Localization API) MCP Server: Get full control over localization assets.
Manual workflows force you to treat every project, key, and locale as isolated entities. You have to manually run checks—is the project created? Are all locales set up? Is the key unique?—before you can confidently proceed with a translation update.
Now, your agent handles that coordination. It doesn't just execute one tool; it chains them together: `get_project` -> `list_locales` -> `update_translation`. You get an atomic, verifiable result for complex state changes, making the entire process reliable.
What your AI can actually do with this
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.
019e5d44-ce1a-70d9-8e0f-1e71c875435b 
Here's how it actually works
The bottom line is that your AI client executes a sequence of API calls, managing complex state transitions across projects and translations for you.
Subscribe to the server and provide your unique Phrase Access Token.
Ask your agent for a high-level goal, like 'I need to add Japanese support to the Dashboard project.'
The agent runs multiple tools (list_projects -> create_locale -> update_project) until the task is complete and confirms the changes.
Who is this actually for?
This server is built for people who spend too much time copying data between specialized web portals. You're the developer whose code changes break the localization pipeline because they forgot to update a single key, or the localization manager staring at 50 different project dashboards trying to figure out which locale needs fixing.
Uses this to create translation keys and manage locales directly from their IDE while coding. They don't want context switching; they just want the key added.
Needs to quickly list projects, check locale configurations across multiple titles, or bulk download files without navigating the web UI.
Automates the initial setup of new localization initiatives, generating entire project structures and initial key sets for upcoming feature releases.
What Changes When You Connect
Stop Context Switching: You can run list_projects and then immediately jump into project management tasks (like calling create_key)—all from the chat window. No need to open a separate web browser tab.
Bulk Data Operations: Need to update 50 translations? Use upload_file to ingest a spreadsheet of data, or use update_translation in a loop via your agent to fix multiple strings across different locales.
Full Lifecycle Control: From initial setup (create_project) through maintenance (list_locales), this tool gives you full programmatic control over the entire localization structure. It's an end-to-end management system.
Code-Sync Management: The create_key and delete_key tools let developers manage their source code strings (keys) directly from within the agent, keeping your codebase and Phrase perfectly synced instantly.
Deep Inspection: Don't guess what you have. Use get_project, list_locales, or get_key to fetch precise data points—knowing exactly which locale is missing or which key needs updating before writing any code.
See it in action
The Missing Locale Problem
A product manager notices that the 'German' language (de-DE) was never added to a new project. Instead of logging into Phrase and manually navigating setup menus, they prompt their agent: 'Check if German is available for Project XYZ.' The agent runs list_locales and confirms it's missing. They then instruct the agent to run create_locale, solving the issue in three steps.
The Broken Key Sync
A developer refactors a feature and changes the key 'user.profile.avatar' to 'user.avatar.display'. Instead of manually updating every reference, they ask their agent to use update_key to rename the string across the entire project scope. This prevents broken translations in all target languages.
The Initial Project Setup
A team starts a new product line and needs localization setup for English, Spanish, French, and Japanese. They prompt their agent to 'Start a new project called Global Site.' The agent runs create_project and then sequentially calls create_locale for all four languages, getting the entire scaffold ready instantly.
The Translation Audit
A localization manager needs to audit all translations for a specific key ('welcome.message') across 15 different locales. They use list_translations and then prompt the agent to check if any locale is missing required data, ensuring no language falls out of sync.
The honest tradeoffs
Manual API Lookups
The developer sees an error about a bad key name. They waste time searching the Phrase web UI or running multiple individual get_key calls to verify existence.
First, run list_keys for the project to get a full inventory of available keys. Then, use get_key only on the specific key you suspect is broken. This minimizes redundant read operations.
Ignoring File Uploads
The team has translations in a giant Excel sheet but doesn't know how to get them into the system without manual copy-pasting into individual translation records.
Don't try to update each cell individually. Use upload_file and point it at your formatted spreadsheet. This bulk action ingests data far faster than any single tool call.
Overwriting Data Blindly
The agent is told to 'fix the project settings' without checking current values, potentially deleting critical metadata or changing the wrong default locale.
Always run get_project and review the output before running update_project. Check the existing structure first. Read before you write.
When It Fits, When It Doesn't
Use this server if your primary pain point is managing the structural integrity of localization data—the keys, the languages, or the projects themselves. You need to run full CRUD operations (Create, Read, Update, Delete) on organizational units.
Don't use it if you only need simple messaging or document storage; those systems are better suited for basic text exchange. If you just want to retrieve a single translated string value without knowing the key first, consider an alternative dedicated lookup tool instead of using list_translations when a simpler getter might suffice.
In short: Use this if you're building out the localization system. Don't use it if you are only writing one sentence into a text field.
Questions you might have
How do I use the create_key tool with Phrase API MCP Server? +
You tell your agent what key you need and where. For example: 'Create a new translation key called 'user.greeting.message' in the Main App project.' The agent handles the necessary syntax for create_key.
Can I delete a whole localization project using Phrase API MCP Server? +
Yes, you use the delete_project tool. Be careful; this action is irreversible and wipes out all associated keys, locales, and translations within that project scope.
Does list_locales show me if a locale is missing for a project? +
The list_locales tool shows you every configured language. If the required language isn't in the returned list, it means the locale needs to be added first using create_locale.
What should I use if I have translations in a CSV file? +
Don't try to update them one by one. Use the upload_file tool and point it at your structured spreadsheet. This handles bulk data ingestion efficiently, updating many keys/translations simultaneously.
What credentials do I need to connect before running list_projects? +
You must supply a valid Phrase Access Token. This token authorizes your agent to interact with your specific account and execute any commands, like listing projects.
How does the get_project tool retrieve details about an existing project? +
It requires the unique Project ID. Once you provide that ID, the tool returns all metadata, including locale setup, key counts, and status information for that specific localization container.
If I need to change a translation string, how does update_translation work? +
The update_translation tool requires three things: the Project ID, the Locale ID, and the new content. It overwrites the existing text for that specific key/language combination.
Can I use download_file to get translations in multiple formats? +
Yes, download_file handles various file types. You specify the format you need (like JSON or CSV) and the scope of data, pulling all required translations into a single downloadable package.
Can I list all translation keys for a specific project? +
Yes! Use the list_keys tool by providing the project_id. It will retrieve all translation keys configured for that project.
How do I add a new language to my localization project? +
You can use the create_locale tool. You'll need to provide the project_id, the locale name (e.g., 'French'), and the locale code (e.g., 'fr-FR').
Is it possible to update an existing project's name? +
Yes, the update_project tool allows you to modify properties like the project name and main_format using the project_id.
We've already built the connector for Phrase API. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 20 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.