Locize
Read and write Locize translation keys, manage branches, and publish i18n versions from your agent while building multilingual apps.
Overview
Locize MCP is an MCP server for the Build phase that lets AI assistants read and write translations, manage branches, and publish Locize versions.
What is this MCP server?
- Hosted streamable-http MCP at https://mcp.locize.app
- Read and write translation resources from AI assistants
- Publish versions and manage Locize branches without leaving the agent
- Version 1.0.0 with integration docs at locize.com/docs/integration/mcp
- Targets i18next/Locize workflows for web and mobile string catalogs
- Server version 1.0.0 per MCP manifest
- Remote endpoint: https://mcp.locize.app (streamable-http)
- Official MCP integration documentation on locize.com
What problem does it solve?
Updating translations and publishing locale versions still breaks solo builders out of the agent into the Locize UI and manual file edits.
Who is it for?
Indie builders on Locize/i18next who want agent-driven string updates and controlled publishes during feature work.
Skip if: English-only products with no TMS, or teams that require professional translator workflows outside Locize automation.
What do I get? / Deliverables
After registering Locize MCP, your agent can sync keys, adjust copy per language, and publish versions so multilingual builds stay current with implementation.
- Updated translation keys and languages in Locize
- Published or staged Locize versions ready for app bundles
- Branch-aligned locale changes traceable from agent sessions
Recommended MCP Servers
Journey fit
Localization is implemented alongside UI and copy—canonical shelf is Build when strings ship in the product surface. Translation CRUD and publish flows attach to frontend and user-facing assets rather than backend-only APIs or ops monitoring.
How it compares
Hosted TMS MCP integration, not a generic docs generator or static i18n linter skill.
Common Questions / FAQ
Who is app.locize.mcp/server for?
Solo developers and small teams using Locize for i18n who want Claude Code, Cursor, or Codex to manage translations and releases from the same session as code changes.
When should I use app.locize.mcp/server?
Use it during Build when adding locales, fixing UI copy, managing translation branches, or publishing a version before you ship a multilingual release.
How do I add app.locize.mcp/server to my agent?
Add the streamable-http remote https://mcp.locize.app in your MCP client and configure Locize project API access per https://www.locize.com/docs/integration/mcp.