Integration

Translate.com integration

Translate.com Translate API runs machine translation of text (the vendor advertises more than 90 language pairs). List the languages machine translation supports with their codes, translate a text from a source language to a target language and read how much of the plan's limit the call used, and check the account's word balance. Machine translation requires an active Translate.com API subscription. The human translation order routes (they draw on the word balance or a bound bank card) are not exposed. Authentication is the API key from the Translate.com customer account, sent in the x-api-key header.

Connect Translate.com How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Translate.com.Built from the 3 Translate.com tools below, on the connection you add once.

What you can do with Translate.com

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.

Balance, 1 operation

get_balanceGet balanceGETReturns the account's balance: all available words, words left on the subscription, the separate words balance, and whether a bank card is bound to the account.

Language, 1 operation

list_languagesList languagesGETLists the languages available for machine translation, each with its code (pass it as source_language or translation_language to translate_text), English name and native name.

Translation, 1 operation

translate_textTranslate textPOSTTranslates a text by machine from source_language to translation_language (codes from list_languages). Returns the translation and the plan limit used and remaining. Needs an active API subscription.

Use Translate.com from Claude Code, Cursor or Codex

Connect Translate.com in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Translate.com 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 Translate.com

Create your workspace
Sign up free. Nothing to install.
Connect Translate.com once
Add your Translate.com 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.