What can you do with the Google Cloud Translation integration?

LiveContext exposes 16 operations on Google Cloud Translation, covering glossary, language, translation and batch. Common uses include website localization, Model discovery and Pronunciation guides.

Which OAuth scopes does Google Cloud Translation require?

The operations that declare a scope all need https://www.googleapis.com/auth/cloud-translation.

LiveContext

All integrations

Google Cloud Translation integration

Google Cloud Translation API enables dynamic translation of text and documents between thousands of language pairs. Supports both Basic (v2) and Advanced (v3) editions with features including auto-detection of source language, Neural Machine Translation (NMT), Translation LLM models, glossaries for domain-specific terminology, batch translation for large volumes, and document translation preserving original formatting. Perfect for multilingual applications, content localization, real-time translation services, and enterprise translation workflows.

16 toolsOAuthAPI docs

Connect Google Cloud Translation How integrations work

Common Google Cloud Translation use cases

website localization
Model discovery
Pronunciation guides
brand name consistency
simple text translation
validating glossary exists
Domain-specific translation
translating entire websites
removing outdated glossaries
glossary management interface

What you can do with Google Cloud Translation

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Glossary, 4 operations

POSTcreate_glossary
Creates a glossary in Google Cloud Translation for consistent terminology. Define term mappings that ensure specific translations across all requests using this glossary.
DELETEdelete_glossary
Deletes a glossary from Google Cloud Translation. Removes the glossary and all its term entries permanently.
GETget_glossary
Retrieves metadata for a specific Google Cloud Translation glossary. Returns details including language configuration, entry count, and creation timestamp.
GETlist_glossaries
Lists all glossaries in a Google Cloud Translation project location. Returns metadata including names, language pairs, entry counts, and timestamps.

Language, 4 operations

POSTdetect_language_v2
Detects the language of text using Google Cloud Translation Basic API (v2). Simple language identification with API key authentication.
POSTdetect_language_v3
Detects the language of text using Google Cloud Translation Advanced API (v3). Returns language code with confidence score for the input content.
GETget_supported_languages_v2
Retrieves supported languages for Google Cloud Translation Basic API (v2). Returns language codes with optional localized names.
GETget_supported_languages_v3
Retrieves supported languages for Google Cloud Translation Advanced API (v3). Returns language codes with localized names and source/target support indicators.

Translation, 3 operations

POSTadaptive_translate
Translates text using adaptive machine translation with custom training examples.
POSTtranslate_text_v2
Translates text using Google Cloud Translation Basic API (v2). Simple API key authentication with support for 100+ languages and Neural Machine Translation.
POSTtranslate_text_v3
Translates text using Google Cloud Translation Advanced API (v3) with Neural Machine Translation or Translation LLM models. Supports glossaries for consistent terminology and custom AutoML models.

Batch, 1 operation

POSTbatch_translate_text
Batch translates large text volumes asynchronously using Google Cloud Translation. Reads from Cloud Storage, supports multiple target languages, and outputs to GCS.

Document, 1 operation

POSTtranslate_document
Translates documents synchronously using Google Cloud Translation while preserving formatting. Supports PDF, Word, PowerPoint, Excel, and HTML files.

Html, 1 operation

POSTtranslate_html
Translates HTML content while preserving markup structure and tags.

Model, 1 operation

GETget_model_info
Lists available translation models including NMT, Translation LLM, and custom-trained AutoML models.

Text, 1 operation

POSTromanize_text
Converts text from non-Latin scripts to Roman/Latin characters (transliteration).

OAuth scopes Google Cloud Translation requires

Each operation declares the scopes Google Cloud Translation requires for it.

https://www.googleapis.com/auth/cloud-translationneeded by adaptive_translate, batch_translate_text, create_glossary and 13 more

Use Google Cloud Translation from Claude Code, Cursor or Codex

Connect Google Cloud Translation in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Cloud Translation operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Cloud Translation

Create your workspace
Sign up free. Nothing to install.
Connect Google Cloud Translation once
Add your Google Cloud Translation connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Cloud Translation integration FAQ

What can you do with the Google Cloud Translation integration?: LiveContext exposes 16 operations on Google Cloud Translation, covering glossary, language, translation and batch. Common uses include website localization, Model discovery and Pronunciation guides.
Which OAuth scopes does Google Cloud Translation require?: The operations that declare a scope all need https://www.googleapis.com/auth/cloud-translation.