DeepL and AI: Is there an MCP server for DeepL?

DeepL is a translation and writing service from Cologne. Anyone who wants an AI assistant such as Claude or ChatGPT to work with DeepL first asks: Is there an MCP server, and which plan is needed?

In short

Yes. DeepL runs an official, centrally hosted MCP server. According to DeepL, users sign in with their DeepL account and need no API key. The limits per request depend on the plan. We found no statement on where the MCP server processes data.

What DeepL offers itself

The hosted MCP server. DeepL describes it in the developer documentation. It runs over Streamable HTTP at https://mcp.deepl.com/v1/mcp. The OAuth metadata names dynamic client registration and client ID metadata documents. DeepL lists the server in the directories of Claude, ChatGPT and Microsoft Copilot. Other clients add the URL as their own connector.

Tools. According to the documentation there are up to 29 tools. They translate text, upload documents and images and fetch the result, rephrase, correct and list languages. Further tools cover glossaries, style rules and custom instructions. The documentation also lists deleting tools, for example delete-glossary and delete-style-rule-set. The service specification in the terms names read-only access to glossaries, style rules and instructions instead. We did not resolve this contradiction. According to DeepL, the tools depend on plan and permissions. Style profiles cannot be created or changed through the server.

Plans. According to DeepL, the server covers DeepL Free and seat-based plans. According to the documentation, Free cannot apply glossaries and style rules and cannot set formality or instructions per request. Seat-based plans can, and creating and editing depends on the team permissions. Rephrasing and correcting apply there if the plan includes DeepL Write.

Limits per request. According to the documentation:

• Characters per translation request: 5,000 in Free, 128,000 in seat-based plans.
• Characters per rephrase or correct request: 2,000 in Free, 128,000 in seat-based plans.
• Texts per request: 50. Target languages per request: 10. Each target language counts as its own translation for the quota.
• Custom instructions: up to 10 per request with 300 characters each, seat-based plans only.

According to the terms, usage through the server counts toward the plan’s quota. DeepL names no separate bill for the server.

Documents. According to DeepL, documents run outside the model context: the assistant starts the upload and the file goes straight to DeepL. If the assistant cannot reach mcp.deepl.com, it shows an upload widget in the chat. On Claude Team and Enterprise, an owner must allow network access to mcp.deepl.com under “Organization settings > Capabilities” for this. According to DeepL, PNG and JPEG files may be up to 3 MB.

Account or API key. There are two paths. On the account path, the plan of the signed-in person applies. For the API path, the terms name the endpoint mcp-api.deepl.com. It uses the same API key as api.deepl.com and is billed like the API, if the API plan includes MCP. The developer documentation for the server does not describe this second endpoint. A call without sign-in answered 401, so the endpoint is reachable. We checked nothing more.

A REST API. The DeepL API is an HTTP interface with an API key in the Authorization header. Pro accounts use https://api.deepl.com, Free accounts https://api-free.deepl.com. According to DeepL, the API key does not belong in client-side code.

Claude plugin. DeepL/claude-plugin is an official plugin for Claude Code (MIT). According to the README it needs a suitable DeepL subscription and opens the DeepL sign-in on first access. According to the README, the repository is generated from a private repository.

AI in the product. Through the server, the assistant reaches DeepL Write to rephrase and correct. The terms list DeepL Write Pro and DeepL Voice as separate services. According to DeepL, texts sent through the server are never used to train DeepL’s models. The API documentation notes that data handling can differ between Free and Pro. We did not clarify which rule applies to Free: DeepL’s help centre blocked our request.

The Docs MCP server. At https://developers.deepl.com/mcp, DeepL offers a second, read-only server. It only searches the developer documentation, needs no sign-in and translates nothing.

Vendor and contract. According to the terms, the contracting party is DeepL SE, Maarweg 165, 50825 Cologne. The imprint names the Amtsgericht Köln, HRB 104617. The privacy policy lists further group companies, among them DeepL AI GmbH, DeepL US Inc. and DeepL UK Ltd. According to the privacy policy, DeepL concludes a data processing agreement on request via privacy@deepl.com.

Data processing. According to DeepL, text requests through the server are not stored beyond the request. Document sessions are kept briefly and then deleted. Traffic is encrypted, and according to DeepL the server talks only to DeepL’s own services. On location: according to the privacy policy, DeepL translates documents with DeepL Pro and DeepL Translator on infrastructure in the EEA. It says nothing about the MCP server there. The terms let DeepL determine the processing location, which can depend on the customer’s location, among other things. For the API, DeepL names api.deepl.com as the EU default. Regional endpoints (USA, Japan) exist only with a signed addendum. For the MCP server, DeepL names no location. According to the terms, it is currently not available for subscriptions with the Data Residency add-on. This is why we set no data location for this page.

What the community and third parties offer

DeepL/deepl-mcp-server is DeepL’s own local open-source server (MIT, last pushed on November 5, 2026). It needs Node.js 18 and an API key, runs over stdio and has 13 tools, including translate-text, translate-document and rephrase-text. Glossaries, style rules and instructions are read-only there. The README points to the hosted server for new features. From the community there is, for example, watchdealer-pavel/deepl-mcp-server (MIT, 24 tools according to the README, needs the DeepL API). Zapier also lists a “DeepL MCP” as a Zapier service that runs through a Zapier account. According to the Zapier page, there are actions such as translate text, improve text, create, edit and delete a glossary, find a glossary and check usage. The page does not prove which plans or limits apply. It is not a community solution and not from DeepL.

What this means for your company

• Anyone who uses the server through the DeepL account needs no API key. The limits and functions depend on the plan, and in Free they are much tighter.
• If documents are to be translated, check the network access for mcp.deepl.com on Claude Team or Enterprise.
• If your DeepL contract includes a Data Residency add-on, the MCP server is currently not available according to the terms.
• Clarify the processing location with DeepL if it matters to you. The public sources do not name it for the MCP server.
• What reaches the AI assistant falls under its terms, not under those of DeepL.