DeepL MCP Server

DeepL MCP server exists for a simple reason — assistants are far more useful when they can act on DeepL directly instead of describing what you should do. MCP Server for DeepL Translation API.

What you get

An MCP (Model Context Protocol) server providing high-quality translation capabilities via the DeepL API.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: DEEPL_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ (including Node.js 25) - DeepL API Key — Sign up here (Free tier available)

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the deepl mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by watchdealer-pavel; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against DeepL's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.