Localazy MCP. Run full localization workflows from your agent.

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.