Connect your agent to SimpleLocalize and let it manage keys, translations, and publishing through the Model Context Protocol. Works with Cursor, Windsurf, GitHub Copilot, Claude Desktop, and custom agent runtimes.

Why teams use it
Translation management becomes part of the same workflow where code is written and reviewed.
Ask your AI agent to add or update translation keys directly from source code context.
Run bulk updates for missing translations across languages with one prompt.
Trigger hosting publication for a selected environment after your review pass.
Watch the workflow
See a real session where an AI agent uses the SimpleLocalize MCP server to work with translation keys and translations directly from the editor.
Installation
Create a project API key in SimpleLocalize and add this config to your MCP client. Replace SIMPLELOCALIZE_API_KEY with your key value.
Capabilities
createTranslationKeys: Bulk key creation from codeupdateTranslationsBulk: Multi-language text updatesgetTranslations: Fetch missing translations by localepublishHosting: Trigger zero-downtime hosting deploymentmanageLanguages: Add or delete project localesLocal development
You can run the server locally, attach MCP Inspector, and test tool responses before sharing configuration with your team.
See full setup in MCP documentation and source code on GitHub.
Any client supporting standard Model Context Protocol (stdio transport) works out of the box, including Cursor, Windsurf, Claude Desktop, and GitHub Copilot.
No, the MCP server works with free-tier SimpleLocalize projects using your project API key.
The agent reads your codebase context (such as React useTranslation hooks, i18next calls, or JSON translation files) and compares key usages directly against your SimpleLocalize project using the getAllTranslationKeys tool.
Yes. The MCP server runs via npx or Node.js over standard input/output (stdio), making it compatible with custom agent runtimes, CLI workflows, and automated scripts.