Can I use Lokalise as a CLI?

Yes. KosmoKrator exposes a Lokalise CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Lokalise through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Lokalise tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Lokalise credentials stored?

Lokalise credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Lokalise MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Lokalise CLI for Coding Agents

Use the Lokalise CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API token auth

Submit Lokalise feedback View package source

Lokalise CLI for Coding Agents

Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

Use this pattern when another coding agent needs exact commands and schema discovery. The Lokalise CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Lokalise CLI for Coding Agents
kosmokrator integrations:configure lokalise --set api_token="$LOKALISE_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call lokalise.lokalise_list_projects '{"limit":1,"page":1}' --json

Discovery Before Execution

Agents and scripts can inspect Lokalise docs and schemas before choosing a function.

kosmo integrations:docs lokalise --json
kosmo integrations:docs lokalise.lokalise_list_projects --json
kosmo integrations:schema lokalise.lokalise_list_projects --json
kosmo integrations:search "Lokalise" --json
kosmo integrations:list --json

Useful Lokalise CLI Functions

Function	Type	Parameters	Description
`lokalise.lokalise_list_projects`	Read	limit, page	List Lokalise projects. Returns project IDs, names, languages, and other metadata. Supports pagination.
`lokalise.lokalise_get_project`	Read	project_id	Get details of a specific Lokalise project. Returns project name, description, languages, statistics, and settings.
`lokalise.lokalise_list_keys`	Read	project_id, limit, page	List translation keys in a Lokalise project. Returns key IDs, names, platforms, and other metadata. Supports pagination.
`lokalise.lokalise_get_key`	Read	project_id, key_id	Get details of a specific translation key in a Lokalise project. Returns key name, platforms, translations, and other metadata.
`lokalise.lokalise_create_key`	Write	project_id, key_name, platforms, translations, description, tags	Create a new translation key in a Lokalise project. The key name and optional translations for each language can be provided.
`lokalise.lokalise_list_translations`	Read	project_id, limit, page	List translations in a Lokalise project. Returns translation values, language codes, and key references. Supports pagination.
`lokalise.lokalise_get_current_user`	Read	none	Get the currently authenticated Lokalise user. Returns user email, name, and account details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Lokalise CLI Pages

CI Lokalise CLI for CI. Cron Jobs Lokalise CLI for cron jobs. Shell Scripts Lokalise CLI for shell scripts. Headless Automation Lokalise CLI for headless automation.