# Localazy MCP for AI Agents AI Agent Connect

> Localazy MCP lets you manage software localization and translations directly through your AI agent. You can list projects, import content, manage source keys, and handle glossary terms without switching tabs. It handles the heavy lifting of maintaining consistency across multiple languages for your apps.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_BvDLBhhjTQFk1tXGm7inq31wAeYUya187ifYuL79/ai-agent-connect
- **Tags:** i18n, l10n, translation-api, software-localization, continuous-localization

## Description

Managing software translations usually feels like a chore of jumping between spreadsheets, translation platforms, and your code editor. You spend half your time making sure a specific term stays consistent across five different languages or hunting down a missing translation key. This Connector changes that by bringing your entire localization pipeline into your AI client. Instead of clicking through a dashboard to update a glossary term or check a project's status, you just tell your agent what needs to happen. It handles the communication with the backend to pull in new files, push out updates, and keep your translation team in sync. Because Vinkius hosts this Connector, you can connect it to your existing workflow and stop treating localization as a side task. It turns translation management into a conversation where you can quickly audit content, manage visual context with screenshots, and ensure your global rollout stays on schedule. You can handle batch updates to your keys, manage webhooks for automation, and retrieve CDN metadata for your published releases without ever leaving your workspace. It removes the friction of manual data entry and lets you focus on the actual product.

## Tools

### create_project
Create a new localization project within your organization. This helps you organize different apps or products.

### delete_glossary_term
Remove a specific term from your project glossary. Use this to clean up outdated terminology.

### download_file
Get the raw content of a file for a specific language. This is useful for auditing translations.

### get_webhook_secret
Retrieve the secret used for HMAC verification on your webhooks. Use this to secure your automation.

### import_content
Bring in supported file formats along with their translations. This automates the sync of your local files.

### list_cdn_metadata
See the metadata URLs for your published release tags. Use this to track live content on the CDN.

### list_file_content
See the keys and translations for a specific file and language. This helps you check specific strings quickly.

### list_files
View all files currently in a project. Use this to get an overview of your project structure.

### list_glossary_terms
See every term in your project's glossary. Use this to audit your brand terminology.

### list_import_formats
Check which file types and parameters are supported. This helps you prepare your source files.

### list_projects
See all projects accessible with your current token. Use this to get a high-level view of your work.

### list_screenshots
View all screenshots associated with a project. Use this to see what visual context is available.

### list_webhooks
See all configured webhooks for a project. Use this to manage your automation triggers.

### set_key_priority
Set the priority for multiple keys at once. This helps manage how your app handles fallback strings.

### set_key_tags
Apply tags to up to 1,000 keys in a batch. Use this to organize your keys by feature or module.

### update_glossary_term
Modify an existing term in your glossary. Use this to keep your brand voice consistent.

### update_screenshot
Change the metadata or tags for a specific screenshot. This helps organize your visual context.

### update_source_key
Modify the properties of a source key. Use this to adjust how keys behave in your project.

### update_webhooks
Change the configuration for your project webhooks. Use this to adjust your automation settings.

### upload_screenshot
Add a new screenshot using a Base64 encoded image. This gives your translators visual context.

### delete_screenshot
Remove a visual screenshot from your project. Use this to clear out old visual context.

### delete_source_key
Delete a specific key from your current project. This helps when removing features from your UI.

### create_glossary_term
Add a new term to your project's glossary. Use this to establish new brand rules.

## Prompt Examples

**Prompt:** 
```
Check the status of my mobile app project and tell me which languages are finished.
```

**Response:** 
```
### Project Status: Mobile App

| Language | Completion | Status |
| :--- | :--- | :--- |
| English | 100% | ✅ Done |
| French | 95% | 🟡 In Progress |
| Spanish | 80% | 🟡 In Progress |
| German | 40% | 🔴 Pending |

**Summary:** You are nearly finished with the French localization, but the German translation still needs significant work.
```

**Prompt:** 
```
Add a new glossary term for 'Cloud Sync' and explain it as the background process for data backup.
```

**Response:** 
```
✅ **Glossary Term Created**

- **Term:** Cloud Sync
- **Description:** The background process for data backup.

I've added this to your project glossary. This will help ensure that all translators use the same phrasing for this feature.
```

**Prompt:** 
```
Show me the French translations for the login screen file.
```

**Response:** 
```
### French Translations: login_screen.json

| Key | Translation |
| :--- | :--- |
| `login_button` | Se connecter |
| `welcome_msg` | Bienvenue |
| `forgot_password` | Mot de passe oublié |
| `submit_click` | Valider |

I found 4 keys in the French file for the login screen.
```

## Capabilities

### Create new localization projects
Generate a new project within your organization with specific source languages and tones.

### Import translation files
Bring in supported file formats including existing translations directly into your project.

### Update glossary terms
Modify existing terms to ensure consistent terminology across all your localized content.

### Retrieve content for languages
Get the keys and translations for a specific language and file instantly.

### Manage project webhooks
Configure and manage webhooks to automate your localization workflow.

### List CDN metadata
See the metadata URLs for your published release tags from the CDN.

### Upload visual context
Add screenshots to your project to provide translators with visual context.

## Use Cases

### Syncing hundreds of new keys
A developer needs to sync 500 new translation keys from a JSON file and wants to use import_content to avoid manual uploads.

### Enforcing brand terminology
A localization manager needs to ensure 'Dashboard' is always translated the same way and uses create_glossary_term to set the rule.

### Auditing global readiness
A product owner wants to know how many languages are finished and asks the agent to run list_projects to see the stats.

### Verifying specific UI strings
A QA tester needs to see the French version of a specific button and uses list_file_content to verify the text.

## Benefits

- Keep your brand voice consistent by updating glossary terms with update_glossary_term without manual entry.
- Speed up file syncing by using import_content to bring in translations from various formats instantly.
- Get visual context for your translators by quickly adding images with upload_screenshot.
- Manage large-scale updates efficiently using set_key_tags to organize thousands of keys at once.
- Audit your progress easily by querying project statistics and language coverage with list_projects.

## How It Works

The bottom line is you get a direct line of command to your localization pipeline without leaving your workspace.

1. Subscribe to the Localazy MCP on Vinkius.
2. Provide your Localazy Personal Access Token.
3. Use your AI client to manage projects and translations.

## Frequently Asked Questions

**Can I use Localazy MCP to manage my app's translations?**
Yes, it connects your AI agent to Localazy so you can manage projects, keys, and glossaries using natural language.

**How does Localazy MCP help with translation consistency?**
You can use it to create and update glossary terms, ensuring your AI agent and human translators use the same phrasing.

**Can I import translation files using Localazy MCP?**
Yes, you can use it to bring in various file formats directly into your projects without manual uploads.

**Does Localazy MCP support screenshots for translators?**
It lets you upload and manage screenshots so your translators have the visual context they need for better accuracy.

**Can I see my project progress with Localazy MCP?**
You can ask your agent to list projects and include statistics to see exactly how much of your app is translated.

**Is Localazy MCP good for large scale localization?**
It's great for high-volume work because it supports batch operations like tagging thousands of keys at once.

**How can I check which file formats are supported for import?**
You can use the `list_import_formats` tool. It will return a comprehensive list of all supported file types and their specific parameters for the Localazy API.

**Can I update the context or character limit for a specific translation key?**
Yes! Use the `update_source_key` tool. You can modify properties like the character limit, context comments, and even mark keys as hidden or deprecated.

**How do I retrieve the translations for a specific file in a target language?**
Use the `list_file_content` tool by providing the Project ID, File ID, and the target language code. It will return the keys and their corresponding translations.