DeepL MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPL_API_KEY | Yes | Your DeepL API key. You can get one by signing up at DeepL API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-source-languagesA | Get list of available source languages for translation |
| get-target-languagesA | Get list of available target languages for translation |
| translate-textA | Translate text to a target language using DeepL API. Review all available optional parameters and use those applicable to your scenario for best results. When the translation includes a glossary, you must specify the source language as well as the target language. If the user requests a glossary by name instead of by id, you can use the list-glossaries tool to get a name for each id. |
| get-writing-stylesA | Get list of writing styles the DeepL API can use while rephrasing text |
| get-writing-tonesA | Get list of writing tones the DeepL API can use while rephrasing text |
| rephrase-textB | Rephrase text in the same language, or into a different language, using DeepL API |
| translate-documentC | Translate a document file using DeepL API |
| list-glossariesA | Get a list of all glossaries with metadata for each - name, dictionaries available, and creation time. This does not fetch any glossary entries. Use the get-glossary-dictionary-entries tool to fetch entries. |
| get-glossary-infoA | Given an id, get metadata about the glossary with that id - its name, available dictionaries, and creation time. This does not fetch any glossary entries. Use the get-glossary-dictionary-entries tool to fetch entries. |
| get-glossary-dictionary-entriesA | Retrieve all the entries from a given glossary dictionary. (A glossary consists one of one or more dictionaries, each of which contains entries for a specific language pair, in one direction. For example, one dictionary could contain entries for translations from German to English, and another dictionary could contain entries for translations from English to German.) To retrieve all entries for a glossary with multiple dictionaries, use the get-glossary-info or list-glossaries tool to find out what dictionaries it contains, then use this tool for each dictionary. |
| list-style-rulesA | Get a list of all style rules with metadata for each - id, name, language, and timestamps. Style rules can be applied when translating text or documents. Use the get-style-rule tool to fetch the configured rules and custom instructions of a single style rule. |
| get-style-ruleA | Given an id, get a single style rule with its full detail - configured rules and custom instructions. |
| get-custom-instructionA | Get a single custom instruction belonging to a style rule. Use the get-style-rule tool to find out which custom instructions a style rule contains. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource or action: language listing, translation, rephrasing, glossary listing/detail/entries, and style rule listing/detail/custom instructions. The only pairs that could be confused (writing styles vs tones, style rule vs custom instruction) are distinguished by their descriptions, so ambiguity is minimal.
All tools follow a consistent verb_noun pattern using lowercase with hyphens (get-, list-, translate-, rephrase-). There are no mixed conventions or vague verbs like 'process'.
13 tools is within the ideal 3-15 range. The count reflects the breadth of DeepL features (translation, rephrasing, glossaries, style rules) without being overwhelming.
Core translation and rephrasing workflows are covered (language lists, translate text/document, rephrase, styles/tones). However, the server only offers read operations for glossaries and style rules (list/get), with no create/update/delete, leaving a notable gap for managing these resources.