Model Context Protocol

Translate from your AI assistant.

The manilo MCP server lets an assistant such as Claude run a translation for you: it asks for the file, tells you the price, waits for your go-ahead and hands back the finished InDesign files.

What it looks like

You talk to your assistant as usual. Behind the scenes it uses the manilo tools:

  1. You: "Translate our catalogue into French and British English."
  2. The assistant creates an upload link. You send the IDML file through it.
  3. The assistant reports the price, for example 60.00 EUR net for 2,000 words.
  4. You confirm. Only now does the translation start.
  5. A few minutes later the assistant gives you a download link and tells you what the automatic checks found, for example a paragraph that became much longer. The job also appears in the manilo app.

Things to ask

Connecting

The server lives at:

https://app.manilo.ai/mcp

With a sign-in. In assistants that offer custom connectors, add this address as a connector. You are sent to a manilo page, where you log in, see what the assistant may do, set a monthly limit and confirm. No key is needed, and you can disconnect at any time under API access in the manilo app.

With an API key. Create a key in the manilo app under API access and give it a monthly limit. The server speaks the Streamable HTTP transport and accepts the key as a bearer token. In Claude Code, one command is enough:

claude mcp add --transport http manilo https://app.manilo.ai/mcp \
  --header "Authorization: Bearer $MANILO_API_KEY"

Clients that are configured with a JSON file usually take an entry like this:

{
  "mcpServers": {
    "manilo": {
      "type": "http",
      "url": "https://app.manilo.ai/mcp",
      "headers": { "Authorization": "Bearer mnl_live_..." }
    }
  }
}

Trying it without cost. On the manilo page that asks for your approval, switch on test mode. The assistant then runs the complete flow, but nothing is translated or charged, and the result is a copy of your file.

The sign-in follows the MCP authorization specification: OAuth 2.1 with PKCE, dynamic client registration and discovery through /.well-known/oauth-protected-resource.

Tools

ToolWhat it doesScope
list_languagesLists the supported language codesnone
create_upload_linkCreates a one-time link for one IDML filefiles:write
get_upload_statusReports whether the file has arrived and returns its IDfiles:write
create_quoteReturns a binding price. Starts nothing and costs nothingtranslations:write
start_translationStarts the translation as quoted. This is the only tool that spends moneytranslations:write
get_jobReports status and progress. Once finished: a signed download link and the quality notes of the job, so the assistant can tell you what to reviewjobs:read
list_jobsLists recent translations of the accountjobs:read
cancel_jobCancels a pending or running translationtranslations:write
get_balanceReports the account balance and what this connection may still spendbilling:read
list_glossaryLists terms with a fixed translationglossary:write
add_glossary_entryFixes the translation of a term for a language pairglossary:write
search_translation_memoryLooks up how segments were translated beforetm:read

An assistant only sees the tools its key is allowed to use. A key with jobs:read alone can follow translations but cannot start one.

Why this is safe to hand to an assistant

Getting the file in and the result out

A chat cannot pass a large InDesign file to a tool. That is why the assistant gives you an upload link instead: it opens a page where you drop the file. The link accepts exactly one file and expires after 30 minutes. Assistants that can run commands on your machine upload the file themselves.

The result comes back as a signed download link that is valid for 24 hours. Anyone with the link can download the files, so share it only with people who should have them.

Next

The tools map directly to the REST API. See the API reference for the details, or Authentication for keys and limits.