Lokalise MCP Server connects AI assistants to the Lokalise translation management platform, enabling teams to manage localization projects, translation keys, and workflows through natural conversation. Key capabilities include: - Strategic project management with portfolio analysis, project health monitoring, and bottleneck identification - Bulk content operations supporting 1000+ translation keys at once, with filename filtering and platform-specific tagging (iOS, Android, Web) - Global expansion tools for adding languages, tracking translation progress, and analyzing completion metrics - Team orchestration features for managing user groups, permissions, workload distribution, and reviewer assignments - Workflow automation with file processing, translation memory (TM) and machine translation (MT) integration, and multi-stage review pipelines - Real-time monitoring through process dashboards, audit trails, and bulk operation tracking - Enterprise-grade security with multi-layer authentication, secure token handling, and rate limiting

Lokalise MCP Server

> ⚠️ Disclaimer: This is an unofficial, personal project and is not affiliated with, endorsed by, or associated with Lokalise Inc. It uses the open-source Lokalise Node.js SDK to provide MCP integration. All code and implementation are my own work.

Bring the power of Lokalise to your AI assistant

[](https://smithery.ai/server/@AbdallahAHO/lokalise-mcp) [](https://www.npmjs.com/package/lokalise-mcp) [](https://opensource.org/licenses/MIT) [](https://www.typescriptlang.org/) [](https://nodejs.org/)

🎯 What Is This?

The Lokalise MCP Server connects AI assistants like Claude to Lokalise, the leading translation management platform. Through natural conversation, you can manage translation projects, update content, and automate localization workflows—no coding required.

Perfect for: Product Managers • Developers • Localization Teams • Content Teams

---

🚀 Key Features & Capabilities

Transform your localization workflow with 59 tools across 11 domains and 17 pre-built automation templates:

| Feature Category | Capabilities | What You Get | |-----------------|-------------|--------------| | 🎯 Strategic Management | Portfolio analysis, project health monitoring, team coordination | Executive insights, bottleneck identification, resource optimization | | 🔤 Smart Content Operations | Bulk key operations (1000+ at once), filename filtering, platform tagging | Release-ready content management, iOS/Android/Web coordination | | 🌍 Global Expansion | Language addition, progress tracking, completion analytics | Market entry automation, translation velocity insights | | 👥 Team Orchestration | User groups, permissions, workload distribution, reviewer assignment | Optimal team structure, timezone-aware assignments | | 🔄 Workflow Automation | File processing, TM+MT integration, multi-stage review pipelines | End-to-end automation, quality gates, escalation rules | | 📊 Real-time Monitoring | Process dashboards, audit trails, bulk operation tracking | Operational visibility, failure detection, performance metrics | | 🔒 Enterprise Security | Multi-layer auth, secure token handling, rate limiting | Production-ready security, compliance support |

🎯 Why to use Lokalise MCP?

| Traditional Approach | With Lokalise MCP | |--------------------------|----------------------| | Manual project analysis across multiple screens | "Analyze my portfolio" → Instant strategic insights | | Hours setting up review workflows | "Create review tasks for uploaded file" → Done in seconds | | Complex team permission management | "Set up teams for 3 new markets" → Automated structure | | Reactive problem-solving | Proactive bottleneck identification and recommendations | | Tool-by-tool operations | Orchestrated multi-tool workflows with one prompt |

✨ See It In Action

Copy these prompts to experience sophisticated multi-tool orchestration. From simple requests to advanced patterns—Claude handles the complexity automatically:

💻 React i18n Development Workflow (Cursor IDE)

`` Prompt: "I'm working on a new checkout flow in React. Please scan my current components, extract all hardcoded strings that need internationalization, convert them to i18n keys using our naming convention (checkout.step1.title), refactor the JSX to use our i18next hooks, then sync the new keys to our 'Mobile App' project in Lokalise and create translation tasks for our EU markets using relevant tools in configured Lokalise MCP.

Use these exact Lokalise MCP tools:

What Claude orchestrates with MCP tools: ✓ lokalise_list_projects - Locates 'Mobile App' project ✓ lokalise_list_keys - Validates against existing keys to prevent duplicates ✓ lokalise_create_keys` - Bulk uploads new i18n keys with platform tags: [{ key_name: "checkout.payment.title", platforms: ["web", "ios", "android"], translations: [{ language_iso: "en", translat