Name: Tolgee
Author: tolgee

Tolgee MCP

Your app's translations in Tolgee: search keys, create translations, trigger machine translation

Tool-list grade A Remote · Streamable HTTP API key 22 tools v1.0.0

No reviews yet by tolgeeGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Your app's translations in Tolgee: search keys, create translations, trigger machine translation

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http tolgee-tolgee-mcp https://app.tolgee.io/mcp/developer --header 'X-API-Key: ${X_API_KEY}'

# 2 — ask your agent for something these tools do
#   get_batch_job_status, machine_translate, store_big_meta and 19 more

It needs X_API_KEY (Tolgee Personal Access Token (tgpat_...) or Project API Key (tgpak_...)): this sends it in the X-API-Key header from your environment, so export it first — its endpoint answers 401 without it.

Tolgee costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

tolgee1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.

Claude Codedeclared by this listing

This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads X_API_KEY (Tolgee Personal Access Token (tgpat_...) or Project API Key (tgpak_...)) from your environment each time it connects and sends it in the X-API-Key header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx X_API_KEY … and open a new terminal (Windows).

claude mcp add --scope user --transport http tolgee-tolgee-mcp https://app.tolgee.io/mcp/developer --header 'X-API-Key: ${X_API_KEY}'

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: X-API-Key header — Tolgee Personal Access Token (tgpat_...) or Project API Key (tgpak_...). You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.

What you approve

22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Get the status of a batch job (e.g. machine translation) by its ID. Use to poll for completion.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
jobId	number	yes	ID of the batch job

Start machine translation for specified keys into target languages. Returns a batch job ID — use get_batch_job_status to poll for completion.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keyNames	array	yes	Names of keys to translate
targetLanguageTags	array	yes	Language tags to translate into (e.g. ['de', 'fr'])
namespace	string	no	Optional: namespace of the keys
branch	string	no	Optional: branch name

Store key relationships so Tolgee can use translations of related keys as context during machine translation, producing more consistent results. Keys that appear near each other in source code (e.g. on the same page or component) should be stored as related.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
relatedKeysInOrder	array	yes	List of related keys in the order they appear together
branch	string	no	Optional: branch name

List branches in a Tolgee project. Returns up to 100 results per page. Only available for projects with branching enabled (enterprise feature).

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
search	string	no	Optional: search filter for branch names
page	number	no	Optional: page number (0-based, default 0)

Create a new branch in a Tolgee project by forking from an existing branch. Only available for projects with branching enabled (enterprise feature).

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
name	string	yes	Name of the new branch
originBranchId	number	yes	ID of the branch to fork from

Delete a branch from a Tolgee project. IMPORTANT: This is a destructive operation. The AI assistant should always confirm with the user before calling this tool.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
branchName	string	yes	Name of the branch to delete

List translation keys in a Tolgee project. Returns up to 100 keys per page. Use search_keys to find specific keys by name or translation text.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
branch	string	no	Optional: branch name
page	number	no	Optional: page number (0-based, default 0)

Search for translation keys in a Tolgee project by name or translation text. Returns up to 50 matching keys per page. Note: namespace and tags filtering is not yet supported — filter results client-side if needed.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
query	string	yes	Search query (matches key name or translation text)
languageTag	string	no	Optional: language tag to search translations in
branch	string	no	Optional: branch name
page	number	no	Optional: page number (0-based, default 0)

Create translation keys in a Tolgee project with optional translations and tags. Keys that already exist are silently skipped — their translations and tags are not updated. Use update_key and set_translation to modify existing keys.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keys	array	yes	List of keys to create
namespace	string	no	Optional: default namespace for all keys (individual keys can override)
branch	string	no	Optional: branch name

Get a translation key's metadata (name, namespace, description) by its name. To get the key's translations, use get_translations.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keyName	string	yes	The translation key name
namespace	string	no	Optional: namespace of the key
branch	string	no	Optional: branch name

Update an existing translation key's name, namespace, or description

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keyName	string	yes	Current key name (used to find the key)
keyNamespace	string	no	Optional: current namespace of the key (used to find the key)
keyBranch	string	no	Optional: branch name (used to find the key, for branching projects)
newName	string	yes	New key name (provide the current name if unchanged)
newNamespace	string	no	Optional: new namespace for the key
newDescription	string	no	Optional: new description for the key

Delete translation keys from a Tolgee project. IMPORTANT: This is a destructive operation. The AI assistant should always confirm with the user before calling this tool.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keyNames	array	yes	Names of the keys to delete
namespace	string	no	Optional: namespace of the keys
branch	string	no	Optional: branch name

List all languages configured for a Tolgee project. Returns up to 1000 results per page.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
page	number	no	Optional: page number (0-based, default 0)

Add a new language to a Tolgee project

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
name	string	yes	Language display name (e.g. 'German')
tag	string	yes	Language tag / IETF BCP 47 code (e.g. 'de')
originalName	string	no	Native name of the language (e.g. 'Deutsch')
flagEmoji	string	no	Flag emoji for this language

List all namespaces in a Tolgee project. Namespaces organize translation keys into logical groups (e.g. by feature, page, or module).

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)

List Tolgee projects accessible to the current user. Returns up to 100 results per page.

Parameter	Type	Required	Notes
search	string	no	Optional search query to filter projects by name
page	number	no	Optional: page number (0-based, default 0)

Create a new Tolgee project with initial languages

Parameter	Type	Required	Notes
name	string	yes	Project name
organizationId	number	yes	ID of the organization to create the project in
languages	array	yes	Initial languages for the project
baseLanguageTag	string	no	Tag of the base language (default: first language)

Get translation status and progress for each language in a project. Returns per-language statistics including translated, reviewed, and untranslated percentages.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)

List all tags used in a Tolgee project. Returns up to 1000 results per page.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
search	string	no	Optional: search filter for tag names
page	number	no	Optional: page number (0-based, default 0)

Add tags to translation keys. Creates tags if they don't exist.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keyNames	array	yes	Names of the keys to tag
tags	array	yes	Names of the tags to add
namespace	string	no	Optional: namespace of the keys
branch	string	no	Optional: branch name

Get translations for a specific key in a Tolgee project. Returns translations in all project languages, or only the specified languages if provided.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keyName	string	yes	The translation key name
namespace	string	no	Optional: namespace of the key
branch	string	no	Optional: branch name
languages	array	no	Optional: language tags to filter by (e.g. ['en', 'de']). If omitted, returns all languages.

Set or update translations for a key in one or more languages. The key must already exist — use create_keys to create it first.

Parameter	Type	Required	Notes
projectId	number	no	ID of the project (required for PAT, auto-resolved for PAK)
keyName	string	yes	The translation key name
namespace	string	no	Optional: namespace of the key
translations	object	yes	Translations as {languageTag: text} map (e.g. {"en": "Hello", "de": "Hallo"})
branch	string	no	Optional: branch name

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Tolgee or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.0 · scanned 23 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 0 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest2f21da0530eb570af65e6ac647cfa6cdf1e0df563b7c269e892ba3974c8d14a3

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
get_batch_job_status	no tags
machine_translate	no tags
store_big_meta	no tags
list_branches	no tags
create_branch	no tags
delete_branch	no tags
list_keys	sensitive-source	sensitive-source: keyword "list_keys"
search_keys	no tags
create_keys	no tags
get_key	no tags
update_key	no tags
delete_keys	no tags
list_languages	no tags
create_language	no tags
list_namespaces	no tags
list_projects	no tags
create_project	no tags
get_project_language_statistics	no tags
list_tags	no tags
tag_keys	no tags
get_translations	no tags
set_translation	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest2f21da0530eb570a

Scanned2026-10-23

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.