The lookup tools are what make this more than a translate button: a translation can name a glossaryId or styleId, and the get- tools let you find the right one first, so terminology and tone stay consistent with what your team already set up. Translating with a glossary requires an explicit source language — auto-detection is off the table in that one case.
A stdio server that exposes DeepL as 13 MCP tools: text and document translation, rephrasing, and read-only lookups over the glossaries and style rules already in your DeepL account.
- translate-text with the full parameter set — formality, a glossaryId, a styleId, context, preserveFormatting, splitSentences and customInstructions — and text that takes a single string or an array translated entry by entry
- translate-document reads a PDF, DOCX, PPTX, XLSX, HTML or TXT off disk and writes the translated file back; without outputFile it derives the name by appending the language code, so report.pdf becomes report_de.pdf
- rephrase-text rewrites in the same language or into another one, with a style and tone drawn from what your account supports
- get-source-languages and get-target-languages return the codes DeepL accepts, and get-writing-styles and get-writing-tones return the exact values rephrase-text will take
- list-glossaries, get-glossary-info and get-glossary-dictionary-entries read your glossaries — a glossary being one or more dictionaries, each a single language pair in one direction
- list-style-rules, get-style-rule and get-custom-instruction read the style rules you have configured, so a translation can apply them by id
- Region handling is built in: omit the source code and DeepL detects it, and a bare target like en, pt or zh is filled out to en-US, pt-BR or zh-Hans
Node.js 18 or newer and a DeepL API key from your account, passed as DEEPL_API_KEY — the server exits immediately if it is not set. It runs over stdio, normally launched by the client as npx -y deepl-mcp-server. translate-document reads and writes files on the machine running the server. Glossaries and style rules are read-only through these tools; you create and edit them in your DeepL account.
One command plus a key — DEEPL_API_KEY=your-api-key npx -y deepl-mcp-server, then supply credentials
