Developers

Your coding agent can do the translating

LocalizeMe ships an MCP server, so Claude Code, Cursor and any other MCP client can read and write your translations directly — add a key while writing the feature that needs it, then export the files your build expects. No copy-paste, no separate dashboard trip.

Included on every plan, the free one too.

Connect it

Create an API key from Developer access in the dashboard, then point your client at the MCP endpoint. That is the whole setup.

mcp.json

{
  "mcpServers": {
    "localizeme": {
      "url": "https://api.localizeme.app/mcp",
      "headers": {
        "Authorization": "Bearer lz_live_8f3a92c1…"
      }
    }
  }
}

Streamable HTTP transport. Every call runs as the key's user, passes the same permission checks as the REST API, and is attributed to them in the project's activity history.

What it can do

19 tools, covering everything the dashboard does.

Projects

Find a project, create one, change the languages it targets.

list_projectsget_projectcreate_projectupdate_projectdelete_project

Keys

Add and edit the keys your code references.

list_keysget_keycreate_keyupdate_keydelete_key

Translations

Set values per language and platform, and move them through review.

set_translationsdelete_translationset_translation_status

Languages

Browse the shared catalog or define a language a project needs.

list_languagesadd_custom_languageremove_project_language

Import & export

The same file handling the dashboard offers, in seven formats.

export_translationsimport_translationsget_export_formats

Or use the REST API

The same API keys work against the REST endpoints, so CI can pull the latest strings at build time in seven formats — JSON, PO, iOS .strings and .xcstrings, Android XML, CSV and YAML.

# every language for a project, as a zip
curl -H "Authorization: Bearer lz_live_…" \
  "https://api.localizeme.app/api/translations/export/json/?project_id=1&language=all"

Get an API key

Free plan · no credit card