MCP for
AI engineers

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.

No credit card required•14-day free trial•Tracking-free service
Configuring SimpleLocalize MCP server in Cursor AI mcp.json settings

Why teams use it

Your agent can talk to localization data

Translation management becomes part of the same workflow where code is written and reviewed.

Stay inside your editor

Ask your AI agent to add or update translation keys directly from source code context.

Batch translation updates

Run bulk updates for missing translations across languages with one prompt.

Publish from agent

Trigger hosting publication for a selected environment after your review pass.

Watch the workflow

MCP localization in Cursor AI

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

MCP config in 30 seconds

Add the SimpleLocalize MCP server URL to your MCP client and sign in with your SimpleLocalize account. There is nothing to install and no API key to copy.

mcp.json
{ "mcpServers": { "simplelocalize": { "url": "https://api.simplelocalize.io/mcp" } } }

Capabilities

Exposed MCP Tools

  • create_translation_keys: Bulk key creation from code
  • update_translations: Multi-language text updates
  • list_translations: Fetch missing translations by locale
  • publish_translations: Trigger zero-downtime hosting deployment
  • create_language, delete_language: Add or delete project locales
Agent session output
# Prompt in Cursor > Add missing checkout translations for de and fr # Tool calls list_translation_keys -> 152 keys list_translations -> 19 missing in de, 22 missing in fr update_translations -> 41 translations updated # Result ✓ de and fr checkout flows are complete ✓ Ready for review before publishing

Custom agents

Call it from scripts and headless agents

Agents without a sign-in screen can call the hosted server over HTTP with a Project API Key or a Personal Access Token in a header.

Terminal
# List the tools available to the agent $ curl https://api.simplelocalize.io/mcp \ -H "X-SimpleLocalize-Token: $SIMPLELOCALIZE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}' ✓ list_translation_keys, list_translations, update_translations, ...

See full setup in MCP documentation.

Connect your AI agent to localization

  • Claude, Cursor, Windsurf and Copilot support
  • Bulk key and translation operations
  • Hosting publish from MCP tools
Create free project
No credit card required∙5-minute setup
"The product
and support
are fantastic."
Laars Buur|CTO
"The support is
blazing fast,
thank you Jakub!"
Stefan|Developer
"Interface that
makes any dev
feel at home!"
Dario De Cianni|CTO
"Excellent app,
saves my time
and money"
Dmitry Melnik|Developer

Frequently asked questions

Which AI clients support SimpleLocalize MCP?

Any client supporting the Model Context Protocol over Streamable HTTP works out of the box, including Claude, Claude Code, Cursor, Windsurf, VS Code and GitHub Copilot. You sign in with your SimpleLocalize account and choose the projects and tools the agent can use.

Do I need a paid SimpleLocalize account?

No, the MCP server works with free-tier SimpleLocalize projects.

How does the agent know which translation keys to create or update?

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 list_translation_keys tool.

Can I use the SimpleLocalize MCP server in CI/CD pipelines or headless agents?

Yes. Custom agent runtimes, CLI workflows and automated scripts can call the hosted server over HTTP with a Project API Key or a Personal Access Token in a header, without the sign-in screen.