MCP server for syncing translation keys to Lokalise with AI-powered translations
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"lokalise-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Lokalise MCP Integration MCP server for extracting translation keys from code and syncing them to Lokalise with AI-powered translations. ## Features - 🔍 Extract translation keys from git diff and untracked files - 🤖 Three translation modes: No AI, Lokalise AI, or Claude AI - 👀 Interactive preview before creating keys - 🛡️ Content safety guards to prevent harmful translations - 📦 Batch creation with progress tracking (3 keys at a time) - ⚠️ Skip existing keys automatically - 🎯 Supports custom translation functions (t, translate, Translate, etc.) ## Installation ### Prerequisites - Lokalise account with API access - **Optional:** Anthropic API key (only required for Mode 3 - Claude AI translations) - **One of:** - Docker (for Option 1 - easiest, no Python required) - Python 3.10+ with uv/pip (for Options 2-3) ### Option 1: Using uvx (Recommended - Simplest Setup) No installation needed - just works: Configure Claude Code MCP in `~/.config/claude/config.json`: ```json { "mcpServers": { "lokalise": { "command": "uvx", "args": ["lokalise-mcp"], "env": { "LOKALISE_API_TOKEN": "your-api-token-here", "LOKALISE_PROJECT_ID": "your-project-id-here" } } } } ``` **Note:** Add `"ANTHROPIC_API_KEY": "your-anthropic-api-key-here"` only if you want Mode 3 (Claude AI translations). **Benefits:** - ✅ Zero configuration - just 2 required environment variables - ✅ Auto-updates to latest version - ✅ No volume mounts or file path complexity - ✅ Works immediately ### Option 2: Using Docker (Alternative - No Python Required) Docker is available but more complex because the container needs access to your local git repository: ```bash docker pull sidzan/lokalise-mcp:latest ``` Note: Docker setup for this MCP is more complex than API-only MCPs (like mcp-atlassian) because lokalise-mcp needs to read your local git repository files. **We recommend using uvx (Option 1) instead for simplicity.** If you still want Dock…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.