Can I use Google Translate as a CLI?

Yes. KosmoKrator exposes a Google Translate CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Google Translate through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Google Translate tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Google Translate credentials stored?

Google Translate credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Google Translate MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Google Translate MCP, CLI, and Lua Integration for AI Agents

Google Translate integration docs for AI agents: MCP gateway setup, Google Translate CLI commands, Lua API reference, credentials, and function schemas.

7 functions 5 read 2 write API key auth

Submit Google Translate feedback View package source

Google Translate for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Machine-Readable Metadata

integration_slug: google-translate
route_slug: google-translate
package: google-translate
auth_strategy: api_key API key
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true
supports_multi_account: true

Quick Links

Lua APIAgent-facing namespace and function reference. Google Translate CLIHeadless setup and direct function calls. Google Translate MCPMCP gateway setup for external clients. Submit feedbackReport missing tools, auth problems, wrong docs, or runtime issues. ContributeAdd tools or improve metadata in the integrations repo.

Google Translate MCP Client Matrix

Use these pages when a specific agent client or framework needs copy-pasteable MCP setup for Google Translate.

Google Translate CLI Matrix

Use these pages for direct Google Translate CLI workflows in scripts, CI, cron, and agent wrappers.

CI Google Translate CLI for CI. Cron Jobs Google Translate CLI for cron jobs. Shell Scripts Google Translate CLI for shell scripts. Headless Automation Google Translate CLI for headless automation. Coding Agents Google Translate CLI for coding agents.

Function Catalog

Function	Type	Parameters	Description
`google-translate.google_translate_translate_text`	Write `write`	4	Translate text using Google Cloud Translation. Supports automatic source language detection or explicit source language specification. Returns translated text with detected source language.
`google-translate.google_translate_detect_language`	Read `read`	1	Detect the language of text using Google Cloud Translation. Returns detected language codes and confidence scores.
`google-translate.google_translate_list_supported_languages`	Read `read`	1	List languages supported by Google Cloud Translation. Returns language codes and names. Optionally specify a target language to localize language names.
`google-translate.google_translate_list_glossaries`	Read `read`	0	List all glossaries in your Google Cloud Translation project. Returns glossary names, language pairs, and entry counts.
`google-translate.google_translate_get_glossary`	Read `read`	1	Get details of a specific Google Cloud Translation glossary by name. Returns glossary name, language pair, entry count, and timestamps.
`google-translate.google_translate_create_glossary`	Write `write`	4	Create a new Google Cloud Translation glossary. Glossaries define custom translations for specific terms. Provide term pairs as an array of source/target strings.
`google-translate.google_translate_get_current_user`	Read `read`	0	Verify the Google Cloud Translation API key and get connection information. Confirms the API key is valid and the service is reachable.