Skip to main content
Glama

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.

NPM Version License: MIT TypeScript Node.js

🎯 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


Related MCP server: i18n Agent

🚀 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)

MCP Tools: lokalise_list_projects → lokalise_list_keys → lokalise_create_keys → lokalise_list_usergroups → lokalise_create_task

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:
- lokalise_list_projects (to find Mobile App project)
- lokalise_list_keys (to check for existing keys)
- lokalise_create_keys (to upload new i18n keys)
- lokalise_list_usergroups (to find EU translation teams)
- lokalise_create_task (to create translation tasks)"

// Before: components/checkout/PaymentStep.tsx
const PaymentStep = () => (
  <div>
    <h2>Payment Information</h2>
    <p>Enter your card details below</p>
    <button>Continue to Review</button>
  </div>
);

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", translation: "Payment Information" }]
  }]
✓ `lokalise_list_usergroups` - Resolves "EU markets" to specific translation teams
✓ `lokalise_create_task` - Creates translation tasks for DE, FR, ES, IT with team assignments
✓ Auto-refactors JSX to use useTranslation hooks
✓ Updates local i18n JSON files with new key structure

// After: Automatically refactored
const PaymentStep = () => {
  const { t } = useTranslation();
  return (
    <div>
      <h2>{t('checkout.payment.title')}</h2>
      <p>{t('checkout.payment.subtitle')}</p>
      <button>{t('checkout.payment.continue')}</button>
    </div>
  );
};

Result: Code internationalized, 12 new keys synced via Lokalise MCP tools,
translation tasks created for 4 languages—all without leaving your IDE.
Development workflow stays uninterrupted while localization setup happens
automatically through direct lokalise MCP integration.

📊 CSV Translation Upload Automation

Triggers: lokalise_list_projects → CSV parsing → lokalise_create_keys (bulk) → lokalise_list_project_languages → lokalise_create_task (per language)

Prompt: "I'm attaching our latest feature strings export from Product. It's a CSV with
columns: key_id, context, en_source, es_draft, fr_draft. Using relevant tools in configured Lokalise MCP; Please upload these 50 new keys to our 'E-commerce Platform' project, create translation tasks for the missing
languages (German, Italian, Portuguese), and assign them to our relevant regional teams.
The Product team wants this shipped by end of sprint (March 15th)."

[Attach: feature_v3_strings.csv]

What Claude orchestrates:
✓ Parses CSV and validates column structure
✓ Locates E-commerce Platform project
✓ Creates 50 keys with English source + Spanish/French drafts
✓ Identifies missing target languages (DE, IT, PT)
✓ Resolves regional team assignments automatically
✓ Creates separate translation tasks per language/team
✓ Sets March 15th deadline with buffer for review
✓ Provides upload summary + task tracking URLs

Result: 50 keys uploaded, 3 translation tasks created, teams notified—
what used to take 2 hours of manual CSV imports, key creation, and task setup
now happens in 30 seconds with full audit trail and team coordination.

🎯 Strategic Portfolio Dashboard

Triggers: lokalise_list_projects → lokalise_get_project (parallel) → lokalise_list_project_languages → lokalise_list_tasks

Prompt: "I need a strategic overview of my localization portfolio. Using relevant tools in configured Lokalise MCP;
Show me which projects need immediate attention, identify bottlenecks across teams, and give me data-driven
recommendations for resource allocation. Include completion rates, task backlogs, and
any projects that haven't seen activity in the last 30 days."

What Claude does automatically:
✓ Fetches all projects with statistics
✓ Analyzes each project's health in parallel
✓ Cross-references team workloads
✓ Identifies stalled projects and overdue tasks
✓ Generates strategic recommendations

Result: Executive-level insights you can act on immediately

🔄 Intelligent File Processing Workflow

Triggers: lokalise_list_projects → lokalise_list_keys (filter by filename) → lokalise_list_usergroups + lokalise_list_contributors → lokalise_list_project_languages → lokalise_create_task (multiple)

Prompt: "I just uploaded 'user-onboarding-v2.json' to my Mobile App project via the Lokalise UI.
The TM+MT processing is done. Now create review tasks for quality assurance - assign
Spanish content to our EMEA translation team, French to Marie (marie@ourcompany.com),
and German to whoever is available on the DACH team. Set the deadline for next Friday."

What Claude orchestrates:
✓ Locates your Mobile App project
✓ Finds all keys from the uploaded file
✓ Resolves "EMEA translation team" → user group ID
✓ Resolves "marie@ourcompany.com" → contributor ID
✓ Finds DACH team members and assigns optimally
✓ Creates separate review tasks per language
✓ Sets appropriate deadlines and task descriptions

Result: Complete review workflow ready in seconds, not minutes of manual setup

🚀 Bulk Operations with Smart Validation

Triggers: lokalise_list_projects → lokalise_list_keys (filtered) → lokalise_bulk_update_keys → lokalise_list_tasks → lokalise_create_task

Prompt: "I need to clean up our iOS release. Find all keys tagged 'onboarding' across all
projects, ensure they have iOS platform designation, verify they're all translated to
Spanish and French, and create catch-up tasks for any missing translations. Also check
if any of these keys have been changed in the last 7 days and might need re-review."

What Claude coordinates:
✓ Searches across all projects for 'onboarding' tagged keys
✓ Audits platform tags and adds iOS where missing
✓ Cross-checks translation completeness for Spanish/French
✓ Identifies recently modified keys needing re-review
✓ Creates targeted tasks for missing translations
✓ Provides summary of changes and remaining work

Result: Release-ready content with full audit trail and completion plan

💡 Master Tip: The more context and constraints you provide, the smarter Claude's orchestration becomes. Include timelines, priorities, team constraints, and business objectives for maximum AI leverage.


🎯 Built-in Workflow Prompts

Beyond these examples, the MCP server includes 17 sophisticated prompt templates that orchestrate complex multi-tool workflows automatically. These aren't just examples—they're production-ready templates you can use immediately.

📋 Project Management Suite

Ready-to-use prompts for strategic project oversight:

Prompt Template

What It Does

Tools Orchestrated

project_portfolio_overview

Strategic analysis across all projects with bottleneck identification

4-6 tools in parallel

project_deep_dive

Comprehensive health analysis of a specific project

6-8 tools coordinated

new_project_setup

Complete project creation with languages and initial structure

5-7 tools sequenced

project_cleanup

Safe removal of deprecated content with impact analysis

3-5 tools with validation

🌍 Localization Workflow Suite

Automated language expansion and progress monitoring:

Prompt Template

What It Does

Tools Orchestrated

language_expansion

Add new markets with proper configuration and team setup

4-6 tools coordinated

translation_progress_check

Comprehensive progress analysis with actionable insights

3-5 tools in parallel

bulk_key_creation

Smart content organization for new features

3-4 tools sequenced

🔄 Advanced Workflow Automation

Sophisticated multi-stage orchestration:

Prompt Template

What It Does

Tools Orchestrated

post_upload_review_workflow

Complete review pipeline for uploaded files with team assignment

6-8 tools orchestrated

document_extraction_review_workflow

Extract uploaded CSV/JSON content as keys + create translation tasks

5-7 tools coordinated

automated_review_pipeline

Multi-stage review with quality gates and escalation

8-10 tools orchestrated

team_translation_setup

Organize teams with optimal workload distribution

6-8 tools coordinated

🚀 Enterprise Automation Suite

Production-ready workflows for complex operations:

Prompt Template

What It Does

Tools Orchestrated

process_monitoring_dashboard

Real-time monitoring across projects with failure detection

4-6 tools in parallel

user_group_audit

Comprehensive team analysis with security recommendations

5-7 tools coordinated

translation_memory_import

Smart TM integration with conflict resolution

6-8 tools orchestrated

bulk_operations_monitor

Track and audit large-scale changes with rollback info

4-6 tools coordinated

team_onboarding_workflow

Complete new member setup with permissions and training

5-7 tools sequenced

🎭 How to Use Prompt Templates

# In Claude, simply reference the prompt name:
"Use the project_portfolio_overview prompt from configured Lokalise MCP to analyze my localization portfolio"

# Or trigger directly with parameters:
"Run the post_upload_review_workflow from configured Lokalise MCP  for 'user-guide.pdf' in Mobile App project,
assign Spanish to EMEA Team and French to marie@company.com"

# Customize for your needs:
"Use the team_translation_setup prompt from configured Lokalise MCP but focus on timezone optimization
for our distributed team across 4 continents"

Template Benefits:

  • 🎯 Zero Learning Curve: Pre-built workflows ready to use

  • 🚀 Multi-Tool Orchestration: Each template coordinates 3-10 tools automatically

  • 🧠 Context Awareness: Smart parameter resolution and error handling

  • 📊 Rich Outputs: Formatted reports with actionable insights

  • ⚡ Production Ready: Battle-tested in real localization projects


📦 Quick Start

Get up and running in under 60 seconds:

🚀 Recommended: One-Click Install

# Install for Claude Desktop (most popular)
npx -y @smithery/cli install @AbdallahAHO/lokalise-mcp --client claude

# Other clients: cursor, vscode, raycast, gemini

What happens: Auto-installs, configures permissions, prompts for your Lokalise API key, ready to use.

🎯 Alternative Installation Methods

Fast local install, no Node.js required:

  1. Download the latest .dxt from Releases

  2. Double-click or drag into Claude Desktop → Settings → Extensions

  3. Enter your LOKALISE_API_KEY when prompted

  4. Verify: "Can you list my Lokalise projects?"

Run directly without installing:

# Direct execution
npx lokalise-mcp

Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "lokalise": {
      "command": "npx",
      "args": ["-y", "lokalise-mcp"],
      "env": {"LOKALISE_API_KEY": "your-api-key-here"}
    }
  }
}
npm install -g lokalise-mcp
lokalise-mcp  # Run the server

🔑 Get Your API Key

  1. Log in to Lokalise

  2. Go to Profile → API Tokens (https://app.lokalise.com/profile#apitokens)

  3. Click Generate new token

  4. Copy and save securely

⚙️ Configuration

API Key Setup

The Lokalise API key can be configured in multiple ways (in order of priority):

  1. Environment Variable (Recommended for security):

    export LOKALISE_API_KEY="your-api-key-here"
  2. .env File (For local development):

    cp .env.example .env
    # Edit .env and add your API key
  3. Global MCP Config (~/.mcp/configs.json):

    {
      "lokalise-mcp": {
        "LOKALISE_API_KEY": "your-api-key-here"
      }
    }

Getting Your API Token

  1. Log in to Lokalise

  2. Navigate to Profile → API Tokens (https://app.lokalise.com/profile#apitokens)

  3. Click Generate new token

  4. Copy the token and save it securely

🚀 Running the Server

# HTTP mode (recommended for development)
npm run mcp:http

# STDIO mode (for Claude Desktop integration)
npm run mcp:stdio

# CLI mode (direct commands)
npm run cli -- list-projects

🤖 Using with Claude Desktop

Quick Verification

Once installed, you can verify the connection by asking Claude:

"Can you list my Lokalise projects?"

Claude will use the lokalise_list_projects tool to fetch and display your projects.

Claude Desktop Setup

If installed via Smithery, no manual config is needed. Verify by looking for the 🔌 icon and asking Claude: “Can you list my Lokalise projects?”

✅ Verification

Once installed, test the connection:

"Can you list my Lokalise projects?"

Claude will use the lokalise_list_projects tool and display your projects with statistics.

📚 Available Tools

The server provides 59 MCP tools covering all major Lokalise operations across 11 domains:

Projects (6 tools)

  • lokalise_list_projects - List all projects with statistics

  • lokalise_get_project - Get detailed project information

  • lokalise_create_project - Create a new project

  • lokalise_update_project - Update project settings

  • lokalise_delete_project - Delete a project

  • lokalise_empty_project - Remove all keys from a project

Keys (7 tools) - Enhanced with file filtering

  • lokalise_list_keys - List keys with NEW: filterFilenames support

  • lokalise_get_key - Get detailed key information

  • lokalise_create_keys - Create multiple keys at once (up to 1000)

  • lokalise_update_key - Update a single key

  • lokalise_bulk_update_keys - Update multiple keys

  • lokalise_delete_key - Delete a single key

  • lokalise_bulk_delete_keys - Delete multiple keys

Languages (6 tools)

  • lokalise_list_system_languages - List all available languages

  • lokalise_list_project_languages - List project languages

  • lokalise_add_project_languages - Add languages to project

  • lokalise_get_language - Get language details

  • lokalise_update_language - Update language settings

  • lokalise_remove_language - Remove a language

User Groups (8 tools) - NEW

  • lokalise_list_usergroups - List all user groups

  • lokalise_get_usergroup - Get group details

  • lokalise_create_usergroup - Create new group

  • lokalise_update_usergroup - Update group settings

  • lokalise_delete_usergroup - Delete group

  • lokalise_add_members_to_group - Add members to group

  • lokalise_remove_members_from_group - Remove members from group

  • lokalise_add_projects_to_group - Assign projects to group

Translations (4 tools)

  • lokalise_list_translations - List with cursor pagination

  • lokalise_get_translation - Get translation details

  • lokalise_update_translation - Update a translation

  • lokalise_bulk_update_translations - Bulk updates with rate limiting

Additional Collections

  • Contributors (6 tools) - Manage project team members

  • Tasks (5 tools) - Create and manage translation tasks

  • Comments (5 tools) - Handle key comments and discussions

  • Glossary (5 tools) - Maintain terminology consistency

  • Team Users (4 tools) - NEW - Workspace user management

  • Queued Processes (2 tools) - NEW - Monitor background operations

🛠️ Advanced Configuration

Environment Variables

Variable

Description

Default

LOKALISE_API_KEY

Your Lokalise API token (required)

-

TRANSPORT_MODE

Server mode: http or stdio

http

PORT

HTTP server port

3000

DEBUG

Enable debug logging

false

🐛 Troubleshooting

"Authentication failed"

  • Verify your API token is correct

  • Check token permissions in Lokalise settings

  • Ensure the token has appropriate project access

"Rate limit exceeded"

  • The server includes automatic rate limiting

  • For high-volume operations, consider batching

  • Wait 60 seconds before retrying

"Connection refused"

  • For HTTP mode: Ensure the server is running (npm run mcp:http)

  • For STDIO mode: Check Claude Desktop configuration

  • Verify firewall settings for port 3000

Configuration File Locations

Claude Desktop Config:

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

MCP Global Config:

  • All platforms: ~/.mcp/configs.json

Debug Mode

Enable detailed logging:

# For development
DEBUG=true npm run mcp:http

# In Claude Desktop config
"env": {
  "LOKALISE_API_KEY": "your-key",
  "DEBUG": "true"
}

Getting Help

  1. Check this troubleshooting section

  2. Review GitHub Issues

  3. Enable debug mode for detailed error messages

  4. Contact support with debug logs

📄 License

MIT License - see LICENSE for details.

🤝 Contributing

We welcome contributions! See our Contributing Guide for details on:

  • Setting up the development environment

  • Architecture and code organization

  • Automated CI/CD checks on all PRs

  • Release process and workflow

  • Creating new tools and domains

  • Submitting pull requests

🙏 Acknowledgments


Available Tools

59 tools
lokalise_add_contributorsA

Onboards one or more new team members to a project. Required: projectId, contributors array with email and permissions (admin_rights, is_reviewer, languages). Use for team expansion, granting translator access, or adding reviewers. Returns: Added contributors with assigned IDs. Note: Sends invitation emails automatically.

Inputs: projectId (required), contributors (required).

lokalise_add_members_to_groupA

Adds users to a user group, granting them group-based permissions and project access. Required: teamId, groupId, userIds array. Use to onboard team members, assign role-based access, or batch permission updates. Returns: Operation confirmation. Members immediately gain group permissions and project access.

Inputs: teamId (required), groupId (required), userIds (required).

lokalise_add_project_languagesA

Starts translating into new languages by adding them to the project. Required: projectId, languages array with {lang_iso}. Optional per language: custom_iso, custom_name, custom_plural_forms. Use when expanding to new markets or adding regional variants. Returns: Added languages with IDs. Tip: Check system languages first for valid ISO codes.

Inputs: projectId (required), languages (required).

lokalise_add_projects_to_groupA

Adds projects to a user group, granting all group members access to specified projects. Required: teamId, groupId, projectIds array. Use to expand group project scope, onboard projects to existing teams, or batch project assignments. Returns: Operation confirmation. All group members gain immediate project access.

Inputs: teamId (required), groupId (required), projectIds (required).

lokalise_bulk_delete_keysA

Large-scale cleanup removing multiple obsolete keys permanently. Required: projectId, keyIds array. Use for removing deprecated feature sets, post-refactoring cleanup, or major content pruning. Returns: Deletion results. Critical Warning: Irreversible batch operation - all selected keys and translations permanently deleted. Always verify key list before execution.

Inputs: projectId (required), keyIds (required).

lokalise_bulk_update_keysA

Efficiently modifies metadata for multiple keys in one operation. Required: projectId, keys array with {key_id} plus changes. Use for large-scale reorganization, batch platform updates, or systematic tagging. Returns: Updated keys and any errors. Performance: Processes up to 1000 keys per request. More efficient than individual updates for 3+ keys.

Inputs: projectId (required), keys (required).

lokalise_bulk_update_translationsA

Efficiently processes batch translation corrections or approvals. Required: projectId, updates array (up to 100). Each update needs translation_id plus changes. Use for mass approvals, systematic corrections, or importing reviewed content. Returns: Success/error per translation. Performance: ~5 updates/second with automatic rate limiting and retries.

Inputs: projectId (required), updates (required).

lokalise_create_commentsA

Adds one or more comments to a translation key for team collaboration. Required: projectId, keyId, comments array with 'comment' text. Use to ask translators questions, provide context, leave implementation notes, or flag issues. Supports bulk creation for efficiency. Returns: Created comments with IDs. Note: Comments are visible to all project members.

Inputs: projectId (required), keyId (required), comments (required).

lokalise_create_glossary_termsA

Adds new terminology rules to maintain translation consistency. Required: projectId, terms array with {term, definition}. Optional per term: case_sensitive, translatable, forbidden, translations by language. Use for brand names, technical jargon, or untranslatable terms. Returns: Created terms with IDs. Supports bulk creation up to 1000 terms.

Inputs: projectId (required), terms (required).

lokalise_create_keysA

Adds new UI text or content to be translated (up to 1000 keys per request). Required: projectId, keys array with {key_name, platforms}. Optional per key: description, tags, translations. Use for new features, initial setup, or content expansion. Returns: Created keys with IDs and any errors. Tip: Include base language translations to speed up workflow. Pairs with: lokalise_list_keys to verify.

Inputs: projectId (required), keys (required).

lokalise_create_projectA

Initializes a new localization project for an app or service. Required: name. Optional: description, base_lang_iso (default 'en'). Use when starting localization for new products or creating test environments. Returns: Project ID and access details. Next steps: Add languages, upload keys, invite team members.

Inputs: name (required), description, base_lang_iso, languages.

lokalise_create_taskA

Initiates a new batch of translation or review work. Required: projectId, title, languages array. Optional: description, due_date, assignees (applies to all languages), type (translation/review), keys scope. Use to assign work to translators, set deadlines, or organize sprints. Returns: Created task with ID and assignments. Tip: Use assignees for simple same-user-all-languages setup.

Inputs: projectId (required), title (required), description, keys, +12 more.

lokalise_create_usergroupA

Creates a new user group in a Lokalise team for organized permission management. Required: teamId, name, isReviewer, isAdmin. Optional: adminRights, languages, projects, members. Use to establish role-based access control, organize team permissions, or set up project-specific groups. Returns: Created group with assigned ID and configuration.

Inputs: teamId (required), name (required), isReviewer (required), isAdmin (required), +4 more.

lokalise_delete_commentA

Permanently removes a specific comment from a translation key. Required: projectId, keyId, commentId. Use to clean up resolved discussions, remove outdated information, or delete accidental comments. Returns: Confirmation of deletion. Warning: This action cannot be undone. Consider archiving important discussions elsewhere first.

Inputs: projectId (required), keyId (required), commentId (required).

lokalise_delete_glossary_termsA

Removes obsolete or incorrect glossary entries. Required: projectId, termIds array. Use to clean up outdated terminology, remove duplicates, or fix mistakes. Returns: Deletion confirmation. Warning: Removes all term translations and rules. Supports bulk deletion. Consider updating instead of deleting for audit trail.

Inputs: projectId (required), termIds (required).

lokalise_delete_keyA

Permanently removes obsolete content and all its translations. Required: projectId, keyId. Use for removing deprecated features, cleaning typos in key names, or content no longer needed. Returns: Deletion confirmation. Warning: Irreversible - all translations lost. Consider archiving important content first. For multiple keys, use bulk delete.

Inputs: projectId (required), keyId (required).

lokalise_delete_projectA

Permanently destroys a project and ALL its data. Required: projectId. Use for removing test projects or discontinued products. Returns: Deletion confirmation. CRITICAL WARNING: Irreversible - deletes all keys, translations, history, and team assignments. Export data first if needed. Consider emptying instead.

Inputs: projectId (required).

lokalise_delete_taskA

Cancels a work assignment, removing it from assignee queues. Required: projectId, taskId. Use to cancel mistaken tasks, clean completed work, or remove test assignments. Returns: Deletion confirmation. Note: Only removes the assignment - keys and translations remain unchanged. Cannot be undone.

Inputs: projectId (required), taskId (required).

lokalise_delete_team_userA

Removes a user from a Lokalise team. Required: teamId, userId. Use to remove members, clean up permissions, or manage team structure. Returns: Success message with user details.

Inputs: teamId (required), userId (required).

lokalise_delete_usergroupA

Deletes a user group from a Lokalise team, removing all associated permissions. Required: teamId, groupId. Use for cleanup, removing obsolete groups, or restructuring team organization. Returns: Deletion confirmation. Warning: Removes all group assignments - members lose group-based permissions immediately.

Inputs: teamId (required), groupId (required).

lokalise_empty_projectA

Resets project content while preserving settings and team. Required: projectId. Use for major refactoring, starting fresh, or clearing test data. Returns: Operation confirmation. Effect: Removes all keys and translations but keeps languages, team, and project configuration. Safer alternative to deletion.

Inputs: projectId (required).

lokalise_get_commentA

Gets full details of a single comment including complete text and metadata. Required: projectId, keyId, commentId. Use when comment text was truncated in list view or to get exact timestamps. Returns: Complete comment data with author details and creation time. Pairs with: lokalise_delete_comment for comment management.

Inputs: projectId (required), keyId (required), commentId (required).

lokalise_get_contributorA

Retrieves detailed information about a specific team member's access and permissions. Required: projectId, contributorId. Use to verify exact permissions before updates, investigate access issues, or get complete language assignments. Returns: Full contributor profile including all language permissions and administrative rights.

Inputs: projectId (required), contributorId (required).

lokalise_get_current_userA

Checks your own permissions and access level in a project. Required: projectId. Use to verify your administrative capabilities, check language access, or confirm reviewer status before attempting restricted operations. Returns: Your contributor profile with all permissions. Essential before permission-sensitive operations.

Inputs: projectId (required).

lokalise_get_glossary_termA

Fetches complete details for a single glossary term by ID. Required: projectId, termId. Use to understand precise translation rules, check case-sensitivity requirements, or view all language translations for a term. Returns: Full term data including definition, properties, and language-specific translations. Critical for translator guidance.

Inputs: projectId (required), termId (required).

lokalise_get_keyA

Deep-dives into a single content item to understand its complete state. Required: projectId, keyId. Use to investigate translation status, view all language versions, check metadata, or debug issues. Returns: Full key data including all translations, platforms, tags, comments, and history. Essential for detailed analysis or before making targeted updates.

Inputs: projectId (required), keyId (required).

lokalise_get_languageA

Examines detailed settings for a specific project language. Required: projectId, languageId. Use to verify plural rules, check RTL configuration, or understand custom settings. Returns: Complete language configuration including ISO codes, plural forms, and writing direction. Important for languages with complex grammar rules.

Inputs: projectId (required), languageId (required).

lokalise_get_projectA

Deep analysis of a single project's health and configuration. Required: projectId. Optional: includeLanguages (completion rates), includeKeysSummary (content stats). Use for project audits, progress reports, or understanding structure. Returns: Complete project metadata, team info, language progress, key statistics. Essential for project status assessment.

Inputs: projectId (required), includeLanguages, includeKeysSummary.

lokalise_get_queued_processA

Gets detailed status and information about a specific async process (upload, download, etc.). Required: projectId, processId. Use to check process completion, diagnose failures, or get detailed progress information. Returns: Complete process details with logs and status history.

Inputs: projectId (required), processId (required).

lokalise_get_taskA

Investigates a specific work assignment in detail. Required: projectId, taskId. Use to check task progress, view assignee workload, or debug workflow issues. Returns: Complete task data including all assignments, completion percentages, settings, and history. Pairs with: lokalise_update_task for modifications.

Inputs: projectId (required), taskId (required).

lokalise_get_team_userA

Gets detailed information about a specific user in a team. Required: teamId, userId. Use to verify user permissions, check role assignments, or investigate access issues. Returns: Complete user profile with all team permissions and administrative rights.

Inputs: teamId (required), userId (required).

lokalise_get_translationA

Examines a single piece of translated text in detail. Required: projectId, translationId. Use to check exact wording, review status, modification history, or investigate QA issues. Returns: Complete translation data including content, reviewer info, timestamps, and quality flags. Essential for translation debugging.

Inputs: projectId (required), translationId (required), disableReferences.

lokalise_get_usergroupA

Gets detailed information about a specific user group including members, permissions, and project assignments. Required: teamId, groupId. Use to audit group configuration, verify member access, or understand permission structure. Returns: Complete group profile with admin rights, language permissions, and assigned projects/members.

Inputs: teamId (required), groupId (required).

lokalise_list_contributorsA

Lists all team members in a project with their roles and permissions. Required: projectId. Optional: limit (100), page. Use to audit team access, check language assignments, or prepare permission changes. Returns: Contributors with email, role, admin status, and language permissions. Use before adding new members to avoid duplicates.

Inputs: projectId (required), limit, page.

lokalise_list_glossary_termsA

Retrieves paginated glossary terms that define translation rules for consistency. Required: projectId. Optional: limit (100), cursor for pagination. Use to discover defined terminology including brand names, technical terms, and forbidden words. Returns: Terms with properties (case-sensitive, translatable, forbidden) and translations. Essential before translating to prevent terminology errors.

Inputs: projectId (required), limit, cursor.

lokalise_list_key_commentsA

Retrieves all comments for a specific translation key to understand discussion history and context. Required: projectId, keyId. Optional: limit (100), page. Use this to review translator questions, see implementation notes, or audit collaboration on a specific key. Returns: Paginated list of comments with author, timestamp, and content. Pairs with: lokalise_create_comments to continue discussions.

Inputs: projectId (required), keyId (required), limit, page.

lokalise_list_keysC

Explores the project's content structure by listing translation keys. Required: projectId. Optional: limit (100), cursor, filterKeys array, filterPlatforms array, includeTranslations. Use to browse content organization, find specific keys, or audit platform coverage. Returns: Keys with metadata and optional translations. Supports cursor pagination for large projects. Start here to understand project content.

Inputs: projectId (required), limit, page, includeTranslations, +3 more.

lokalise_list_project_commentsA

Fetches all comments across an entire project for a comprehensive overview of team collaboration. Required: projectId. Optional: limit (100), page. Use this to identify keys with active discussions, audit communication patterns, or find unresolved questions. Returns: Comments grouped by key with context. Note: Can be data-intensive for large projects.

Inputs: projectId (required), limit, page.

lokalise_list_project_languagesA

Shows which languages are currently being translated in a project. Required: projectId. Optional: includeProgress (shows completion %), limit, page. Use to audit translation coverage, identify incomplete languages, or prepare reports. Returns: Active languages with progress stats. Start here to understand project's localization scope.

Inputs: projectId (required), includeProgress.

lokalise_list_projectsA

Portfolio overview showing all accessible localization projects. Optional: limit (100), page, includeStats (adds progress/QA data). Use as entry point to discover projects, assess translation health, or find specific project IDs. Returns: Projects with names, IDs, base language, stats. Start here before diving into specific projects.

Inputs: limit, page, includeStats.

lokalise_list_queued_processesA

Lists all background/async processes in a Lokalise project with status tracking. Required: projectId. Optional: limit (100), page. Use to monitor file uploads, downloads, bulk operations, or troubleshoot process issues. Returns: Processes with status, progress, and completion estimates.

Inputs: projectId (required), limit, page.

lokalise_list_system_languagesA

Discovers all languages available in Lokalise platform that can be added to projects. Optional: limit (100), page. Use to find supported languages before project setup, verify language codes, or check RTL/plural form support. Returns: Languages with ISO codes, native names, RTL status, plural forms. Essential before adding new target languages.

Inputs: limit, page.

lokalise_list_tasksA

Monitors ongoing translation work and deadlines across the project. Required: projectId. Optional: filterTitle, filterStatuses array, limit (50), page. Use to track workload, find overdue tasks, or check assignment status. Returns: Tasks with assignees, progress, due dates, and language scope. Essential for project management and workflow monitoring.

Inputs: projectId (required), limit, page, filterTitle, +1 more.

lokalise_list_team_usersA

Lists all users in a Lokalise team with pagination support. Required: teamId. Optional: limit (100), page. Use to audit team composition, check access levels, or prepare team changes. Returns: Users with roles, permissions, and activity status.

Inputs: teamId (required), limit, page.

lokalise_list_translationsA

Low-level inspection of actual translated text across languages. Required: projectId. Optional: limit (100), cursor, filterLangId, filterIsReviewed, filterQaIssues. Use for quality audits, finding untranslated content, or checking specific language progress. Returns: Translation entries with content, status, QA flags. Note: Different from keys - this shows actual text.

Inputs: projectId (required), limit, cursor, filterLangId, +6 more.

lokalise_list_usergroupsA

Lists all user groups in a Lokalise team with pagination support. Required: teamId. Optional: limit (100), page. Use to audit team organization, check group structure, or prepare group management operations. Returns: User groups with names, member counts, permissions, and language assignments. Essential for understanding team hierarchy.

Inputs: teamId (required), limit, page.

lokalise_remove_contributorA

Removes a team member from a project, revoking all access. Required: projectId, contributorId. Use for offboarding, security cleanup, or removing inactive members. Returns: Confirmation of removal. Warning: Immediate effect - contributor loses all project access. Consider permission downgrade instead for temporary changes.

Inputs: projectId (required), contributorId (required).

lokalise_remove_languageA

Drops support for a language by removing it from the project. Required: projectId, languageId. Use when discontinuing localization for a market or cleaning up test languages. Returns: Removal confirmation. Critical Warning: Permanently deletes ALL translations for this language. Export translations first if needed.

Inputs: projectId (required), languageId (required).

lokalise_remove_members_from_groupA

Removes users from a user group, revoking group-based permissions and project access. Required: teamId, groupId, userIds array. Use for role changes, offboarding, or permission cleanup. Returns: Operation confirmation. Warning: Immediate effect - users lose group permissions and project access.

Inputs: teamId (required), groupId (required), userIds (required).

lokalise_remove_projects_from_groupA

Removes projects from a user group, revoking group member access to specified projects. Required: teamId, groupId, projectIds array. Use to limit project scope, offboard projects, or restructure access. Returns: Operation confirmation. Warning: All group members lose immediate project access.

Inputs: teamId (required), groupId (required), projectIds (required).

lokalise_update_contributorA

Modifies a team member's role, permissions, or language access. Required: projectId, contributorId. Optional: admin_rights, is_reviewer, languages array. Use to promote/demote users, adjust language assignments, or fix permission issues. Returns: Updated contributor profile. Note: Cannot modify your own admin rights.

Inputs: projectId (required), contributorId (required), is_admin, is_reviewer, +2 more.

lokalise_update_glossary_termsA

Modifies existing glossary definitions and properties. Required: projectId, terms array with {term_id} plus changes. Use to refine definitions, add language translations, or adjust rules (case-sensitivity, forbidden status). Returns: Updated terms. Supports bulk updates. Changes apply immediately to all future translations.

Inputs: projectId (required), terms (required).

lokalise_update_keyA

Modifies key metadata to improve organization and translator context. Required: projectId, keyId. Optional: key_name, description, platforms, tags. Use to clarify meaning for translators, fix platform assignments, or reorganize content. Returns: Updated key. Note: This updates metadata only - use translation tools to modify actual text. Changes apply immediately.

Inputs: projectId (required), keyId (required), keyData (required).

lokalise_update_languageA

Modifies language settings within a project. Required: projectId, languageId, languageData object. Optional in data: lang_iso, lang_name, plural_forms. Use to fix incorrect configurations, customize language names, or adjust plural rules. Returns: Updated language settings. Changes affect how translations are handled.

Inputs: projectId (required), languageId (required), languageData (required).

lokalise_update_projectA

Modifies project settings and metadata. Required: projectId, projectData object. Optional in data: name, description. Use to rename projects, update descriptions, or fix project information. Returns: Updated project details. Note: Only changes metadata - use other tools for content/language changes.

Inputs: projectId (required), projectData (required).

lokalise_update_taskA

Modifies an active work assignment. Required: projectId, taskId. Optional: title, description, due_date, language assignments, settings. Use to extend deadlines, reassign work, or update scope. Returns: Updated task details. Note: Cannot change task type after creation. Changes notify assignees automatically.

Inputs: projectId (required), taskId (required), taskData (required).

lokalise_update_team_userA

Updates a team user's role (owner, admin, member, or biller). Required: teamId, userId, role. Use to manage permissions, promote/demote, or adjust access levels. Returns: Updated user profile with new role and permissions.

Inputs: teamId (required), userId (required), role (required).

lokalise_update_translationA

Modifies actual translated text or its review status. Required: projectId, translationId. Optional: translation (new text), is_reviewed, is_unverified. Use to fix typos, approve translations, or mark problematic content. Returns: Updated translation. Note: Changes visible immediately to all users.

Inputs: projectId (required), translationId (required), translationData (required).

lokalise_update_usergroupA

Updates a user group's properties including permissions and assignments. Required: teamId, groupId, name, isReviewer, isAdmin. Optional: adminRights, languages. Use to adjust group permissions, modify access levels, or reorganize team structure. Returns: Updated group configuration. Note: Cannot modify projects/members here - use dedicated tools.

Inputs: teamId (required), groupId (required), name (required), isReviewer (required), +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 59 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear verb_noun names. However, with 59 tools, some similar operations exist (e.g., bulk_delete vs single delete, list vs get for various entities), but descriptions clearly differentiate them.

    Naming Consistency5/5

    All tools follow a consistent 'lokalise_verb_noun' pattern, with verbs like list, create, update, delete, get, add, remove used predictably across the surface.

    Tool Count2/5

    59 tools is far beyond the typical 3-15 range for a coherent server. This many tools can overwhelm an agent and lead to selection errors, even if individually well-described.

    Completeness5/5

    The surface provides full CRUD and lifecycle management for projects, keys, translations, contributors, glossary, tasks, comments, languages, teams, and groups. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers