Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tolgee

REMOTE · APP.TOLGEE.IO

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

Available components

−1 this week 93 Trust /100

Last scanned (22 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2887 tokens (~115/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management95
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 25 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 0
    • Server version: v3.245.0 → v3.246.0 functional
  • 19 Nov 26 −1
    • New tool “accept_suggestion”, which the server declares destructive security
    • New tool “decline_suggestion”, which the server declares destructive security
    • Schema quality: 2299 → 2887 ▼ functional
    • Server version: v3.243.0 → v3.245.0 functional
    • New tool “list_keys_with_suggestions” functional
    • New tool “list_suggestions” functional
  • 17 Nov 26 0
    • Server version: v3.242.7 → v3.243.0 functional
  • 14 Nov 26 0
    • Server version: v3.242.5 → v3.242.7 functional
  • 12 Nov 26 0
    • Server version: v3.242.4 → v3.242.5 functional
  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 92 to 95.

  • 8 Nov 26 −1

    No change was recorded against any check on this day. Stability & Change Management went from 95 to 92.

  • 7 Nov 26 0
    • Server version: v3.242.2 → v3.242.4 functional
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 21 Nov 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=YR1,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 RSA 2048 SHA256-RSA 6934e015fc7eaabaa3cff7d28d493d9604f
SANs: app.tolgee.io
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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. DS published 38690 8 Verified
tolgee.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://app.tolgee.io/.well-known/oauth-protected-resource/mcp/developer"

Bearer resource_metadata="https://app.tolgee.io/.well-known/oauth-protected-resource/mcp/developer"
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

Protected resource metadata

Document https://app.tolgee.io/.well-known/oauth-protected-resource/mcp/developer
Retrieved Yes
Resource https://app.tolgee.io/mcp/developer
Authorisation server https://app.tolgee.io

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
MCP tools · 25 exposed · ~2,887 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. 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 →

Tool Tokens
accept_suggestion ~173

Accept a translation suggestion: its text becomes the translation of the key in that language. With declineOther, all other active suggestions for the same key and language are declined.

NameTypeReqDescription
branchstring–Optional: branch name
declineOtherboolean–Optional: decline the other active suggestions of this key and language (default false)
keyNamestringyesThe translation key name
languageTagstringyesLanguage tag (e.g. 'de')
namespacestring–Optional: namespace of the key
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
suggestionIdnumberyesID of the suggestion (from list_suggestions)

No output schema declared.

No examples provided.

create_branch ~102

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

NameTypeReqDescription
namestringyesName of the new branch
originBranchIdnumberyesID of the branch to fork from
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

create_keys ~129

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.

NameTypeReqDescription
branchstring–Optional: branch name
keysarrayyesList of keys to create
namespacestring–Optional: default namespace for all keys (individual keys can override)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

create_language ~127

Add a new language to a Tolgee project

NameTypeReqDescription
flagEmojistring–Flag emoji for this language
namestringyesLanguage display name (e.g. 'German')
originalNamestring–Native name of the language (e.g. 'Deutsch')
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
tagstringyesLanguage tag / IETF BCP 47 code (e.g. 'de')

No output schema declared.

No examples provided.

decline_suggestion ~122

Decline a translation suggestion.

NameTypeReqDescription
branchstring–Optional: branch name
keyNamestringyesThe translation key name
languageTagstringyesLanguage tag (e.g. 'de')
namespacestring–Optional: namespace of the key
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
suggestionIdnumberyesID of the suggestion (from list_suggestions)

No output schema declared.

No examples provided.

delete_branch ~69

Delete a branch from a Tolgee project.

NameTypeReqDescription
branchNamestringyesName of the branch to delete
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

delete_keys ~93

Delete translation keys from a Tolgee project.

NameTypeReqDescription
branchstring–Optional: branch name
keyNamesarrayyesNames of the keys to delete
namespacestring–Optional: namespace of the keys
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

get_batch_job_status ~85

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

NameTypeReqDescription
jobIdnumberyesID of the batch job
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

get_key ~111

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

NameTypeReqDescription
branchstring–Optional: branch name
keyNamestringyesThe translation key name
namespacestring–Optional: namespace of the key
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

get_project_language_statistics ~73

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

NameTypeReqDescription
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

get_translations ~140

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

NameTypeReqDescription
branchstring–Optional: branch name
keyNamestringyesThe translation key name
languagesarray–Optional: language tags to filter by (e.g. ['en', 'de']). If omitted, returns all languages.
namespacestring–Optional: namespace of the key
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

list_branches ~107

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

NameTypeReqDescription
pagenumber–Optional: page number (0-based, default 0)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
searchstring–Optional: search filter for branch names

No output schema declared.

No examples provided.

list_keys ~106

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.

NameTypeReqDescription
branchstring–Optional: branch name
pagenumber–Optional: page number (0-based, default 0)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

list_keys_with_suggestions ~130

List keys that have pending (active) translation suggestions in a language. Returns up to 100 keys per page; use list_suggestions on a key to see the suggestions themselves.

NameTypeReqDescription
branchstring–Optional: branch name
languageTagstringyesLanguage tag (e.g. 'de')
pagenumber–Optional: page number (0-based, default 0)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

list_languages ~84

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

NameTypeReqDescription
pagenumber–Optional: page number (0-based, default 0)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

list_namespaces ~76

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

NameTypeReqDescription
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

list_projects ~72

List Tolgee projects accessible to the current user. An OAuth token lists only the projects it was authorized for. Returns up to 100 results per page.

NameTypeReqDescription
pagenumber–Optional: page number (0-based, default 0)
searchstring–Optional search query to filter projects by name

No output schema declared.

No examples provided.

list_suggestions ~163

List translation suggestions for a key in one language. Returns up to 100 results per page.

NameTypeReqDescription
branchstring–Optional: branch name
keyNamestringyesThe translation key name
languageTagstringyesLanguage tag (e.g. 'de')
namespacestring–Optional: namespace of the key
pagenumber–Optional: page number (0-based, default 0)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
statesarray–Optional: only suggestions in these states (ACTIVE, ACCEPTED, DECLINED). Default: all.

No output schema declared.

No examples provided.

list_tags ~98

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

NameTypeReqDescription
pagenumber–Optional: page number (0-based, default 0)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
searchstring–Optional: search filter for tag names

No output schema declared.

No examples provided.

machine_translate ~132

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

NameTypeReqDescription
branchstring–Optional: branch name
keyNamesarrayyesNames of keys to translate
namespacestring–Optional: namespace of the keys
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
targetLanguageTagsarrayyesLanguage tags to translate into (e.g. ['de', 'fr'])

No output schema declared.

No examples provided.

search_keys ~150

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.

NameTypeReqDescription
branchstring–Optional: branch name
languageTagstring–Optional: language tag to search translations in
pagenumber–Optional: page number (0-based, default 0)
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
querystringyesSearch query (matches key name or translation text)

No output schema declared.

No examples provided.

set_translation ~141

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

NameTypeReqDescription
branchstring–Optional: branch name
keyNamestringyesThe translation key name
namespacestring–Optional: namespace of the key
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
translationsobjectyesTranslations as {languageTag: text} map (e.g. {"en": "Hello", "de": "Hallo"})

No output schema declared.

No examples provided.

store_big_meta ~127

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.

NameTypeReqDescription
branchstring–Optional: branch name
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
relatedKeysInOrderarrayyesList of related keys in the order they appear together

No output schema declared.

No examples provided.

tag_keys ~110

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

NameTypeReqDescription
branchstring–Optional: branch name
keyNamesarrayyesNames of the keys to tag
namespacestring–Optional: namespace of the keys
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
tagsarrayyesNames of the tags to add

No output schema declared.

No examples provided.

update_key ~167

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

NameTypeReqDescription
keyBranchstring–Optional: branch name (used to find the key, for branching projects)
keyNamestringyesCurrent key name (used to find the key)
keyNamespacestring–Optional: current namespace of the key (used to find the key)
newDescriptionstring–Optional: new description for the key
newNamestringyesNew key name (provide the current name if unchanged)
newNamespacestring–Optional: new namespace for the key
projectIdnumber–ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http tolgee-tolgee 'https://app.tolgee.io/mcp/developer'
Common questions

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 93 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 25 tools: get_batch_job_status, machine_translate, store_big_meta, list_branches, create_branch, and 20 more. Their descriptions and schemas cost roughly 2,887 tokens of context every time the server is loaded.

Does the Tolgee MCP server require authentication?

Yes. Tolgee asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Tolgee MCP server still maintained?

Tolgee is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Tolgee MCP server?

VerifyMCP ran 13 checks on Tolgee, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.