Localazy MCP for AI. Run full localization workflows from your agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Localazy (AI Translation & Localization API) manages your entire localization workflow through natural language commands. Use your agent to list projects, create new content keys, import translation files, and maintain glossary consistency without leaving your IDE.
What AI agents can do with Localazy (AI Translation & Localization API) Automation
Create glossary term
Adds a new, mandatory term to the project's glossary.
Create project
Initializes and creates a brand new localization project within your account.
Delete glossary term
Removes an existing term from the glossary, stopping its use in translations.
Run list_projects to get a list of all accessible projects, including language coverage statistics.
Use tools like create_glossary_term or update_glossary_term to enforce specific terminology across an entire product line.
Run import_content to upload supported file formats, making them ready for translation into your project's content pool.
Retrieve the raw content of a translated file using download_file in any specified language.
Manage source keys with tools like list_source_key, or set key priorities for translation teams via batch operations (set_key_priority).
Ask an AI about this
Waiting for input…
What AI agents can do with Localazy (AI Translation & Localization API) MCP Server: 23 Tools for L10n
This server provides comprehensive tools to control the entire localization lifecycle—from project setup and glossary definition to content import and file download.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Localazy (AI Translation & Localization API) on VinkiusCreate Glossary Term
Adds a new, mandatory term to the project's glossary.
Create Project
Initializes and creates a brand new localization project within your account.
Delete Glossary Term
Removes an existing term from the glossary, stopping its use in translations.
Delete Screenshot
Deletes a previously uploaded visual context screenshot.
Delete Source Key
Removes a specific key from the project's source pool of content.
Download File
Retrieves the actual raw file content for a specified language and version.
Get Webhook Secret
Fetches the secret used by webhooks, required for secure HMAC verification checks.
Import Content
Uploads supported file formats, making them available in the project for translation...
List Cdn Metadata
Lists metadata URLs associated with published content release tags (CDN).
List File Content
Returns all keys and their current translations for a specific language in a given...
List Files
Provides an inventory listing of all content files currently attached to the project.
List Glossary Terms
Fetches and lists every term that is currently defined in the project's glossary.
List Import Formats
Shows a list of supported file types and their required parameters for importing content.
List Projects
Retrieves all projects accessible by the token, optionally including language...
List Screenshots
Lists all uploaded visual context screenshots for a specific project.
List Webhooks
Shows the list of webhooks configured and linked to the current project.
Set Key Priority
Performs a batch operation that assigns priority levels to multiple source keys at...
Set Key Tags
Applies descriptive tags to up to 1,000 source keys in a single batch action.
Update Glossary Term
Modifies the definition or usage rules of an existing glossary term.
Update Screenshot
Updates metadata (like link phrases or tags) for a screenshot already uploaded to...
Update Source Key
Changes specific properties associated with an existing source key.
Update Webhooks
Modifies or reconfigures the webhook settings for a project.
Upload Screenshot
Uploads a new screenshot image, encoded in Base64 format, to provide visual context.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Localazy integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Localazy (AI Translation & Localization API), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Localazy. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 23 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually coordinating content keys and project statuses is a huge time sink., Solved with Vinkius AI Gateway
Right now, checking localization progress means opening the web dashboard, navigating to Project A, then looking at Language Stats. You repeat that for Project B, C, and D. If you need to compare all of them—say, verifying if they all hit 90% completion—you spend half a day clicking through tabs and copy-pasting data into a spreadsheet.
With this MCP server, you just ask your agent: 'List all my projects and give me their language coverage.' The agent runs `list_projects` and spits out the entire dataset in one clean response. It cuts out the dashboard entirely.
Localazy (AI Translation & Localization API) MCP Server
Manually managing translations requires a loop of actions: 1) Check status (`list_projects`). 2) Find the term needing correction. 3) Go to glossary and update it manually (`update_glossary_term`). 4) Re-check the file content (`list_file_content`) to verify the fix.
Now, you tell your agent: 'Update the term 'Widget' in Project X because of a brand change.' The agent calls `update_glossary_term` and handles all necessary cross-references. It’s one prompt; it’s done.
What your AI can actually do with this
You're running a massive localization pipeline? Connect your Localazy API MCP Server to your agent and manage every detail of your translation workflow without leaving your IDE. You don't need to switch screens or jump through web forms; you just talk to your AI client, and it handles the heavy lifting.
Project Oversight & Setup
You can get a full picture of what you’re working on by calling list_projects, which hands you an inventory of every project associated with your token, even language coverage stats. Need to start from scratch? Use create_project to initialize and build a brand new localization project in the account.
For security and configuration, you'll need to manage webhooks. You can list all existing webhooks linked to the current project using list_webhooks, or modify them entirely with update_webhooks. If you require the secret for secure HMAC verification checks, get_webhook_secret retrieves it for you.
Content Import and Asset Management
Getting content into the system is straightforward. You upload supported file formats using import_content, which makes them ready to go in the project's translation pool. Want to see what files are already attached? Run list_files for a full inventory.
Once you have the source material, your agent can pull specific data points. Use list_file_content to get all keys and their current translations for any language in a file. If you need the raw content of an asset, download_file retrieves it for any specified language or version.
To keep track of published material, list_cdn_metadata returns metadata URLs associated with specific content release tags (CDN). You can also manage visual context by uploading new screenshots—encoded in Base64 format via upload_screenshot—to provide your translators with necessary visuals. Check out existing images using list_screenshots, or update the metadata, like link phrases or tags, for an already uploaded image with update_screenshot.
If a screenshot is wrong, you can delete it with delete_screenshot.
Terminology and Key Control
Consistency is everything. To enforce specific terminology across your entire product line, you manage the glossary. You'll use list_glossary_terms to see every term currently defined in the project’s glossary. To mandate a new word or phrase, call create_glossary_term. If that term changes its meaning or usage rules, update_glossary_term lets you modify it; if it's outdated, delete_glossary_term removes it entirely.
When managing source keys (the actual content placeholders), your agent handles the heavy lifting. You can perform batch operations to apply descriptive tags to up to 1,000 keys using set_key_tags. Alternatively, if you need to assign specific importance levels to multiple source keys at once, use set_key_priority.
You can also adjust individual key properties with update_source_key, remove a key from the project's source pool via delete_source_key, or list all available source keys using list_source_key.
Workflow Summary
In short, you use this server to manage everything: You can run list_projects and check out status reports. You upload files with import_content. You control terminology by creating and updating glossary entries. You download translated assets using download_file, and you keep track of key changes or bulk-update priorities with the source key tools.
019e5d2f-1dd5-7296-9a1a-09610f777041 
Here's how it actually works
The bottom line is that you talk to your AI client, not the API. Your agent handles all the necessary calls—like fetching project IDs or listing files—and gives you a clean answer.
Subscribe to the server and provide your Localazy Personal Access Token.
Prompt your agent with a localization task, like 'List all my projects and check language completion.'
The agent uses list_projects (or another tool) to fetch data, which it then presents directly in plain English.
Who is this actually for?
This server is built for developers and product managers who hate context switching. If your job involves coordinating content across multiple languages, you need this. It stops you from having to jump between the IDE, the project dashboard, and a terminal just to check if 'login button' was translated correctly.
Uses your agent to automate syncing translation keys and files directly inside their IDE or terminal.
Checks project status via list_projects, updates mandatory glossary terms, and reviews visual context by managing screenshots.
Queries project statistics using the agent to ensure multi-language support remains on track for upcoming releases.
What Changes When You Connect
Project status checks are instant. Instead of navigating to the dashboard, run list_projects through your agent and immediately see if 'Mobile App' is 95% complete in five languages.
Maintain absolute consistency across all translated text. Use create_glossary_term or update_glossary_term so that agents enforce specific terminology before translators even start.
Never lose source files again. The agent can run list_file_content to pull keys and translations for a file, giving you the exact data set you need without manual exports.
Visual context is always available. You upload screenshots using upload_screenshot and then track them via list_screenshots, ensuring translators have exactly what they need in one place.
Automate asset pipelines by managing metadata. Use list_cdn_metadata to verify which content versions are published, linking your translation effort directly to the release tag.
See it in action
A new feature needs 10 languages added.
The PM knows 'Web Dashboard' is missing German (de). They ask their agent: 'What projects are ready for language addition?' The agent runs list_projects and identifies the gap. Next, they use create_project to spin up the new locale, ensuring the whole process stays in chat.
The glossary needs updating.
A marketing team changes how 'Client' is referred to. Instead of manually finding every instance, they run: 'Update the term 'Client' to use 'Customer.''. The agent calls update_glossary_term and immediately fixes consistency everywhere.
Syncing files in a CI/CD pipeline.
A developer needs to verify that all strings are present before deployment. They ask the agent: 'Show me keys for strings.json (ID: f789) in French.' The agent runs list_file_content, giving them a clean, structured JSON output they can paste right into their terminal.
Checking translation progress before a deadline.
The Product Owner needs an overview. They ask: 'What are the completion stats for all projects?' The agent runs list_projects, providing a clear, summarized view of language coverage percentages and IDs in one go.
The honest tradeoffs
Listing everything manually
The developer logs into the Localazy web dashboard. They click 'Projects,' then filter by status, then open each project to check files and glossaries—a process taking 30 minutes.
Instead of clicking through menus, just ask your agent: 'List all my projects and give me a summary of their current language completion percentages.' The agent uses list_projects and delivers the entire overview in one response.
Editing terms across multiple interfaces
A writer changes a term on a spreadsheet, then has to log into Localazy's web UI, find the glossary, and manually update it. This often leads to stale data.
Run update_glossary_term directly through your agent conversation. You tell the AI client exactly what needs changing—the term, its new definition, and the project ID—and it handles the API call.
Checking file contents in small batches
A tester wants to verify one key's translation. They download a file, copy a piece of text, paste it into another tool, and then try to find the corresponding key ID.
Tell your agent: 'What are all the keys and translations for strings.json (ID: f789) in French?' The agent runs list_file_content, giving you a complete mapping immediately.
When It Fits, When It Doesn't
Use this server if your workflow involves coordinating multiple, distinct localization tasks—like checking project status and updating glossary terms and importing files. It's an orchestration tool. Don't use it if you only need to view a single, static resource (e.g., just reading the contents of one file). For simple viewing or retrieval without modification, consider using dedicated API wrappers or direct client integrations instead. The power here is in chaining: running list_projects to get IDs, and then feeding those IDs into update_webhooks for a massive batch operation. If your task is single-threaded (e.g., 'just upload this file'), the tool itself works. But if it's multi-step ('check status -> update terms -> download result'), stick with this MCP Server.
Questions you might have
How do I check which projects are available using list_projects? +
You simply ask your agent to run list_projects. The tool returns a structured list of all accessible projects, giving you their IDs and current language metrics right away.
Can I use create_glossary_term to enforce a specific phrase? +
Yes. You pass the desired term and its description to create_glossary_term. This immediately adds it to the project's glossary, forcing translators to follow that exact wording.
What is the best way to download a translated file? Do I use list_file_content? +
No. Use list_file_content if you want to see what keys and translations exist. To actually get the raw, usable content of a specific language, run download_file.
How do I manage visual context for my translators? +
You use screenshot tools. First, upload images with upload_screenshot, then list them using list_screenshots. You can also update the metadata on existing visuals with update_screenshot.
How do I secure my webhooks and verify incoming data using `get_webhook_secret`? +
You retrieve the secret key via get_webhook_secret. Your system uses this token to perform HMAC verification on all incoming webhook payloads. This ensures that only authorized sources can send updates to your project.
Before I run `import_content`, how do I verify compatible file types using `list_import_formats`? +
list_import_formats shows all supported file formats and their specific parameters. This lets you confirm the correct structure before importing, preventing data loss or import failure.
What should I do if `list_files` returns an empty list for a project? +
An empty result from list_files means no files are currently attached to the project. You'll need to use import_content first, or check if another user cleared out the file directory.
How do I manage and audit my external connections using `list_webhooks`? +
list_webhooks provides a list of all configured webhooks for your project. You can review their URLs and ensure they point to the correct endpoints before updating them.
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.
We've already built the connector for Localazy. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 23 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.