SimpleLocalize

You set up and use this MCP server to interact with SimpleLocalize translations. It exposes tools to create and update translation keys, fetch keys and details, manage tags and languages, and retrieve translations, all through a standardized MCP interface that client applications can consume.

How to use

Configure your MCP client to connect to the SimpleLocalize MCP server. You can run the server locally via a client that supports MCP stdio connections by using the provided command and API key. Once configured, you can perform common translation management tasks such as creating translation keys, updating translations, retrieving keys, and managing languages and tags. Use separate client configurations for a local build or a hosted runtime as needed, and pass your API key securely to authorize requests.

How to install

Prerequisites you need before installation:

Node.js and pnpm should be installed on your system.

# Install dependencies
pnpm install

# Build the MCP server
pnpm build

Additional setup and usage notes

If you plan to run the MCP server from a client with a local build, configure the client to point to the built server. Use the following example to start the server via a local Node.js process after you build the project. Replace the path with the actual location of your built index.js and supply your API key.

{
  "mcpServers": {
    "simplelocalize": {
      "command": "node",
      "args": ["path/to/simplelocalize-mcp-server/build/index.js"],
      "env": {
        "SIMPLELOCALIZE_API_KEY": "your_api_key"
      }
    }
  }
}

Configuration and security notes

An API key is required to access SimpleLocalize MCP endpoints. Create and manage your API keys in your SimpleLocalize account under Settings > Credentials. Pass the API key to the MCP client as shown in the configuration examples, and keep your keys secure.

Debugging and troubleshooting

If you need to inspect MCP requests and responses during development, use an MCP Inspector tool or whichever debugging utility your environment provides. Ensure you include the --api-key argument in the runtime configuration so requests can be authenticated.

Notes and examples

The MCP server supports the following primary actions: create translation key, update translations, get all translation keys, get translation key details, get tags, create tags, get languages, create languages, and get translations. You can extend functionality by adding new tools or endpoints as needed.

Available tools

Create translation key

Create a new translation key to categorize a piece of text for translation across languages.

Update translations

Modify existing translations for one or more languages.

Get all translation keys

Retrieve a list of all translation keys in the project.

Get translation key details

Fetch detailed information about a specific translation key.

Get tags

Retrieve the list of tags used to group or categorize translation keys.

Create tag

Create a new tag to organize translation keys.

Get languages

Fetch the list of languages configured in the project.

Create languages

Add new languages to support translations.

Get translations

Retrieve translations for specific keys and languages.