Tolgee MCP Server
The Tolgee MCP Server brings the full power of Tolgee into your AI coding assistant, letting you manage translations without ever leaving your editor. Connect Claude Code, Cursor, or any MCP-compatible AI assistant to your Tolgee project and start managing localization tasks conversationally.
What is the Tolgee MCP server?
The Tolgee MCP server is the Model Context Protocol endpoint built into the Tolgee platform. It lets AI assistants (Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any other MCP-compatible client) manage your Tolgee localization projects through natural language.
It is hosted at https://app.tolgee.io/mcp/developer for Tolgee Cloud and is available on every self-hosted Tolgee instance. No proxy, no separate process. Your AI client talks to Tolgee directly over HTTP.
The server is maintained by the Tolgee team and listed in the MCP Registry as io.github.tolgee/tolgee.
Which MCP clients are supported?
The Tolgee MCP server uses the standard streamable-HTTP MCP transport, so it works with any MCP-compatible client that supports remote HTTP servers. You authenticate in one of two ways: sign in with your Tolgee account in the browser (OAuth, supported by clients such as Claude Code and VS Code), or pass a Project API Key or Personal Access Token in the X-API-Key header. The setup guide covers both.
Available Roles
The MCP server currently exposes a single role-based endpoint:
| Role | Endpoint | Description |
|---|---|---|
| Developer | /mcp/developer | Full access to keys, translations, languages, tags, namespaces, branches, and batch operations. |
More roles (e.g. translator, project manager) are planned for future releases.
How to Get Started
- Follow the setup guide to connect your AI client to Tolgee.
- Check the usage guide for example workflows and best practices.
How does the Tolgee MCP server compare to the Tolgee CLI and REST API?
All three talk to the same underlying Tolgee API but target different workflows. The Tolgee MCP server is for natural-language use from inside an AI assistant. The Tolgee CLI is for scripted, repeatable operations such as push and pull in CI pipelines. The Tolgee REST API is for building your own integrations, dashboards, or in-product features. They are complementary, not alternatives, most teams end up using two or three.
| Tolgee MCP server | Tolgee CLI | Tolgee REST API | |
|---|---|---|---|
| Best for | Conversational use from AI assistants | Scripts, CI sync/push/pull | Building your own apps & integrations |
| Where you use it | Claude, Cursor, ChatGPT, Windsurf… | Terminal | Your code (any language) |
| Auth | Sign in with your Tolgee account, or PAK/PAT via X-API-Key | Sign in with your Tolgee account, or PAK/PAT | PAK or PAT |
| Discoverability | High (AI lists tools and prompts for missing params) | Medium (use tolgee --help) | Low (read the OpenAPI spec) |
| Determinism | Lower — natural language can be ambiguous | High | High |
| Bulk / batch ops | ✔ | ✔ | ✔ |
A common end-state of our users:
- MCP server — day-to-day exploratory work and one-off fixes from inside Claude or Cursor.
- CLI — committed sync between repo and Tolgee in CI (e.g.
tolgee pushon merge tomain). - REST API — in-app translation lookup, custom dashboards, or webhooks.