Tolgee

REMOTE · APP.TOLGEE.IO · SCANNED AUG 3

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

Available components

+4 this week 70 70 Trust /100

Trust breakdown (6 categories)

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 →

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 Usability77

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · app.tolgee.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http tolgee-tolgee https://app.tolgee.io/mcp/developer

# ~/.codex/config.toml

[mcp_servers.tolgee-tolgee]
url = "https://app.tolgee.io/mcp/developer"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tolgee-tolgee": {
      "type": "remote",
      "url": "https://app.tolgee.io/mcp/developer",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add tolgee-tolgee --url https://app.tolgee.io/mcp/developer --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  tolgee-tolgee:
    url: "https://app.tolgee.io/mcp/developer"

// mcp.json

{
  "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.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 65

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	23 Jun 2026	21 Sept 2026	RSA 2048	SHA256-RSA	56302eb288b0dc9d93824fbf9cdc03c130a
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

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

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

MCP tools — 22 exposed · ~2,106 tokens

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.

Tool Tokens

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).

Input Output Examples

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.

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	65
27 Jul	66
28 Jul	66
29 Jul	67
30 Jul	68
31 Jul	68
1 Aug	69
2 Aug	69
3 Aug	70