Skip to main content
Glama
ytarfa

tolgee-mcp

by ytarfa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TOLGEE_API_KEYYesYour Tolgee API key
TOLGEE_API_URLNoBase URL of your Tolgee instancehttps://app.tolgee.io

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsA

List all Tolgee projects accessible to the authenticated user.

Returns a list of projects with their IDs, names, and base language.

get_projectB

Get details of a specific Tolgee project.

Args:
    project_id: The numeric ID of the project.
create_projectA

Create a new Tolgee project.

Args:
    name: The name for the new project.
    base_language_tag: BCP 47 language tag for the base language (default: "en").
update_projectB

Update an existing Tolgee project's settings.

Args:
    project_id: The numeric ID of the project to update.
    name: The new name for the project.
delete_projectA

Delete a Tolgee project. This action is irreversible.

Args:
    project_id: The numeric ID of the project to delete.
list_languagesA

List all languages configured in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
create_languageB

Add a new language to a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    name: Display name of the language (e.g., "French").
    tag: BCP 47 language tag (e.g., "fr", "de", "ja").
update_languageB

Update a language's properties in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    language_id: The numeric ID of the language to update.
    name: The new display name for the language.
delete_languageB

Delete a language from a Tolgee project. This removes all translations for this language.

Args:
    project_id: The numeric ID of the project.
    language_id: The numeric ID of the language to delete.
list_keysB

List localization keys in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    page: Page number (0-indexed, default 0).
    size: Number of keys per page (default 20).
search_keysA

Search for localization keys by name in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    search: Search query string to match against key names.
create_keyA

Create a new localization key in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    name: The key name (e.g., "button.submit", "greeting.hello").
    namespace: Optional namespace for the key.
    translations: Optional dict mapping language tags to translation values (e.g., {"en": "Hello", "fr": "Bonjour"}).
update_keyA

Update a localization key's name.

Args:
    project_id: The numeric ID of the project.
    key_id: The numeric ID of the key to update.
    name: The new name for the key.
delete_keysB

Delete one or more localization keys from a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    key_ids: List of key IDs to delete.
import_keysB

Import localization keys with translations into a Tolgee project.

Each key object should have a "name" field and a "translations" dict mapping language tags to values.

Args:
    project_id: The numeric ID of the project.
    keys: List of key objects, each with "name" (str) and "translations" (dict of language_tag -> value).

Example keys format:
    [{"name": "greeting", "translations": {"en": "Hello", "fr": "Bonjour"}}]
get_translationsA

Get translations for keys in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    languages: Optional list of language tags to filter by (e.g., ["en", "fr"]). If not specified, all languages are returned.
    page: Page number (0-indexed, default 0).
    size: Number of items per page (default 20).
set_translationsC

Set translation values for an existing key in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    key_name: The name of the existing key.
    translations: Dict mapping language tags to translation text values (e.g., {"en": "Hello", "fr": "Bonjour"}).
create_or_update_translationsA

Create a key if it doesn't exist and set its translations. If the key already exists, update its translations.

Args:
    project_id: The numeric ID of the project.
    key_name: The key name.
    translations: Dict mapping language tags to translation text values.
    namespace: Optional namespace for the key.
set_translation_stateA

Set the state of a specific translation.

Args:
    project_id: The numeric ID of the project.
    translation_id: The numeric ID of the translation (not the key ID).
    state: The new state. Valid values: "UNTRANSLATED", "TRANSLATED", "REVIEWED".
get_translation_historyB

Get the modification history of a specific translation.

Args:
    project_id: The numeric ID of the project.
    translation_id: The numeric ID of the translation.
export_translationsA

Export translations from a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    format: Export format. Supported: "JSON" (default), "XLIFF", "PO", "APPLE_STRINGS_STRINGSDICT", "ANDROID_XML", "FLUTTER_ARB", "PROPERTIES", "YAML_RUBY".
    languages: Optional list of language tags to export (e.g., ["en", "fr"]). Exports all languages if not specified.
    filter_namespace: Optional namespace to filter exported keys.
import_translationsB

Import translations into a Tolgee project using single-step import.

Each key object should have a "name" and "translations" mapping language tags to values.

Args:
    project_id: The numeric ID of the project.
    keys: List of key objects with "name" (str) and "translations" (dict of language_tag -> value).

Example:
    [{"name": "hello", "translations": {"en": "Hello", "de": "Hallo"}}]
list_tagsB

List all tags in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    page: Page number (0-indexed, default 0).
    size: Number of tags per page (default 20).
tag_keyB

Add a tag to a localization key. Creates the tag if it doesn't exist.

Args:
    project_id: The numeric ID of the project.
    key_id: The numeric ID of the key to tag.
    tag_name: The name of the tag to add.
remove_tag_from_keyB

Remove a tag from a localization key.

Args:
    project_id: The numeric ID of the project.
    key_id: The numeric ID of the key.
    tag_id: The numeric ID of the tag to remove.
list_namespacesA

List all used namespaces in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
update_namespaceC

Rename a namespace in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    namespace_id: The numeric ID of the namespace to rename.
    name: The new name for the namespace.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 27 tools

Disambiguation2/5

Several tools overlap heavily: import_keys and import_translations are nearly identical, and set_translations, create_or_update_translations, and create_key all offer ways to write translations. An agent could easily choose the wrong write operation when the intended behavior is upsert versus update-existing versus bulk import.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern: create_, update_, delete_, list_, get_, set_, import_, export_. The similar names like import_keys and import_translations are confusing semantically, but they do not violate the naming convention.

Tool Count2/5

At 27 tools, the server exceeds the range where each tool clearly earns its place, and some tools appear redundant rather than complementary. Trimming duplicate import/write operations would reduce the surface to a more coherent size.

Completeness4/5

The toolset covers project, language, key, translation, tag, and namespace lifecycle needs, including import/export and translation history. Minor gaps exist such as no explicit translation deletion or tag rename, but agents can work around them with existing operations.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources