SimpleLocalize
for LuumenAI
Read localization keys and translations, then change them as approved steps.
Connect SimpleLocalize with an API key and Luumen can read your project the way a localization owner does: languages, tags, hosting environments, key metadata, translation state, and recent activity. When something needs to change — a new key, a corrected string, a batch of translations — Luumen shows the exact edit and waits for your approval before it writes.
The SimpleLocalize toolbox
14 tools: 7 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadExport TranslationsCreate downloadable snapshot URLs for project translations in a selected file format.
- ReadGet Project ContextReturn the connected project and its current languages, tags, and hosting environments so an agent can choose valid identifiers before managing translations.
- ReadGet Translation KeyReturn full metadata for one translation key selected by key and namespace.
- ReadList ActivityReturn a manually selected page of recent project changes for operational visibility.
- ReadList File FormatsReturn the file formats currently accepted by SimpleLocalize exports, including multi-language, beta, and deprecation metadata.
- ReadList Translation KeysSearch translation keys and return one controllable page of provider summary fields.
- ReadList TranslationsSearch translations by key, language, text, review state, or namespace and return one page.
- WriteCreate TagCreate a project tag for organizing translation keys. Approval by default
- WriteCreate Translation KeyCreate one translation key and optional metadata in the connected project. Approval by default
- WriteCreate Translation KeysCreate up to 100 translation keys and report every rejected entry; valid entries may still be created when others fail. Approval by default
- WriteDelete TagPermanently delete one project tag by its exact name. Approval by default
- WriteDelete Translation KeyPermanently delete one translation key, including all translations attached to it, by exact key and namespace. Approval by default
- WriteSet TranslationSet the text and optional review state for one existing translation key and language. Approval by default
- WriteSet TranslationsSet 1 to 100 translations in one request. Approval by default
One prompt, start to finish
What a governed SimpleLocalize run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create tag, create translation key, create translation keys, delete tag, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to SimpleLocalize — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put SimpleLocalize to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.