Model Context Protocol server for SimpleLocalize

MCP server
for localization

Let Claude, Cursor or any AI agent manage your translations with plain-language prompts. Connect with one URL, nothing to install.

No credit card required•14-day free trial•Tracking-free service

How it works

From prompt to translated app in four steps

SimpleLocalize hosts the MCP server for you. Add its URL to your AI client, sign in and choose what the agent can do. Nothing to install, nothing to host.

1

Add the server URL

Add the server URL as a custom connector in Claude, or paste it into the MCP config of Cursor, VS Code or LM Studio. Claude Code needs a single command.

2

Sign in and choose access

Sign in with your SimpleLocalize account and pick the projects and tools the agent can use. You can change them anytime.

3

Ask the agent

Tell it to localize a component, fill missing translations or export files. The agent picks the right tools by itself.

4

Review in the editor

Every change lands in the SimpleLocalize translation editor with full history, so your team and translators can review it.

For a step-by-step walkthrough, see the getting started guide.

Connect the MCP server

Add https://api.simplelocalize.io/mcp to your AI client and sign in with your SimpleLocalize account. Connect it once and every chat can read, create and publish translations in the projects you chose.

See setup guide
https://api.simplelocalize.io/mcp

In Claude, go to Settings > Connectors, click Add custom connector, paste the URL and click Connect.

MCP Tools for translations

The server exposes SimpleLocalize as MCP tools with typed parameters,
so the agent knows exactly what it can do and what each call changes.

Translation keys

Create, update, rename and delete keys, one or hundreds at a time. Read key details, metadata and paginated lists, and attach screenshots for context.

Translations

Read translations for any language and namespace, and update one or hundreds of them at once straight from the code the agent just wrote.

Auto-translation

Translate a string on the fly without saving it, or start auto-translation jobs with DeepL, Google Translate or OpenAI and check their progress.

Export

Export translations to any of the supported formats: JSON, YAML, XLIFF, PO, iOS strings, Android XML and more.

Hosting & publishing

List and create hosting environments, inspect their details and publish translations to translation hosting from a single prompt.

Project setup

Manage glossary entries, tags, project languages and customer-specific translations. Read project details and the activity log to see what changed.

Prompts that work out of the box

You do not need to learn tool names. Describe the outcome and the agent chains the right calls.

Translation keys

“Localize this React component and push the new translation keys to SimpleLocalize”

Auto-translation

“Find translation keys without a German translation and auto-translate them with DeepL”

Activity log

“What changed in the project since yesterday?”

Translation hosting

“Publish the latest translations to production”

Export

“Export the pl‑PL translations as a single-language JSON file into src/locales”

Glossary

“Add a glossary entry so that 'SimpleLocalize' is never translated”

Screenshots

“Attach this screenshot to the checkout keys so translators see the context”

Works with every MCP client

The server uses the standard Streamable HTTP transport with OAuth sign-in, so it works in any client that supports the Model Context Protocol.

Frequently asked questions

What is an MCP server for localization?

Model Context Protocol (MCP) is an open standard that lets AI agents call external tools. The SimpleLocalize MCP server exposes translation keys, translations, auto-translation, import, export and hosting as tools, so an agent like Claude or Cursor can manage localization in your project from a natural language prompt.

Is the MCP server free?

Yes. The server is free to use. It requires a SimpleLocalize project, and the free plan is enough to try it. Auto-translation usage counts against the characters included in your plan, exactly as it does in the web editor.

How does the agent sign in?

Clients like Claude, Claude Code, Cursor and VS Code open a SimpleLocalize sign-in page, where you choose the projects and tools the app can use. You can change them or disconnect the app anytime in Security > Connected apps. Clients without sign-in support can send a Personal Access Token or a Project API Key in a header instead.

Does the server send my translations to an LLM provider?

The server itself only talks to the SimpleLocalize API. Whatever the agent reads through a tool becomes part of the conversation with your chosen AI client, the same as any file the agent opens. Auto-translation runs on the provider you configured in SimpleLocalize, for example DeepL, Google Translate or OpenAI.

Does it run locally or in the cloud?

In the cloud. SimpleLocalize hosts the server at https://api.simplelocalize.io/mcp, so there is nothing to install or keep up to date. The earlier npm package that ran locally with npx is deprecated.

How is this different from the CLI and the VS Code extension?

The CLI is for scripted, repeatable synchronization in your build or CI. The VS Code and IntelliJ extensions are for editing translations by hand inside the IDE. The MCP server is for delegating localization tasks to an AI agent. Many teams use all three: the agent adds keys, the extension reviews them, the CLI ships them.

Can the agent delete translations by accident?

Only if you leave delete tools enabled when you connect the app; you can unselect them on the sign-in page or later in Security > Connected apps. Delete tools are also annotated as destructive, so clients such as Claude ask for confirmation before running them. Every change is recorded in the project activity log and can be reviewed in the translation editor.

Get started with SimpleLocalize

  • All-in-one localization platform
  • Web-based translation editor for your team
  • Auto-translation, QA-checks, AI and more
  • See how easily you can start localizing your product.
  • Powerful API, hosting, integrations and developer tools
  • Unmatched customer support
Start for free
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

AI agents for translation management

The SimpleLocalize MCP server connects AI coding agents with a translation management system. Instead of copying strings between your code editor and a localization tool, you ask the agent to extract texts, create translation keys, fill missing translations and export files in the format your framework expects. The server implements the Model Context Protocol, the same standard used by Claude, Cursor, GitHub Copilot, Windsurf and a growing list of clients, and calls the SimpleLocalize REST API under the hood.

Localization workflow with Claude, Cursor and Copilot

A typical workflow starts in the code: the agent localizes a component with your i18n library, creates the keys in SimpleLocalize and adds source translations. Next it runs auto-translation for the missing languages, optionally guided by your glossary. Translators and reviewers work in the translation editor, and the agent or the SimpleLocalize CLI pulls the finished translations back into the repository or publishes them to translation hosting.

Hosted MCP server for SimpleLocalize

The server is hosted by SimpleLocalize and covers translation keys, translations, screenshots, auto-translation jobs, tags, languages, customers, glossary, hosting environments, export and project activity. New tools are available in every connected client without updates. The earlier @simplelocalize/simplelocalize-mcp npm package is deprecated; to migrate, replace its npx entry with the server URL, as described in the setup guide.