Your AI agent can now order
human translation.

Connect Claude, Codex, or any MCP client, to BLEND once.
From then on your agent quotes the job, places the order, tracks the linguist’s progress, and hands you the finished files — all without leaving the conversation.

Connect BLEND agent

See how it works

https://app.getblend.com/mcp — no API key to generate or rotate. Works with Claude Desktop, Claude on the web, and Claude Code.

Connect

Pick the path for the client you use.

Claude Desktop or Claude on the web:

Open Settings → Connectors.
Choose Add custom connector.
Name it BLEND, paste https://app.getblend.com/mcp as the endpoint, and click Add. Leave the OAuth fields (Client ID and Client Secret) empty — BLEND’s connector doesn’t need them.
Click Connect on the new BLEND row. Your browser opens BLEND — sign in with the account you already use.
Approve the connection. Claude comes back with BLEND’s tools available.

Claude Code, from the terminal:

claude mcp add --transport http blend https://app.getblend.com/mcp

Claude Code, from the terminal:

/mcp

/mcp opens a list of your connected servers. Select blend, choose Authenticate, and finish the login in the browser tab that opens. The connection is remembered — you won’t be asked again.

If you can already log into BLEND, you can connect. There’s no key to generate, no secret to paste, no config file to edit.

Verify

Ask your agent.

who am i on blend?

That’s the fastest proof the connection works. If it’s live, the agent replies with your BLEND account name and email — the same identity you use to log into the portal. If you get an error instead, the connection didn’t complete; go back and reconnect.

Order something real

Ask for a translation the way you'd ask a colleague.

You ask, in the conversation you’re already having.
The agent prices it and shows you the quote before spending anything.
You approve. It orders.
It checks progress on its own schedule and tells you when the work lands.
The translated files arrive in the same conversation, ready to use.

Nothing about that sequence is scripted. The agent chains BLEND’s tools itself, in the order this specific job actually needs, and figures out that order from the tools’ own descriptions — not from a playbook you wrote for it.

Nothing about the translation gets faster.
Everything around it disappears.

Human translation still takes hours to days. That part doesn’t change, and BLEND MCP was never built to pretend otherwise. What disappears is the busywork wrapped around it: copying content out of the tool you’re actually working in, opening a portal, picking a project type, uploading files, checking back, checking back again, downloading the result, and moving it back to where the work lives.

That hand-off was always the tax. You just paid it so often you stopped noticing.

Machine speed to order.
Human quality to deliver.

Every order still goes to a real, vetted BLEND linguist with the right language pair and subject expertise — exactly like an order placed by hand in the portal. The agent doesn’t translate anything. That’s still a person’s job, on purpose.

Only one tool can reach your wallet

Seven of the eight tools only read. create_translation_project is the only one that spends, and its own instructions tell the agent to quote first — so the cost is on screen before you say yes.

Nothing to leak

Connecting runs a standard OAuth sign-in — the same pattern as “log in with” anywhere else. There’s no long-lived API key sitting in a config file or shell history for someone to find.

A dropped connection can't double-charge you

Every order can carry an idempotency key. Send the same request twice and BLEND hands back the order you already have, not a second one.

Reversible

Disconnect the connector and the access is gone. Scoped to your account, scoped to BLEND, rejected anywhere else.

Real example

You want to create a process where a professional human linguist is checking every new website copy published on your website – and already translated by your LLM into French. You create an agent asking Claude Code to send the source and the translation of the content of a specific page to BLEND using the MCP. The agent gets back a quote and approves it according to your specifications. 15 mins later your agent checks the status of the project and when it’s ready, the edited strings are integrated back into your production website.

Questions worth asking

Do I need a BLEND account already?

No. If you’re an existing customer, your balance, rates, and project history carry over. The agent is another way in, not a separate account. If you’re new to BLEND, create an account and top up credits first. Everything the agent orders shows up in your portal as a normal project either way.

What can my agent actually order?

Seven project types: Translation, Proofreading, Translation + Proofreading, Machine Translation, MTPE Full, Human AI, and Professional Translation + Editing. The headline says “order human translation” because that’s the shift worth naming, but the same connection covers AI and hybrid project types too.

What stops my agent from spending money without asking?

Tool descriptions instruct the model to get a quote before ordering, so cost is on screen before anything is charged. If you want a hard rule instead of a default, just tell your agent to confirm with you every time before placing an order and it will.

Which clients does this work with?

Any client that speaks MCP over HTTP: Claude Desktop, Claude on the web, and Claude Code today, with more as they add support.

What if my agent gets something wrong — like an invalid language pair?

BLEND’s errors are written for the model, not just a log file. Each one names what was wrong and which tool call fixes it, so the agent corrects itself without needing you to step in. Nothing is charged for a failed or guessed call — only ordering spends credits.

Your agent is one connection away from ordering this itself.

Add BLEND as a connector, sign in with the account you already use, and ask your agent to quote something real.