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.
You talk to your assistant as usual. Behind the scenes it uses the manilo tools:
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.
| Tool | What it does | Scope |
|---|---|---|
list_languages | Lists the supported language codes | none |
create_upload_link | Creates a one-time link for one IDML file | files:write |
get_upload_status | Reports whether the file has arrived and returns its ID | files:write |
create_quote | Returns a binding price. Starts nothing and costs nothing | translations:write |
start_translation | Starts the translation as quoted. This is the only tool that spends money | translations:write |
get_job | Reports status and progress. Once finished: a signed download link and the quality notes of the job, so the assistant can tell you what to review | jobs:read |
list_jobs | Lists recent translations of the account | jobs:read |
cancel_job | Cancels a pending or running translation | translations:write |
get_balance | Reports the account balance and what this connection may still spend | billing:read |
list_glossary | Lists terms with a fixed translation | glossary:write |
add_glossary_entry | Fixes the translation of a term for a language pair | glossary:write |
search_translation_memory | Looks up how segments were translated before | tm: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.
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.
The tools map directly to the REST API. See the API reference for the details, or Authentication for keys and limits.