MCP · Model Context Protocol
AI Document Translation MCP Server
Let your AI do the translating.
Plug Belin Doc's PDF and document translation into the MCP client you already use — Claude, Cursor, anything that speaks MCP. Ask in plain language to submit a job, check progress and pull the result. Same account, same quota as the web app.
userTranslate this PDF into Japanese.
↳translate_document · contract.pdf → ja
↳get_document_translation_status · 12 pages
aiDone — layout untouched, here is the translated file.
- Endpoint
- https://mcp.belindoc.com/api/mcp
- Transport
- Streamable HTTP · remote
- Keys per account
- 5
- Last updated
- 2026-08-28
What it can do
Four things to know about translating PDFs over MCP
One sentence, whole job
Say “translate this PDF into Japanese”. Picking the model, submitting and fetching the result all happen behind that one line.
Layout stays put
The translated file keeps the original layout, tables, figures and formula positions.
Your pick of model
Gemini 3, GPT-5.x and the rest of the roster — switch per job instead of being locked to one.
Same account, same quota
Calls draw on the quota and orders you already have on the web app. Nothing to top up separately.
Getting connected
Streamable HTTP · remote
Connect the MCP server in three steps
One key, one block of JSON. Everything after that happens in plain language.
- 01
Create an API key
Sign in, open the avatar menu in the top right and go to the Developer Center. The full key is shown once, right after it is created — save it then.
- 02
Paste the config
Add this block to your client's MCP config and put your key after Bearer in the Authorization header.
- 03
Just ask
Say what you want translated. The client picks the tool, Belin Doc does the work.
{
"mcpServers": {
"belindoc": {
"type": "http",
"url": "https://mcp.belindoc.com/api/mcp",
"headers": {
"Authorization": "Bearer <your API key>"
}
}
}
}The type value differs by client — Claude Code takes http. Streamable HTTP in the spec above is the protocol name, not a value to paste.
In practice
Say it, don't wire it
Six things you can ask for once the server is connected. Each maps to a tool the client calls for you.
- Translate
“Translate this PDF into Japanese.”
↳ translate_document
- Choose a model
“Use Gemini 3 for this contract.”
↳ translate_document
- Video
“Translate this video into English with bilingual subtitles.”
↳ translate_video
- Progress
“Is the one I just submitted finished?”
↳ get_document_translation_status
- Result
“Download the translated file for me.”
↳ get_document_translation_result
- Quota
“How many pages do I have left this month?”
↳ get_account_status
Questions
Before you connect the MCP server
- How is this billed? Is it the same quota as the web app?
- The same one. MCP is another way in, not another product: calls draw on the same page and video quota at the same model coefficients, and there is no MCP-only price.
- How many keys can one account have?
- Five by default. Create, rename, set an expiry and an IP allowlist in the Developer Center — and disable or delete a key whenever you want.
- What if I lose the key?
- The full value is shown only once, at creation — we keep only a hash, so it can't be recovered. If it's gone, reset the key in the Developer Center to get a new value: the name, expiry and IP allowlist stay as they were, and the old value stops working immediately.
- Which clients work?
- Any client that can talk to a remote MCP server over Streamable HTTP — Claude Desktop, Claude Code and Cursor among them.
- What if a key leaks?
- Disable or delete it in the Developer Center right away, then create a new one. You can also give a key an IP allowlist so only your own servers can call it.
Teach your AI to translate
Create a key, paste one block of config. That is the whole setup.