Skip to main content
Glama
README.md
# 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

A3.5/5.0

Scored across 47 tools

Disambiguation2/5

Several tools retrieve translation keys with overlapping purposes (get_all_translation_keys, get_all_translation_keys_v2, get_translation_keys, get_translation_key_details), and update_translation_key vs update_translation_key_by_id requires knowing whether to use key or ID. The screenshot-upload trio and auto-translation variants add further boundary confusion, though descriptions do clarify some distinctions.

Naming Consistency4/5

Most tools follow the verb_noun snake_case pattern (create_language, delete_tag, get_customers), making the set generally predictable. The main inconsistencies are the v2 suffix and the proliferation of similarly named key/list/detail verbs, but the overall convention remains readable.

Tool Count2/5

47 tools is heavy for a single MCP server, even for a broad localization platform. Many could be consolidated (key retrieval variants, screenshot uploads, auto-translation job endpoints), so the count feels inflated rather than earned.

Completeness4/5

The tool surface covers the core localization lifecycle: keys, translations, languages, tags, environments, customers, glossary, auto-translation, import/export, and activity. Minor gaps exist—no environment update/delete, no explicit glossary update, no translation deletion separate from keys—but agents can work around most of these.

Maintenance

ActivityMaintained
ResponsivenessNo issues