Connect Claude Code, Cursor, VS Code Copilot or any MCP client. Your agent adds strings in your base language while it codes, Glotra translates them, and a person approves them in the review queue.
Agents translate. Humans approve. Free for 14 days. No card required.
Your coding agent adds the key over MCP while it writes the feature, in the project's base language.
Add Glotra to Claude Code, Cursor, VS Code or any MCP client, and sign in. There is nothing to install.
While it writes the feature, the agent checks for an existing key, then calls add_key with text in your base language.
Every project language is machine-translated in the same call. The agent hears about anything that couldn't be filled.
Agent and machine text is flagged in the dashboard. Your team approves it or corrects it, and history keeps who did.
Get a zip per platform — en.lproj, values-ar, JSON — or pull the text with a project API key.
Glotra is an MCP server, so Claude Code, Cursor and VS Code Copilot can search your projects and add keys while they work, with the same permissions you have in Glotra.
The agent adds a key in English. Glotra fills every other project language and lists anything that still needs a translator.
Sign in with Glotra and approve what the app may do. Viewers stay read-only, deleting is off unless you allow it, and you can limit it to chosen projects.
Paste one URL into Claude, Cursor or VS Code. Every connection appears under Connected apps, where you or an admin can disconnect it.
Added checkout.pay_button in English and machine-translated it into Arabic and French. Both are waiting for review in Glotra.
Everything an agent or machine translation writes is flagged until a person approves it or corrects it. No MCP tool can clear the flag.
Review flags text rather than holding it back: flagged translations are still in your exports, so a backlog never breaks a build. Clear the list before you release.
Start freeWritten by machine translation for you@company.com (via Cursor).
Filter to what is unfinished, by platform, tag or language, and clear it without leaving the list.
One, few, many, other — per language, with the right export shape for each platform.
Every value keeps its author, source and timestamp, with a word-level diff between revisions.
Group keys by feature or release, and give translators the context a key name can't carry.
Admin, editor and viewer roles, with team grants scoped to the projects each team owns.
Each organization is provisioned its own database, so tenants never share storage.
Bring Web JSON, iOS .strings and .stringsdict, or Android XML. Glotra matches keys across files and tags them in one pass.
Keys carry the platforms they belong to, so an iOS-only string never lands in the web bundle.
Every project issues its own API key. Fetch the current strings for one platform and language in CI, or wire the export into your release script.
Billed per organization, monthly or annually. Every plan starts with a 14-day trial. Cancel whenever.
No. Signing up creates a free workspace with a 14-day trial — one project, 100 keys and a single seat. Add a card only when you are ready to move to a paid plan.
Yes. Import Web JSON, iOS .strings and .stringsdict, or Android XML, and export the same formats back. Glotra sits between them rather than replacing them.
Every key records the platforms it belongs to, so an iOS export contains only the keys marked for iOS. You can also filter the key list by platform while you work.
No. In the dashboard it is optional and runs per key across about 30 languages. Over MCP, add_key translates by default unless the agent turns that off. Either way, machine-written text is flagged for human review.
Text written by machine translation or an AI agent is flagged. A person with editor access approves it, one value at a time or for the whole project, under Needs review in the dashboard. Editing a flagged value also clears the flag. Approved or edited values record who did it.
Admins and editors can edit; viewers read and export only. Grants narrow access further to specific projects, for one person or for a whole team.
Call the export endpoint with a project API key and you get back JSON keyed by language, with simple strings and plurals separated — so a copy change ships without a new build.
Yes. Glotra is an MCP server, so Claude Code, Cursor, VS Code Copilot and other MCP clients can list your projects, search keys, and add or edit keys while you work. Add the server URL to your client, sign in with your Glotra account, and approve what the app may do.
Each organization is provisioned its own database for its projects, keys and translations, so no tenant shares storage with another. The accounts and permissions layer is separate again, with database-level row security as a second backstop.
See all questions — imports, permissions, billing and security in full.
Connect one URL, add a key from your editor, and review it in Glotra. Agents translate. Humans approve.