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 MCP Integration for CrewAI

Connect Lokalise to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API token auth

Submit Lokalise feedback View package source

Connect Lokalise to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Lokalise MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-lokalise": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=lokalise",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=lokalise --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Lokalise instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Lokalise Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Lokalise integration catalog.

MCP tool	Source function	Type	Description
`integration__lokalise__lokalise_list_projects`	`lokalise.lokalise_list_projects`	Read	List Lokalise projects. Returns project IDs, names, languages, and other metadata. Supports pagination.
`integration__lokalise__lokalise_get_project`	`lokalise.lokalise_get_project`	Read	Get details of a specific Lokalise project. Returns project name, description, languages, statistics, and settings.
`integration__lokalise__lokalise_list_keys`	`lokalise.lokalise_list_keys`	Read	List translation keys in a Lokalise project. Returns key IDs, names, platforms, and other metadata. Supports pagination.
`integration__lokalise__lokalise_get_key`	`lokalise.lokalise_get_key`	Read	Get details of a specific translation key in a Lokalise project. Returns key name, platforms, translations, and other metadata.
`integration__lokalise__lokalise_create_key`	`lokalise.lokalise_create_key`	Write	Create a new translation key in a Lokalise project. The key name and optional translations for each language can be provided.
`integration__lokalise__lokalise_list_translations`	`lokalise.lokalise_list_translations`	Read	List translations in a Lokalise project. Returns translation values, language codes, and key references. Supports pagination.
`integration__lokalise__lokalise_get_current_user`	`lokalise.lokalise_get_current_user`	Read	Get the currently authenticated Lokalise user. Returns user email, name, and account details.

Related Lokalise Pages

Lokalise CLIUse direct JSON commands instead of MCP discovery. Lokalise MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.