Usage Tolgee MCP Server

Once the Tolgee MCP server is connected, you manage your localization project by asking your AI assistant in natural language: list and search translation keys, get and set translations, trigger batch machine translation, and manage languages, tags, namespaces and branches. This page shows example prompts you can paste into Claude, Cursor, Windsurf, or ChatGPT, plus best practices for keeping your AI-driven localization workflow safe, fast, and accurate.

What can I do with the Tolgee MCP server?

The Tolgee MCP server exposes 20 tools covering the full localization workflow: list, search, create, update and delete translation keys; get and set translations; manage languages, tags, namespaces and branches; run batch machine-translation jobs; store context for better MT quality; and query project statistics. In short, anything you'd normally do in the Tolgee UI can be done from your AI assistant in natural language.

Tools by category:

Category	Tools
Projects	list_projects, create_project, get_project_language_statistics
Keys	list_keys, search_keys, get_key, create_keys, update_key, delete_keys
Translations	get_translations, set_translation
Languages	list_languages, create_language
Tags	list_tags, tag_keys
Namespaces	list_namespaces
Branches	list_branches, create_branch, delete_branch
Batch / Machine translation	machine_translate, get_batch_job_status
Context for MT	store_big_meta

Example Workflow

Once connected, you can interact with Tolgee in natural language. For example:

You: List all keys in the "homepage" namespace that contain "welcome"

AI: Found 3 keys in namespace "homepage":

• homepage.welcome_title — "Welcome to our platform"
• homepage.welcome_subtitle — "Get started in minutes"
• homepage.welcome_cta — "Sign up free"

You: Translate these keys to German and French using machine translation

AI: Started machine translation batch job. Job ID: 42. Checking status... completed. All 3 keys have been translated to German (de) and French (fr).

Best Practices

• Start with read-only commands — Use list_keys, get_translations, or list_projects first to verify that your connection works before making changes.
• Use a Project API key when working on a single project — This avoids having to specify projectId with every request and limits the blast radius of accidental changes.
• Be careful with destructive operations — Tools like delete_keys and delete_branch are irreversible. AI assistants are instructed to confirm with you before executing them, but always double-check.
• Keep tokens secure — Store your API keys in environment variables or a secrets manager. Don't commit them to version control. Use the minimum required scopes and rotate tokens regularly.
• Leverage Big Meta for better MT quality — If you're using machine translation, store key relationships with store_big_meta so Tolgee can use translations of related keys as context.