Tolgee
REMOTE · APP.TOLGEE.IO · SCANNED SEP 24
Your app's translations in Tolgee: search keys, create translations, trigger machine translation
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 22 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2106 tokens (~95/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_branch" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Tolgee MCP server?
Tolgee is a hosted endpoint at https://app.tolgee.io/mcp/developer, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.tolgee.io
claude mcp add --transport http tolgee-tolgee 'https://app.tolgee.io/mcp/developer'
{
"mcpServers": {
"tolgee-tolgee": {
"url": "https://app.tolgee.io/mcp/developer"
}
}
} {
"servers": {
"tolgee-tolgee": {
"type": "http",
"url": "https://app.tolgee.io/mcp/developer"
}
}
} [mcp_servers.tolgee-tolgee] url = "https://app.tolgee.io/mcp/developer"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tolgee-tolgee": {
"type": "remote",
"url": "https://app.tolgee.io/mcp/developer",
"enabled": true
}
}
} openclaw mcp add tolgee-tolgee --url 'https://app.tolgee.io/mcp/developer' --transport streamable-http
mcp_servers:
tolgee-tolgee:
url: "https://app.tolgee.io/mcp/developer" {
"McpServers": {
"tolgee-tolgee": {
"Transport": "http",
"Url": "https://app.tolgee.io/mcp/developer"
}
}
} assistant mcp add tolgee-tolgee -t streamable-http -u 'https://app.tolgee.io/mcp/developer'
{
"mcpServers": {
"tolgee-tolgee": {
"type": "http",
"url": "https://app.tolgee.io/mcp/developer"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 0
- Server version: v3.224.5 → v3.224.6 functional
- 22 Sept 26 0
- Server version: v3.224.2 → v3.224.5 functional
- 19 Sept 26 0
- Server version: v3.223.1 → v3.224.2 functional
- 17 Sept 26 0
- Server version: v3.221.3 → v3.223.1 functional
- 16 Sept 26 0
- Server version: v3.221.2 → v3.221.3 functional
- 9 Sept 26 0
- Server version: v3.220.0 → v3.221.2 functional
- 7 Sept 26 0
- Server version: v3.219.7 → v3.220.0 functional
- 3 Sept 26 0
- Server version: v3.219.2 → v3.219.7 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://app.tolgee.io/mcp/developer
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.tolgee.io | CN=YR2,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | RSA 2048 | SHA256-RSA | 506db0a378a913203390a32cf0627b47be8 |
| SANs: app.tolgee.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.tolgee.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| tolgee.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 ; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.tolgee.io/mcp/developer | Verified | 200 | |
| http (plaintext) | http://app.tolgee.io/mcp/developer | HTTPS enforced | 301 | https://app.tolgee.io:443/mcp/developer |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_branch ~87
Create a new branch in a Tolgee project by forking from an existing branch. Only available for projects with branching enabled (enterprise feature).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the new branch |
| originBranchId | number | yes | ID of the branch to fork from |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
create_keys ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| keys | array | yes | List of keys to create |
| namespace | string | – | Optional: default namespace for all keys (individual keys can override) |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
create_language ~112
Add a new language to a Tolgee project
| Name | Type | Req | Description |
|---|---|---|---|
| flagEmoji | string | – | Flag emoji for this language |
| name | string | yes | Language display name (e.g. 'German') |
| originalName | string | – | Native name of the language (e.g. 'Deutsch') |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| tag | string | yes | Language tag / IETF BCP 47 code (e.g. 'de') |
No output schema declared.
No examples provided.
create_project ~75
Create a new Tolgee project with initial languages
| Name | Type | Req | Description |
|---|---|---|---|
| baseLanguageTag | string | – | Tag of the base language (default: first language) |
| languages | array | yes | Initial languages for the project |
| name | string | yes | Project name |
| organizationId | number | yes | ID of the organization to create the project in |
No output schema declared.
No examples provided.
delete_branch ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | yes | Name of the branch to delete |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
delete_keys ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| keyNames | array | yes | Names of the keys to delete |
| namespace | string | – | Optional: namespace of the keys |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
get_batch_job_status ~70
Get the status of a batch job (e.g. machine translation) by its ID. Use to poll for completion.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | number | yes | ID of the batch job |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
get_key ~96
Get a translation key's metadata (name, namespace, description) by its name. To get the key's translations, use get_translations.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| keyName | string | yes | The translation key name |
| namespace | string | – | Optional: namespace of the key |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
get_project_language_statistics ~58
Get translation status and progress for each language in a project. Returns per-language statistics including translated, reviewed, and untranslated percentages.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
get_translations ~125
Get translations for a specific key in a Tolgee project. Returns translations in all project languages, or only the specified languages if provided.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| keyName | string | yes | The translation key name |
| languages | array | – | Optional: language tags to filter by (e.g. ['en', 'de']). If omitted, returns all languages. |
| namespace | string | – | Optional: namespace of the key |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
list_branches ~92
List branches in a Tolgee project. Returns up to 100 results per page. Only available for projects with branching enabled (enterprise feature).
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional: page number (0-based, default 0) |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| search | string | – | Optional: search filter for branch names |
No output schema declared.
No examples provided.
list_keys ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| page | number | – | Optional: page number (0-based, default 0) |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
list_languages ~69
List all languages configured for a Tolgee project. Returns up to 1000 results per page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional: page number (0-based, default 0) |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
list_namespaces ~61
List all namespaces in a Tolgee project. Namespaces organize translation keys into logical groups (e.g. by feature, page, or module).
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
list_projects ~60
List Tolgee projects accessible to the current user. Returns up to 100 results per page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional: page number (0-based, default 0) |
| search | string | – | Optional search query to filter projects by name |
No output schema declared.
No examples provided.
list_tags ~83
List all tags used in a Tolgee project. Returns up to 1000 results per page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional: page number (0-based, default 0) |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| search | string | – | Optional: search filter for tag names |
No output schema declared.
No examples provided.
machine_translate ~117
Start machine translation for specified keys into target languages. Returns a batch job ID — use get_batch_job_status to poll for completion.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| keyNames | array | yes | Names of keys to translate |
| namespace | string | – | Optional: namespace of the keys |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| targetLanguageTags | array | yes | Language tags to translate into (e.g. ['de', 'fr']) |
No output schema declared.
No examples provided.
search_keys ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| languageTag | string | – | Optional: language tag to search translations in |
| page | number | – | Optional: page number (0-based, default 0) |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| query | string | yes | Search query (matches key name or translation text) |
No output schema declared.
No examples provided.
set_translation ~126
Set or update translations for a key in one or more languages. The key must already exist — use create_keys to create it first.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| keyName | string | yes | The translation key name |
| namespace | string | – | Optional: namespace of the key |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| translations | object | yes | Translations as {languageTag: text} map (e.g. {"en": "Hello", "de": "Hallo"}) |
No output schema declared.
No examples provided.
store_big_meta ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| relatedKeysInOrder | array | yes | List of related keys in the order they appear together |
No output schema declared.
No examples provided.
tag_keys ~95
Add tags to translation keys. Creates tags if they don't exist.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional: branch name |
| keyNames | array | yes | Names of the keys to tag |
| namespace | string | – | Optional: namespace of the keys |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
| tags | array | yes | Names of the tags to add |
No output schema declared.
No examples provided.
update_key ~152
Update an existing translation key's name, namespace, or description
| Name | Type | Req | Description |
|---|---|---|---|
| keyBranch | string | – | Optional: branch name (used to find the key, for branching projects) |
| keyName | string | yes | Current key name (used to find the key) |
| keyNamespace | string | – | Optional: current namespace of the key (used to find the key) |
| newDescription | string | – | Optional: new description for the key |
| newName | string | yes | New key name (provide the current name if unchanged) |
| newNamespace | string | – | Optional: new namespace for the key |
| projectId | number | – | ID of the project (required for PAT, auto-resolved for PAK) |
No output schema declared.
No examples provided.
What is the Tolgee MCP server?
Tolgee is an MCP server listed in the public MCP registry as io.github.tolgee/tolgee. Your app's translations in Tolgee: search keys, create translations, trigger machine translation. This page covers its hosted endpoint (https://app.tolgee.io/mcp/developer).
Is the Tolgee MCP server safe to use?
Tolgee scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tolgee MCP server expose?
Tolgee exposes 22 tools: get_batch_job_status, machine_translate, store_big_meta, list_branches, create_branch, and 17 more. Their descriptions and schemas cost roughly 2,106 tokens of context every time the server is loaded.
Does the Tolgee MCP server require authentication?
No. We connected to Tolgee without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tolgee MCP server still maintained?
Tolgee is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.