# Lokalise MCP for AI Agents AI Agent Connect > Lokalise lets you manage your entire localization pipeline through an AI agent. You can create projects, manage translation keys, upload files like JSON or XLIFF, and check the status of translation orders without leaving your workspace. It turns your AI into a dedicated localization coordinator for your global products. ## Overview - **Category:** productivity - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_P6sUb9oCxmRtiXdnLymCLXxowdjuKZ2uOdP9WsLW/ai-agent-connect - **Tags:** localization, translation-management, i18n, workflow-automation, key-management, software-localization ## Description Localization is often a mess of switching tabs between your code editor, your translation management system, and your team's communication channels. You spend half your day copy-pasting keys or manually checking if a string actually got translated into Japanese. This Connector changes that by putting the Lokalise platform directly into your AI client. Instead of hunting for a specific key in a dashboard, you just tell your agent to find it, update it, or check its status. You can handle bulk file uploads, manage team roles, and monitor translation progress through a simple conversation. It's a way to keep your localization flow moving without the manual overhead of constant context switching. Because Vinkius hosts this in its catalog, you can plug it into your existing workflow and let your agent handle the heavy lifting of keeping your app's language consistent across every platform. You no longer have to worry about missing strings or broken keys because your agent can verify the status of your projects and orders in real time. It turns your AI into a dedicated localization coordinator that handles the boring parts of internationalization. It removes the friction of moving data between different software environments and keeps your team focused on creating great content. ## Tools ### download_file Generate a download bundle of your translations. Use this to grab your final strings for any platform. ### get_project Fetch the metadata and details for a specific project. This gives you a quick overview of project status. ### list_keys List all translation keys currently in a project. Use this to see every string that needs translating. ### list_languages See all languages currently configured in a project. This helps you verify which regions are supported. ### list_orders View all active and past translation orders in your account. Use this to track professional work. ### list_team_members View all members and their roles in your Lokalise account. This helps you manage who can edit your content. ### list_translations Get the translations for a specific key. Use this to check how a single string looks in every language. ### upload_file Upload a localization file to a project. This lets you move entire JSON or XLIFF files into the system. ### add_translation Add translations to one or more keys. This helps you update multiple strings at once. ### create_key Create translation keys in a Lokalise project. This lets you register new strings without using the web dashboard. ### create_project Create a brand new localization project in your account. This is useful for starting new apps or websites. ### update_key Edit an existing translation key. This is how you change the name or metadata of a specific string. ### list_projects See a full list of all your Lokalise projects. This is the quickest way to see your entire portfolio. ## Prompt Examples **Prompt:** ``` What's the status of my Web App project translations? ``` **Response:** ``` I've checked your Web App project. Here is the current status: | Language | Completion | Status | | :--- | :--- | :--- | | English | 100% | Completed | | Spanish | 84% | In Progress | | French | 42% | Pending | There are currently 3 active translation orders for the French locale. ``` **Prompt:** ``` Create a new key called 'login.error_message' for the Mobile App project. ``` **Response:** ``` I've successfully created the `login.error_message` key in your Mobile App project. It's now ready for your translation team to fill in across all configured languages. ``` **Prompt:** ``` List all the team members who have access to our account. ``` **Response:** ``` Here are the team members currently in your Lokalise account: * **Alex Rivera** (Admin) * **Sarah Chen** (Translator) * **Jordan Smith** (Project Manager) * **Elena Gomez** (Translator) ``` ## Capabilities ### Create new translation projects Start new localization efforts by generating projects directly through your agent. ### Manage localization keys and filters Query and organize your translation strings using specific filters like platform or tags. ### Add new translations to existing keys Update your localized content for one or more keys in a single request. ### Upload and download localization files Move files like JSON, YAML, and XLIFF into your projects or grab download bundles. ### Monitor translation order progress Keep track of professional translation orders and their current status. ### Manage team roles and access View and manage the members who have access to your localization projects. ## Use Cases ### New feature launch A dev needs to add 20 new strings. They ask the agent to use create_key for each one in the Web App project. ### Status check A PM wants to know if the Spanish translation is done. The agent uses list_projects and list_translations to give a summary. ### Bulk update A localization lead needs to push a JSON file. They tell the agent to use upload_file to move it to the mobile project. ### Team management An admin needs to see who has access. They ask the agent to list_team_members to audit roles. ## Benefits - You can create translation keys instantly using create_key so you don't have to wait for manual entry. - You can bulk upload files with upload_file to get your content into the system faster. - You can check project status with list_projects to see exactly how much of your app is ready for launch. - You can update translations on the fly with add_translation to fix bugs in your UI without a full release cycle. - You can manage team access with list_team_members to keep your localization permissions organized. - You can export bundles with download_file to grab your final strings for any platform. ## How It Works The bottom line is you get a conversational interface for your entire localization backend. 1. Get your API token from your Lokalise account settings. 2. Add the Lokalise MCP to your preferred AI client via Vinkius. 3. Ask your agent to perform tasks like listing projects or updating keys. ## Frequently Asked Questions **Can the Lokalise MCP help my developers manage translation keys?** Yes, it lets your AI agent create and update keys directly in your projects so developers don't have to leave their workspace. **How do I use the Lokalise MCP to check translation progress?** You can just ask your agent to list your projects or specific translations to get a real-time status update on your global rollout. **Can I upload translation files using the Lokalise MCP?** Yes, your agent can handle uploading files in formats like JSON, YAML, and XLIFF directly to your specified projects. **Does the Lokalise MCP support team management?** It does. You can use your agent to see who's on your team and what roles they have within your account. **Can I download translation bundles with this?** Yes, you can tell your agent to generate a download bundle for any supported format to get your strings ready for production. **Is the Lokalise MCP good for large scale localization?** It's ideal for it because it automates the repetitive tasks of key management and bulk file syncing that usually slow down big projects. **What kind of Lokalise API token do I need for this integration?** You need a Personal Access Token from your Lokalise account. Go to your profile settings, find the API Tokens section, and generate a new token with read/write access to projects. Keep this token secure as it grants full API access to your account. **How do I add a new translation key to my Lokalise project via the AI agent?** Use the `create_key` action with the project ID, key name (e.g., `homepage.welcome.title`), and optionally specify platforms, tags, and a description. The key will be created with the base language placeholder ready for translation. **Can I export all my translations in a specific format like JSON or YAML?** Yes! Use the `download_file` action and specify the `format` parameter (e.g., `json`, `yml`, `xliff`, `strings`, `xml`). You can also filter by specific languages or filenames to generate targeted export bundles. **Is it possible to add translations programmatically for multiple languages at once?** Yes. The `add_translation` action supports adding translations for one or more keys at once. You can also mark translations as fuzzy or reviewed to indicate their quality status in the workflow.