Lokalise for AI agents
Lokalise is a localization management platform that helps teams manage translation keys, files, and contributors across multilingual products and marketing content. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Lokalise.
Add a new translation key
Create a new key with source text so translators can add it to their language files.
Check a project's translations
Pull existing translations for a key across languages to check for consistency, read-only.
Approve before deleting keys
Require approval before deleting translation keys, since it removes them from every language.
10 Lokalise actions, graded by risk.
Every Lokalise action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- lokalise.list_keysList Keys
- lokalise.list_branchesList Branches
- lokalise.list_projectsList Projects
- lokalise.list_audit_logsList Audit Logs
- lokalise.list_translationsList Translations
- lokalise.list_project_languagesList Project Languages
write
3Create and change things. Allow, or ask the user first.
- lokalise.create_keysCreate Keys
- lokalise.update_keysUpdate Keys
- lokalise.update_translationUpdate Translation
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- lokalise.delete_keysDelete Keys
Lokalise in three steps.
- 01Your users connect LokaliseThey add their Lokalise api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Keys” can wait for the user, and “delete Keys” can be denied outright.
- 03Any agent can actYour agent calls Lokalise through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('lokalise', { read: 'allow', write: 'ask', // create_keys destructive: 'deny', // delete_keys }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Lokalise connects.
Users add their Lokalise api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Lokalise connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Lokalise from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore project management apps.
Lokalise and Arc0, answered.
Can I use Lokalise with Claude, ChatGPT or Cursor?
Yes. Connect Lokalise to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Lokalise actions you allow.
How do users connect Lokalise?
Users add their Lokalise api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Lokalise actions can my agent take?
10 in total: 6 read, 3 write and 1 destructive, such as “create Keys”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Lokalise?
Yes. Actions like “delete Keys” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Lokalise too?
Yes. The same Lokalise connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Lokalise into your agent.
Your users connect Lokalise once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan