SimpleLocalize MCP Server
Official# MCP Server for SimpleLocalize
[SimpleLocalize](https://www.simplelocalize.io/?utm_source=dx&utm_medium=simplelocalize-mcp-server) is the developer-first translation management system.
This is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that provides tools for interacting with the SimpleLocalize API.
## How to setup
Configure your `mcp.json` file and add 'simplelocalize':
```
{
"mcpServers": {
"simplelocalize": {
"command": "npx",
"args": [
"-y",
"@simplelocalize/simplelocalize-mcp",
"--api-key=PROJECT_API_KEY"
]
}
}
}
```
## Features (Tools)
**Translation keys**
- Get translation keys
- Create translation key
- Update translation key
- Delete translation key
- Upload translation key screenshot (base64 or file)
**Translations**
- Get translations
- Update translation (single and bulk)
**Auto-translation**
- Auto-translate text
- Create auto-translation jobs
- Get auto-translation jobs
**Tags, languages & customers**
- Get/create/update/delete tags
- Get/create/update/delete languages
- Get/create/update/delete customers
**Hosting & publishing**
- Get/create hosting environments
- Get hosting environment details
- Publish translations to hosting
**Import, export & activity**
- Import translations from a local file
- Export translations to downloadable file(s)
- Get supported file formats
- Get project activity
**Glossary**
- Get glossary entries
- Create glossary entry
- Delete glossary entry
**Project**
- Get project details
Feel free to add more tools by making a pull request or [creating a feature request](https://github.com/simplelocalize/simplelocalize-mcp-server/issues/new).
## Installation
To use the MCP server, you'll need an API key. You can create and manage API keys in **SimpleLocalize > Settings > Credentials -> Project API Key**:
To run the server in a client like Claude Desktop, Cursor or Windsurf, add the following to your MCP config:
```json
{
"servers": {
"simplelocalize": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@simplelocalize/simplelocalize-mcp", "--api-key=SIMPLELOCALIZE_API_KEY"]
}
}
}
```
Replace `SIMPLELOCALIZE_API_KEY` with your API key
For detailed setup guides, see:
- [Cursor AI](https://docs.cursor.com/context/model-context-protocol)
- [Visual Studio Code](https://code.visualstudio.com/docs/copilot/chat/mcp-servers)
- [GitHub Copilot](https://github.blog/changelog/2025-05-19-agent-mode-and-mcp-support-for-copilot-in-jetbrains-eclipse-and-xcode-now-in-public-preview/)
- [Claude Desktop](https://modelcontextprotocol.io/quickstart/user)
- [Windsurf](https://docs.codeium.com/windsurf/mcp)
## Development
1. Install dependencies:
```bash
pnpm install
```
2. Build the server:
```bash
pnpm build
```
3. Update client to use the local build:
```json
{
"servers": {
"simplelocalize": {
"command": "node",
"args": ["path/to/simplelocalize-mcp-server/build/index.js"],
"env": {
"SIMPLELOCALIZE_API_KEY": "your_api_key"
}
}
}
}
```
## Debugging
To debug the MCP server, you can use the MCP Inspector tool:
1. Run the server with the inspector:
```bash
pnpm inspector
```
2. Open the provided URL in your browser to view and debug the MCP requests and responses.
3. Include the `--api-key` argument.
## Learn more
- [SimpleLocalize developer docs](https://simplelocalize.io/docs/?utm_source=dx&utm_medium=simplelocalize-mcp-server)
- [SimpleLocalize API reference](https://simplelocalize.io/docs/api/get-started/?utm_source=dx&utm_medium=simplelocalize-mcp-server)
- [Sign up for SimpleLocalize](https://simplelocalize.io/register/?utm_source=dx&utm_medium=simplelocalize-mcp-server)
TDQS
Scored across 47 tools
Most tools target distinct resources (keys, translations, languages, customers, environments, glossary, jobs, activity), but there is notable overlap among key retrieval tools (get_translations, get_all_translation_keys, get_translation_keys, get_all_translation_keys_v2, get_translation_key_details) and screenshot upload variants, which could cause misselection without careful reading.
The naming follows a consistent verb_noun pattern (get_, create_, update_, delete_, import_, export_, publish_, etc.) with clear resource nouns. Minor deviations include versioned tool names like get_all_translation_keys_v2 and the slight ambiguity between singular/plural job tools, but overall the pattern is predictable.
47 tools is excessive for most MCP servers, even for a comprehensive translation management platform. While each tool addresses a specific operation, the sheer number overwhelms agents and suggests possible consolidation (e.g., merging single/bulk variants or combining related getters). The count is well above the typical 3-15 range.
The tool surface is quite complete, covering CRUD for translation keys, translations, languages, tags, customers, glossary entries, environments, and auto-translation jobs, plus import/export and activity tracking. Minor gaps include missing update/delete for environments and no dedicated single-translation getter, but these are workable limitations.