Skip to main content
DeepL’s hosted MCP server lets AI assistants — Claude, ChatGPT, Microsoft Copilot, and any other MCP-compatible client — translate text and documents, rephrase and correct writing, and use your organization’s glossaries and style rules, directly from chat. The server is hosted by DeepL at a single endpoint. Sign in with your DeepL account over OAuth — there’s nothing to install and no setup to manage. It works with your existing seat-based DeepL plan.
Requires an active seat-based DeepL subscription. You sign in with your DeepL account; there’s no separate setup required.

​
Connect the connector

​
Prerequisites

  • An active seat-based DeepL subscription.
  • An AI client that supports remote MCP servers over Streamable HTTP (e.g. Claude, ChatGPT, Microsoft Copilot Studio).

​
Connect

1

Add the server by URL

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

Sign in with DeepL

The client discovers DeepL’s OAuth endpoints automatically (authorization server metadata and dynamic client registration). Approve the connection and sign in with your DeepL account.
3

Approve consent

Review and approve the consent screen. No further configuration is required.
4

Start translating

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

​
Translate a document

Document translation moves file bytes out of band so document content never passes through the model’s context window:
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

A client with filesystem access (e.g. a coding agent) uploads the file directly. In other clients, the assistant gives you a link to upload the file yourself.
3

Poll and download

The assistant checks progress with get-document-status, then returns the translated file via download-document once it’s ready.

​
Tool reference

The server exposes 16 tools. Translation, rephrasing, and correction generate new content; glossary and style-rule tools are read-only.

​
Data handling

  • Text payloads are not stored beyond the request.
  • Document-translation sessions are retained briefly (then deleted) to support the out-of-band upload and download flow; file bytes are streamed to DeepL for translation and are not stored by the connector.
  • All traffic is encrypted in transit (HTTPS/TLS). The connector talks only to DeepL’s own services.