# Lokalise MCP > Lokalise takes over your translation workflow. Connect this MCP to manage entire localization pipelines—from creating new keys to downloading finished files—all through natural conversation with your AI agent. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** localization, translation-management, i18n, workflow-automation, key-management, software-localization ## Description Need to handle a massive, multi-language launch? This connector lets you take full control of your product's localization process without leaving your coding environment. You talk to your AI agent, and it handles the API calls to Lokalise. Want to see what projects exist or get details on a specific one? Just ask. Need to add fifty new strings across ten languages? It manages that complex data exchange for you. This means no more copying massive CSVs into separate web tabs. You can list all your translation keys and then tell the agent, 'Update this key with these new values.' The whole process is managed through natural conversation, making it feel like having a dedicated localization coordinator sitting right next to you. All of this powerful functionality is available through Vinkius, connecting Lokalise directly to your preferred AI client. ## Tools ### add_translation Adds specified translations to one or more existing keys within a project. ### create_key Creates entirely new translation keys inside your Lokalise project setup. ### create_project Establishes a brand-new, dedicated localization project in the system. ### download_file Generates and prepares a download bundle of translations for you to retrieve. ### get_project Retrieves detailed metadata about a specific, existing Lokalise project. ### list_keys Fetches a list of all translation keys available within a given project scope. ### list_languages Shows which languages are currently configured for your Lokalise project. ### list_orders Retrieves a list of professional translation orders associated with your account. ### list_projects Lists all the localization projects that currently exist under your Lokalise account. ### list_team_members Retrieves a roster of team members and their roles for administrative review. ### list_translations Shows all recorded translations for a single key within the project. ### update_key Modifies existing translation keys to change their content or metadata. ### upload_file Uploads external localization files, such as JSON or XLIFF, into the project for processing. ## Prompt Examples **Prompt:** ``` List all my Lokalise translation projects and show their current status. ``` **Response:** ``` I've retrieved your Lokalise projects. You have 3 active projects: 'Web App' (98% localized, 5 languages), 'Mobile App' (84% localized, 4 languages), and 'Marketing Site' (100% localized, 8 languages). ``` **Prompt:** ``` Create a new translation key 'checkout.success.message' in my Web App project for the web platform. ``` **Response:** ``` Successfully created the key `checkout.success.message` in your Web App project for the web platform. It's now ready for translators to fill in across all configured languages. ``` **Prompt:** ``` Download all Portuguese (pt-BR) translations from my Mobile App project in JSON format. ``` **Response:** ``` I've generated the download bundle for Portuguese (pt-BR) translations in JSON format. The file contains 342 translated strings with 98% completion. You can download it from the provided link. ``` ## Capabilities ### Manage Project Structure List all existing translation projects and create new ones with a single command. ### Control Translation Keys Create, update, or list specific text keys across your entire project setup. ### Handle Translations Data Fetch translations for a key, add new language versions, and review existing content flags. ### Process Files In and Out Upload localization files (like JSON or YAML) to the project or generate structured download bundles in any format. ### Audit Team and Orders List team members' roles or check the status of professional translation orders. ## Use Cases ### Need to update fifty keys across three languages immediately. The Product Manager asks the agent: 'Update the key 'login.button' with these new values.' The agent uses `add_translation` and `update_key`, ensuring all required language strings are changed correctly, which used to take hours of manual entry. ### Launching a new product line requires dozens of new phrases. The developer asks the agent to 'Create ten new keys for checkout flow.' The agent uses `create_key` repeatedly, populating all necessary strings in the project instantly so translators can start working. ### Need a full export of all content changes from last month. The localization team asks the agent to 'Download everything for Portuguese and German.' The agent uses `download_file`, giving them one clean, zip-ready bundle rather than multiple manual downloads. ### Checking if a new feature requires keys in every language. The PM asks the agent to 'List all translations for this key.' The agent uses `list_translations` and checks the status across all configured languages, giving an immediate compliance report. ## Benefits - Stop switching between tabs. You can list projects or get details using the `get_project` tool, all within the conversation flow. - Keep developers in their IDE. Use `create_key` to instantly add new strings that need translation without leaving your code editor. - Automate content gathering. Upload localization files with `upload_file`, allowing you to process large volumes of data programmatically. - Track team progress easily. You can use `list_team_members` or check professional orders via `list_orders` to see who's working on what. - Simplify bulk exports. Generating a download bundle with the `download_file` tool means you get clean, structured files ready for QA. ## How It Works The bottom line is that you guide the whole localization process using natural language, letting the MCP handle all the complex backend API interactions. 1. Subscribe to this MCP on Vinkius and provide your Lokalise API token. 2. Tell your AI agent what you need. For instance, 'List all active projects.' 3. Your agent executes the necessary calls and returns structured data—like a list of project names or available translation keys—directly into your conversation. ## Frequently Asked Questions **How do I list all my projects using Lokalise MCP?** You simply ask the agent to 'List all projects.' The agent uses `list_projects` and returns a comprehensive list of every project under your account, letting you see what's ready for work. **Can I bulk upload files with Lokalise MCP?** Yes. You use the `upload_file` tool to send localization files like JSON or XLIFF directly into your project queue, handling large data sets in one go. **What if I need to change a key's value?** You tell the agent exactly which key and what the new text should be. It then uses the `update_key` tool to modify that string across all relevant languages. **How do I get translated content for a specific feature?** Use the agent to list translations via `list_translations`. This shows you every language and its current status for a single, identified key. **Is Lokalise MCP useful for developers?** Absolutely. Developers love it because they can use the agent to run commands like `create_key` directly from their IDE chat window instead of needing to open a web browser tab.