The Google Translate MCP for workflows that speak every language
Connect one Google API key and translation plus language detection become workflow steps: localize content, route by language, and reply to customers in their own words.
What the Google Translate MCP connector does
The Google Translate connector for Mattering Automations wraps the Cloud Translation API in two focused nodes: Translate Text converts one or more strings into a target language (source auto-detected unless you pin it), and Detect Language identifies what language a string is written in.
Both nodes speak MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. Detection plus translation as separate steps means workflows can branch on language before deciding what to do.
Two nodes go a long way on a canvas: pipe inbound messages through detection, branch on the result, translate where needed, and hand the text to the next step, whether that is a reply draft, a task, or a database row.
One connection, three surfaces
- Visual automations. Drag Google Translate nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Google Translate node, ready to drop on the canvas
2 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 1
Google Detect Language
Detect the source language of one or more strings.
Action nodes 1
Google Translate Text
Translate one or more strings into a target language.
Connecting Google Translate takes one credential
Create an API key in the Google Cloud console under APIs and Services, then Credentials, with the Cloud Translation API enabled on a billing-enabled project.
In the Google Cloud console, enable the Cloud Translation API on your project.
Create or reuse an API key under APIs and Services, then Credentials.
In Mattering Automations, open Connectors, choose Google Cloud Translation, and create a credential with the key.
Both translation nodes appear in the canvas palette, ready to use.
Common uses for the Google Translate MCP
Multilingual inbox routing
Detect the language of inbound messages and route them to the right queue or teammate, translating a copy for whoever picks it up.
Content localization pipelines
Translate published copy into target languages as a workflow step, then open review tasks so a human approves before anything ships.
Replies in the customer's language
Draft a response with an AI node, translate it into the customer's detected language, and post it back through your comms connector.
Normalizing data for analysis
Translate free-text survey answers or reviews into one language before running sentiment or clustering steps, so analysis sees a consistent corpus.
Agent translation on demand
An MCP-connected assistant translates documents or messages mid-conversation using the same node the canvas uses, no copy-paste into a separate tool.
Example: Every inbound message answered in its own language
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a new customer message arrives through your comms connector.
Google Translate: Detect Language identifies the message language.
An AI step drafts the reply in English, and Google Translate: Translate Text converts it to the detected language.
The reply posts back to the conversation, with the original and translation logged to a Mattering database.
Google Translate MCP questions, answered
Can an AI agent translate text through this MCP?
Yes. Matter and any MCP-connected assistant, including Claude and ChatGPT, can run Translate Text and Detect Language, the same two nodes available on the automation canvas, including batch translation of multiple strings in one call.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Which languages does it support?
The Cloud Translation API supports well over a hundred languages; Google's documentation carries the current list. Source language is auto-detected unless you specify it, and the target is any supported language code.
What does it cost?
Google bills the Cloud Translation API per character translated, with a monthly free tier; Google's pricing page is the source of truth for current numbers, and the API requires a billing-enabled Google Cloud project.
What credential does the connector use?
A Google Cloud API key with the Cloud Translation API enabled, sent as a query parameter and stored encrypted in Google Secret Manager. One key can serve the other Google API-key connectors on the platform too.
Why not just translate with an AI model node?
Sometimes that is right, and the canvas lets you do either. The Translation API gives deterministic, per-character-priced output across a very wide language list, which suits high-volume or compliance-minded pipelines; LLM translation shines when tone and context matter more than consistency. Use each where it fits.
What is not supported?
The connector covers text translation and language detection on the v2 API. Document translation with formatting preserved, glossaries, and custom model features from the v3 advanced API are not exposed as nodes.
Put Google Translate to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Google Translate is a product of its respective owner; Mattering is an independent platform.