Skip to main content
DeepL’s hosted MCP server lets AI assistants such as Claude, ChatGPT, Microsoft Copilot, and any other MCP-compatible client translate text, documents, and images, rephrase and correct writing, and use, create, and edit your organization’s glossaries and style rules, directly from chat. The server is hosted by DeepL at a single endpoint. You sign in with your DeepL account over OAuth, so there’s nothing to install and no API key to manage.

​
Connect

​
Use a listed connector

Claude, ChatGPT, and Microsoft Copilot list DeepL in their app directories. This is the fastest way to connect. On team and enterprise plans of these tools, an admin may need to enable DeepL first.

​
Connect any other MCP client

Use these steps for any client that supports remote MCP servers over Streamable HTTP with OAuth, for example Cursor, VS Code, or Copilot Studio.
1

Add the server by URL

In your AI client, add a new MCP server or custom connector and enter the server URL:
2

Sign in with DeepL

The client discovers DeepL’s OAuth endpoints automatically from the authorization server metadata. DeepL supports dynamic client registration and client ID metadata documents, so you don’t need a client ID or secret. Sign in with your DeepL account.
3

Approve consent

Review and approve the consent screen. If DeepL doesn’t recognize your client, the consent screen shows an extra confirmation step before you can approve.
4

Start translating

Ask the assistant to translate or rephrase, for example: “Translate this email into German and French with a formal tone.”

​
What you can do on each plan

The server only shows the tools your plan and permissions allow. For example, glossary and style rule tools are hidden on DeepL Free.

​
Request limits

When you translate into several target languages in one request, each language counts as a separate translation for usage.

​
Translate a document

Document translation moves file bytes out of band so document content never passes through the model’s context window. One upload can be translated into up to 10 target languages.
1

Start an upload

Ask the assistant to translate a file. It calls upload-document, which returns an upload session and a short-lived link.
2

Provide the file

If the assistant can reach mcp.deepl.com (for example, a coding agent or Claude with network access), it uploads the file directly. Otherwise, it calls upload-document-show-fallback-widget, which shows an upload widget in the chat where you select the file yourself.
3

Poll and download

The assistant checks progress with get-document-status, then returns the translated file with download-document once it’s ready. If you uploaded through the widget, the widget shows the progress and offers the download instead: one file for a single language, or a ZIP archive for several. The file name includes the target language, for example report DE.docx.
Supported formats: .docx, .doc, .pptx, .ppt, .xlsx, .xls, .pdf, .htm, .html, .txt, .xlf, .xliff, .srt, .png, .jpg, and .jpeg. PNG and JPEG files can be up to 3 MB. Size limits for other formats depend on your plan.

​
Glossaries, style rules, and style profiles

On seat-based plans, the assistant can apply your glossaries and style rules when it translates, and create or edit them when you ask, for example: “Add ‘customer account’ as ‘Kundenkonto’ to our English-German support glossary.”
  • Plan limits on the number of glossaries and entries per glossary apply
  • Creating and changing glossaries and style rules requires the matching permissions in your DeepL team
  • Many clients ask you to confirm before the assistant changes or deletes a glossary or style rule
If your admin has assigned a style profile to you, DeepL applies its glossaries and style rules automatically, and they replace the ones the assistant requested. The tool response tells the assistant which customizations were applied. Style profiles can’t be created or changed through the MCP server. See Managing glossaries and Using style rules for how these customizations work.

​
Tool reference

The server exposes up to 29 tools. Read tools only return data. Write tools create content or change your customizations. Destructive tools overwrite or delete existing data.

​
Translation and writing

​
Documents

​
Glossaries

​
Style rules and custom instructions

​
FAQ

Claude uploads files from its code execution sandbox, which needs network access to mcp.deepl.com. On Claude Team and Enterprise plans, an owner allows it in Organization settings > Capabilities: turn on Allow network egress, choose package managers and specific domains, and add mcp.deepl.com.Without this, the assistant shows an upload widget in the chat instead. Select the file there, and download the translation from the widget when it’s ready.
Allow mcp.deepl.com. The MCP server, OAuth sign-in, and document upload and download all run on this domain. During sign-in, your browser also opens the regular DeepL login page.
Team admins can turn off AI connector access for their whole organization. Check with your admin. See Manage AI assistant access to DeepL for your team.

​
Data handling

  • Text payloads are not stored beyond the request
  • Document translation sessions are kept briefly to support the out-of-band upload and download flow, then deleted. File bytes are streamed to DeepL for translation and are not stored by the MCP server
  • All traffic is encrypted in transit (HTTPS/TLS). The server talks only to DeepL’s own services
  • The server supports OAuth token revocation. When a client revokes its token, access ends immediately