Skip to main content
Glama
GalvinGao

SimpleLocalize MCP Server

by GalvinGao

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SIMPLELOCALIZE_API_KEYYesYour SimpleLocalize API key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create_translation_keysA

Create translation keys in bulk for a project.

This endpoint allows you to create multiple translation keys at once. You can create up to 100 translation keys in a single request. Each key must have a 'key' field, and optionally can include 'namespace' and 'description' fields.

Args: keys: List of dictionaries containing key information with fields: - key (required): Translation key (max 500 chars) - namespace (optional): Namespace for the key (max 128 chars) - description (optional): Description for translators (max 500 chars)

update_translationsB

Update translations in bulk with a single request.

This endpoint allows you to update multiple translations at once. You can update up to 100 translations in a single request. Each translation must specify the key, language, and text. Namespace is optional.

Args: translations: List of dictionaries containing translation information with fields: - key (required): Translation key - language (required): Language code - text (required): Translation text (max 65535 chars) - namespace (optional): Namespace for the key

publish_translationsA

Publish translations to a specified environment.

This endpoint publishes translations from the translation editor to hosting environments or from one hosting environment to another. Please note that this endpoint requires authorization and is only available for paid plans.

Common environment keys:

  • "_latest": Publish from Translation Editor

  • "_production": Publish to production environment (from _latest by default)

  • Custom environment key: Publish to custom environment

Args: environment_key: The environment key to publish to (e.g., "_latest", "_production", or custom key)

get_environment_statusB

Get the current status of a specified environment.

This endpoint returns information about the environment including the number of keys, languages, non-empty translations, creation date, and available resources.

Args: environment_key: The environment key to check status for (e.g., "_latest", "_production", or custom key)

duplicate_translationA

Duplicate translations from one key/namespace to another key/namespace.

This function copies all translations for a specific key (and optionally namespace) to another key (and optionally namespace). Useful for duplicating translations when creating similar keys or reorganizing translations.

Args: from_dict: Source dictionary with fields: - key (required): Source translation key - namespace (optional): Source namespace to_dict: Destination dictionary with fields: - key (required): Destination translation key - namespace (optional): Destination namespace

Returns: String message indicating success or failure

get_missing_translationsA

Get a list of translation keys that have missing translations.

This endpoint returns translation keys along with their existing translations, focusing on keys that are missing translations in one or more languages. To identify missing translations, the function compares each key against all languages that have at least one translation in the project.

Returns: List of dictionaries containing: - key (str): Translation key - namespace (str): Namespace for the key (if applicable) - description (str): Description for translators (if applicable) - translations (List[dict]): List of existing translations with fields: - language (str): Language code - text (str): Translation text

get_translations_for_keysA

Get translations for specific translation keys.

This endpoint fetches translations for a list of specified keys, optionally filtered by namespace. Returns all available translations for each key across all languages in the project.

Args: keys: List of translation keys to fetch translations for (required) namespace: Optional namespace to filter the translations (if not provided, fetches from all namespaces)

Returns: List of dictionaries containing: - key (str): Translation key - namespace (str): Namespace for the key - translations (List[dict]): List of translations with fields: - language (str): Language code
- text (str): Translation text - reviewStatus (str): Review status (REVIEWED, NOT_REVIEWED) - lastModifiedAt (str): Last modification timestamp

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: create keys, duplicate translations, get environment status, get missing translations, get translations for keys, publish translations, and update translations. The descriptions clearly differentiate their functions, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with clear, descriptive names: create_translation_keys, duplicate_translation, get_environment_status, get_missing_translations, get_translations_for_keys, publish_translations, update_translations. The naming is uniform and predictable throughout.

Tool Count5/5

With 7 tools, this server is well-scoped for a localization/translation management system. Each tool serves a specific, necessary function in the domain, covering key operations without bloat or redundancy.

Completeness4/5

The toolset covers core translation management workflows well: creation, duplication, retrieval (with various filters), updating, and publishing. A minor gap is the lack of explicit delete operations for keys or translations, which agents might need to work around, but overall coverage is strong.

Maintenance

ActivityInactive
ResponsivenessNo issues