locli
Enables coding agents to manage and localize Android app texts and store listings through locli, including adding and translating strings and validating placeholders, plurals, glossary, and tone before release.
Enables coding agents to manage and localize iOS app texts and store listings through locli, including adding and translating strings and validating placeholders, plurals, glossary, and tone before release.
locli
All your app's texts. Every language. locli is the one place for the texts of your iOS, Android and web app and its store listings. Your coding agent adds and translates them, locli checks every one (placeholders, plurals, glossary, tone), and nothing ships until you approve a release.
This repository holds what runs on your machine:
Folder | What |
| |
The Claude Code plugin: a skill that tells the agent when and how to use locli, plus the MCP server | |
The full agent skill that |
Get started
In your app's repository:
npx @locli/cli initOr ask your coding agent: "Set up locli for this app's texts." (docs: https://locli.dev/docs/agents.md).
Claude Code
/plugin marketplace add mariohahn/locli
/plugin install locli@locliCursor, Codex and other MCP clients
{ "mcpServers": { "locli": { "command": "npx", "args": ["-y", "@locli/cli", "mcp"] } } }Sign in once with npx @locli/cli login (it opens the browser to approve the CLI). CI uses
a project token in LOCLI_TOKEN.
Related MCP server: i1n
Data
The CLI and MCP server talk to one service: the locli server in locli.json (apiURL,
default https://locli.dev, hosted in Frankfurt). They send the app's texts, their keys,
comments and plural forms, and short usage notes such as "used as a toolbar item"; they do not
send source code or file contents. Texts stay in the locli project until it is deleted. The
sign-in token is stored in ~/.config/locli/credentials.json (or $XDG_CONFIG_HOME), readable
only by you. Privacy policy: https://locli.dev/app/privacy/
Issues
Bugs and ideas: open an issue. The locli server and web app are not part of this repository.
License: MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Agentic localization for documents and media, with quality checks and optional human review.
Localize apps from your AI assistant: translate locale files, set glossaries, connect GitHub repos.
Find missing translations in your app, propose texts and publish and deploy them to your CDN.
AI localization for agents: translation, TMS sync, translation memories, glossaries, post-editing.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI-powered translation management built for AI agents. Automate localization with regional sensitivity and zero TMS overhead. Works with Claude Code, Cursor, VS Code via MCP protocol. Supports JSON, YAML, Markdown, PO and more.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceLocalization as code — push, pull, translate, and extract strings from code with AI. 7 MCP tools for type-safe i18n across 182 languages.125 npm2MIT
- AlicenseAqualityBmaintenanceAI localization from your editor — translate an app's string files into 46 languages with placeholder-safe, reproducible output. Eleven formats (JSON, .arb, .po, .strings, Android XML and more), and every translation is read back and checked before it lands.7339 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents, developers, and CI pipelines to run deterministic, offline localization QA — pseudolocalization, locale linting for separators/dates/placeholders/RTL, and glossary enforcement across 20 locales — without any network access or API key. When an OpenAI-compatible endpoint is configured, it can also translate into multiple locales and lint the results, or otherwise emit structured translation jobs instead of fabricating translations.3 npmMIT