Integrations
Bring your content to Localizethat.
Connect the tools where your content already lives, localize it with your company Context, and keep the workflow moving.
Available today: Google Drive import and MCP.
Localize without leaving your Drive workflow.
Bring source content from Google Drive into Localizethat, localize and review it, then save approved language versions back to a Drive folder you choose — no downloading, uploading or duplicate file juggling.
- Browse your Drive from inside Localizethat
- Pull Google Docs straight into a localization
- Save approved language versions back to a Drive folder you choose
- Your source file is never overwritten
Connect Localizethat to more of your workflow.
Localizethat supports Model Context Protocol (MCP), giving compatible tools and AI workflows a standard way to work with Localizethat.
MCP can help you
- Connect compatible AI tools to your workspace
- Bring localization into workflows your team already runs
- Work with Localizethat without relying only on predefined native integrations
What a connected tool can do today
Five actions are available. Every call is authenticated as the connecting user, so a tool only sees what that person is allowed to see.
list_localizationsReadList localization assets with content type, languages and status.
get_localizationReadFetch one localization, its source text and the localized segments per language.
get_brand_contextReadRead brand voices, glossary terms, approved claims and forbidden claims.
add_glossary_termWriteAdd a term to the glossary with a translation, or flag it as do-not-translate.
get_usage_summaryReadCheck credit balance and recent AI usage.
MCP compatibility is not the same as a native integration. It gives compatible tools a standard way to reach Localizethat — it does not connect Localizethat to a CMS, DAM or marketing platform on its own.
Your localization tool shouldn’t become another content silo.
Bring content into Localizethat, work with Context and reviewers, then keep the result moving through your existing content process.
- Content source
- Localizethat
- Localization
- Review
- Next step
More ways to connect are coming.
We’re expanding the native integrations available in Localizethat based on the workflows our customers use most.
Request an integrationStart with the tools you already use.
Connect your content, add your Context and move localization into one workflow.