Translating from Your AI Agent (MCP)

Available from the Solo plan.

LATW Cloud has an MCP server, so the AI agent you already work with — Claude, ChatGPT, Claude Code,
Cursor, VS Code, Windsurf, Codex, n8n or your own — can translate your sites without you opening the
panel. Ask it “how much is left to translate into French?” or “translate all missing products into
German and French”, and the agent checks your site and translates the content itself, with no
Credits used (see Translation by the agent itself).

If you would rather have LATW Cloud translate in the background, ask the agent to use LATW’s engine
— with Credits, or with your own API key if the site is set to Your key. The agent also offers
it when your plan’s words for agent translation are not enough. It shows you the price first and
starts the job only after you confirm. These are ordinary LATW Cloud jobs: they use the site’s
settings (model, AI source, glossary, prompt) and cost what the same job costs from the panel.

Either way the jobs show in Jobs with the origin MCP and are written to your live site as
they are translated.

#Connecting your agent

There is no key or token to copy. You add LATW Cloud to your agent as a remote MCP server, the
agent opens a LATW page, you sign in with your LATW account and press Allow.

• Address: https://app.latw.ai/api/mcp (Streamable HTTP)
• Sign-in: OAuth — the agent finds it by itself, nothing else to enter

The address is on the MCP screen of the panel. Below it, Connect your agent has a tab for
Claude Code, Claude, Codex CLI and ChatGPT — each with what to copy and where to put
it — and Setup prompt, a ready-made text you paste into a coding agent such as Cursor: it adds
the server and starts the sign-in by itself.

Claude (Claude.ai, Claude Desktop, mobile) — open Customize → Connectors, press + Add and
Add custom connector. Name it LATW Cloud, enter the address, press Continue and keep the
sign-in Claude detects. In a Team or Enterprise organization, an owner adds the connector under
Organization settings → Connectors and each member presses Connect next to it. In a chat,
turn LATW Cloud on with + → Connectors.

ChatGPT — custom MCP servers need Developer mode, which you turn on in ChatGPT’s settings
under Apps (the plans and labels that offer it are set by OpenAI and change; check ChatGPT’s help
if you do not find it). Then create an app with the address and OAuth as the authentication.

Claude Code — add the server, then run /mcp in Claude Code, pick latw and sign in:

claude mcp add --transport http latw https://app.latw.ai/api/mcp

Cursor — in ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor
asks you to sign in when it first connects:

{
  "mcpServers": {
    "latw": {"url": "https://app.latw.ai/api/mcp"}
  }
}

Windsurf — in ~/.codeium/windsurf/mcp_config.json, then press Refresh in Windsurf’s MCP
settings and sign in:

{
  "mcpServers": {
    "latw": {"serverUrl": "https://app.latw.ai/api/mcp"}
  }
}

VS Code — in .vscode/mcp.json; VS Code asks you to allow the sign-in when it starts the
server:

{
  "servers": {
    "latw": {"type": "http", "url": "https://app.latw.ai/api/mcp"}
  }
}

Codex CLI — add the server and sign in:

codex mcp add latw --url https://app.latw.ai/api/mcp
codex mcp login latw

n8n — add the MCP Client Tool node to your AI Agent, set the endpoint to
https://app.latw.ai/api/mcp with the HTTP Streamable transport and choose OAuth2 as the
authentication. n8n registers itself with LATW (dynamic client registration is on by default in
its MCP credential); connect the credential and allow it.

Agents that only run local servers — bridge with mcp-remote, which opens the sign-in in your
browser:

{
  "mcpServers": {
    "latw": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.latw.ai/api/mcp"]
    }
  }
}

Your own agent — use an MCP client library with OAuth support (the official MCP SDKs have it).
The server publishes where to sign in, and an app registers itself without asking us for keys.

Check the connection: ask the agent to call get_account. It answers with your plan and your
available Credits.

#Allowing an app

When an agent connects, it opens a LATW page: sign in if you are not signed in, check the name of
the app and press Allow. Cancel sends you back to the app without connecting it. If the page
says MCP is available from the Solo plan, upgrade first and reload the page. Check that you are
signed in to the right LATW account — Switch account is on the same page.

What a connected app may do: see your sites, content, jobs and prices; start, cancel, resume and
retry jobs; translate content itself. It uses all sites of your account. It cannot change settings
(model, AI source, glossary, prompt, budget limits, API keys), top up Credits, change your plan or
connect sites.

Connected apps on the MCP screen lists the apps you allowed, with the date. Disconnect
takes the app’s access away within a minute; jobs it started keep running. To use it again, connect
it again from the app. Jobs started by a connected app show the app’s name in their history, for
example Job created via MCP, app “Claude”.

#What the agent can do

Tool	What it does
get_account	Plan, available Credits, sites used, words left for agent translation, links to the panel
list_sites	Your sites with their languages and translation settings
get_site_coverage	Translated, outdated and missing items per language
list_content_groups, list_content	What the site has and the translation status of each item — the same lists as the Content tab
list_models	Models and their price in your plan
estimate_translation	Counts the words and prices a job, without spending anything
start_translation	Starts the job that was priced
list_jobs, get_job	Progress, cost and failed items with the reason
cancel_job, resume_job	As Cancel and Resume on the job’s page
estimate_retry, retry_failed	As Retry failed on the job’s page: first what the retry would cost, then the retry after you confirm
start_agent_translation, get_source_texts, submit_translations	Translation by the agent itself — see below

The agent can pick items one by one or ask for everything with a status in a group — for example,
all products missing in German. One job takes at most 500 items this way; for more, the agent splits
the work into several jobs. Webflow keeps no translation statuses (see Connecting Webflow), so on a
Webflow site the agent picks the items one by one.

#Price first, then the job

This applies when the agent translates with LATW’s engine. An agent cannot spend Credits in one step. It first asks for an estimate: your site counts the
words, and the agent gets the cost, your balance after the job and any warning (not enough Credits,
a budget limit the job would pass). It must show you that and start the job only after you confirm.

The price holds for 30 minutes. If the content grew in the meantime and the job would cost more,
the job does not start and the agent asks for a new price. As with jobs from the panel, Credits are
reserved when the job starts and what it does not use goes back when it ends; budget limits apply
the same way.

Jobs are translated by LATW Cloud and written to your live site as they finish — exactly as when
you start them in the panel.

#Translation by the agent itself

When you ask the agent to translate, by default it translates with its own model — the
subscription you already pay for — instead of LATW’s engine. LATW Cloud gives it the texts with the site’s prompt, website description and
glossary terms, checks every translation it hands back and writes the valid ones to your site.

• No Credits are used. Instead, the words count towards a monthly limit of your plan, shown on
  the MCP screen and in the plan comparison. When the words left are not enough for a job, the
  agent tells you and offers LATW’s engine, with the price first.
• It uses your agent’s own model and time. A large job, such as a whole catalog, takes the agent
  many steps and uses up your agent subscription’s limits. For large jobs, LATW’s engine may be the
  better choice: it translates in the background while you do something else.
• What LATW checks: the same keys as the source, HTML tags and their order, shortcodes,
  placeholders, links, empty texts and length limits. A translation that breaks them is not written;
  the agent gets the reason and corrects it. LATW guarantees that the write is technically correct —
  the quality of the translation is your agent’s.
• Content that changes while the agent works is read again before its translation is written.
• Every platform, WordPress, Drupal, PrestaShop and Webflow. On Webflow the agent works on a few
  items at a time (Webflow limits how many requests a site token may make a minute), translates whole
  items, and what is published follows the site’s Publishing setting (see Connecting Webflow) —
  as with jobs from the panel.
• In Jobs these jobs show the engine Agent (MCP) and no cost. Retry failed is not
  offered — the agent translates the failed items in a new job.
• A job the agent stops working on is closed after 24 hours without activity; what it did not hand
  in is released on your site.

The texts are sent to the agent only while it translates and are not stored by LATW Cloud.

#What the agent cannot do

The agent cannot change settings (model, AI source, glossary, prompt, budget limits, API keys), top
up Credits, change your plan or connect sites. When something needs your hand, it gives you the
link to the right place in the panel.

#When something goes wrong

Every error the agent gets has a code and the next step. The common ones:

Code	What happened	What to do
unauthenticated	The agent is not signed in, its sign-in expired, or you disconnected the app	Sign in again from the agent (see Connecting your agent)
plan_required	The account has no plan that includes MCP	Choose a plan. Your connected apps are kept and work again
insufficient_credits	The job needs more than your available Credits	Credits → Top up by the missing amount, then estimate again
not_found, job_not_found	The site or job does not exist in your account	Ask the agent to list your sites or jobs
site_unreachable	Your site did not answer	See Site Unreachable
nothing_to_translate	Everything chosen is up to date	Ask for “translate again” only if you really want it
selection_too_large	More than 500 items in one job	Narrow it by type or date, or split it
quote_expired, price_changed	The price is older than 30 minutes, or the job (or the retry) would now cost more	The agent asks for a new price
key_required	The site uses Your key without a key chosen	Pick a key in Sites → your site → Settings
word_limit_reached	Your plan’s words for agent translation are used up this month	Use LATW’s engine, or a bigger plan

If your plan ends, the connected apps stay on the MCP screen, paused, until you renew or
disconnect them.