SimpleLocalize

A MCP (Model Context Protocol) server implementation for SimpleLocalize.

python

3

GitHub Stars

python

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "galvingao-mcp-simplelocalize": {
      "command": "uv",
      "args": [
        "run",
        "--project",
        "/path/to/mcp-simplelocalize/",
        "/path/to/mcp-simplelocalize/main.py"
      ],
      "env": {
        "SIMPLELOCALIZE_API_KEY": "your-api-key-here"
      }
    }
  }
}

You can run an MCP server that connects SimpleLocalize with your project to automate localization. This server lets you translate components using a SimpleLocalize API key, streamlining how you apply translations across your project.

How to use

Use the MCP server with your MCP client to localize components and keep translations in sync with SimpleLocalize. You provide an API key for a specific project, describe your localization rules, and the server handles the localization flow according to those rules.

How to install

# Prerequisites
- Install uv (a package runner)

# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh

# Clone the MCP server repository
git clone https://github.com/GalvinGao/mcp-simplelocalize.git

# Install dependencies
uv sync

Configure the MCP server for your project by creating a Cursor configuration that points to the local MCP project and provides your API key. Place this at a path like .cursor/mcp.json in your project root and ensure it is ignored by version control to keep your API key private.

{
  "mcpServers": {
    "simplelocalize": {
      "command": "uv",
      "args": [
        "run",
        "--project",
        "/path/to/mcp-simplelocalize/",
        "/path/to/mcp-simplelocalize/main.py"
      ],
      "env": {
        "SIMPLELOCALIZE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Describe your project localization requirements under a .cursorrules file to guide the translation process. Include namespaces, language codes, and any conventions or examples you want the LLM to follow.

## Translations
- Put all translations under the `default` namespace
- Language codes supported by this project: `en-US`, `ja-JP`, `ko-KR`, and `zh-Hant`.
- (any other conventions you want the LLM to follow, e.g. key naming style, etc. or just give it some examples would work well)

Additional notes

Once configured, you can prompt the MCP client to localize a component. Typical prompts involve asking the server to translate strings and update components with the translated text using the SimpleLocalize API key you configured.