# How to connect DeepL MCP to Claude

```json
{
  "title": "How to connect DeepL MCP to Claude",
  "toolkit": "DeepL MCP",
  "toolkit_slug": "deepl_mcp",
  "framework": "Claude Cowork",
  "framework_slug": "claude-cowork",
  "url": "https://composio.dev/toolkits/deepl_mcp/framework/claude-cowork",
  "markdown_url": "https://composio.dev/toolkits/deepl_mcp/framework/claude-cowork.md",
  "updated_at": "2026-10-22T05:31:42.182Z"
}
```

## Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.
This guide walks you through the easiest and most secure way to connect your DeepL account to Claude via Composio Connect, enabling it to translate product copy into French and Spanish, improve this customer email for clearer English, list languages supported for document translation, and more such actions on your behalf without compromising your account security.
Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

## Also integrate DeepL MCP with

- [ChatGPT](https://composio.dev/toolkits/deepl_mcp/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/deepl_mcp/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/deepl_mcp/framework/atomic-agent)

## Connect DeepL MCP to Claude Cowork

### Connecting DeepL to Claude Web, Desktop, and Cowork
Two ways to add the Composio connector. Pick whichever you prefer.
### 1. Add with one click
Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.
[Add to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp)
### Add manually
In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.
Click Add custom connector and paste in the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is the DeepL MCP server, and what's possible with it?

The DeepL MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your DeepL account. It provides structured and secure access to DeepL's translation and writing tools, so your agent can translate text, translate documents, correct writing, and rephrase content on your behalf.
- Text translation: Have your agent translate text into one or more target languages using DeepL.
- Document translation: Let the agent upload documents for translation while preserving their original layout and formatting, then check the translation status and download the finished document.
- Writing correction: Direct your agent to fix typos, grammar, and punctuation errors in one or more texts.
- Text rephrasing: Instruct your agent to rephrase content in the same language or a different language.
- Language discovery: Have your agent find the source and target language codes supported by DeepL before starting a translation.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `DEEPL_MCP_CORRECT_TEXT` | Correct-text | Correct one or more texts for typos, grammar and punctuation errors using DeepL. |
| `DEEPL_MCP_DOWNLOAD_DOCUMENT` | Download-document | Get a download link for a translated document once its status is 'done'. Returns 'downloadUrl', a short-lived, single-use link. Fetch it with an HTTP GET (the URL carries its own token, so do not add an Authorization header), or present it to the user. The link works only once. The bytes are streamed from the server and never pass through this conversation. For an upload with several target languages: omit 'targetLang' to get one link per finished language, or pass it to get that one language. |
| `DEEPL_MCP_GET_DOCUMENT_STATUS` | Get-document-status | Check the translation status of a document session. Returns one of: 'awaiting_upload' (file not received yet), 'queued', 'translating', 'done', or 'error'. The additive 'uploadStatus' is 'awaiting', 'uploading', or 'complete' when known. Any of the upload's session ids reports the whole upload: 'status' covers every target language ('translating' while any language still runs, 'error' only when they all failed) and 'targets' reports each language on its own. Once the status is 'done', call download-document. |
| `DEEPL_MCP_GET_SOURCE_LANGUAGES` | Get-source-languages | Get the source language codes supported by DeepL for translation, e.g. 'EN' or 'DE'. Use one of these for the sourceLang parameter of translate-text. |
| `DEEPL_MCP_GET_TARGET_LANGUAGES` | Get-target-languages | Get the target language codes supported by DeepL for translation, e.g. 'EN-US' or 'DE'. Use one of these for the targetLang parameter of translate-text. |
| `DEEPL_MCP_REPHRASE_TEXT` | Rephrase-text | Rephrase text in the same or a different language using DeepL. |
| `DEEPL_MCP_TRANSLATE_TEXT` | Translate-text | Translate text to one or more target languages using DeepL. Use this for plain text provided directly in the conversation — snippets, strings, messages, or passages pasted by the user. Do not use this to translate a file or document (e.g. Word, PowerPoint, Excel, PDF, HTML, .txt, .srt, .xlf/.xliff) — even if you can already read its contents — because it returns plain text and discards the document's layout and formatting. For files, use upload-document instead. Review the optional parameters and use those that apply for best results. When using a glossary, you must specify the source language as well as the target language. If the user references a glossary by name, use list-glossaries to look up its id. An unknown glossaryId is silently ignored (translation proceeds without it). An administrator may assign a language system (style profile) to the account, whose glossaries and style rule set can replace the glossaryId and styleId passed here; 'appliedCustomizations' in the result says so when it happened, per target language. Every target language is translated in one call; the result holds one entry per language, and a language DeepL refused is reported in 'failures' while the others still translate. Multiple texts are supported and translated independently; within each target language, results correlate to the inputs by position. If any text is blank, the whole request is rejected. |
| `DEEPL_MCP_UPLOAD_DOCUMENT` | Upload-document | Translate a whole file or document, preserving its original layout and formatting. Use this — not translate-text — whenever the user wants to translate a file or document (rather than text typed into the conversation), even if its contents are already visible to you; translate-text would strip the formatting. For plain text pasted into the conversation, use translate-text instead. Supported file extensions in this deployment: .docx, .doc, .pptx, .ppt, .xlsx, .xls, .pdf, .htm, .html, .txt, .xlf, .xliff, .srt, .png, .jpg, .jpeg. PNG and JPEG files are limited to 3 MB; limits for other formats depend on the user's plan. Always start a document translation with this call, and pass 'filename' with the file's extension. It reserves a short-lived upload session and returns 'sessionId' and 'uploadUrl'; it does not upload the file itself, and nothing is translated or billed until the file arrives. If the call had no 'filename', first call upload-document again with it. Then do exactly one of the following: 1. Upload the source file bytes: HTTP PUT the raw bytes to 'uploadUrl' with 'Content-Type: application/octet-stream'. 2. If you cannot access or transfer the file bytes, immediately call upload-document-show-fallback-widget with the returned 'sessionId'; it shows the user an upload widget where they select the file. Being unable to upload the bytes directly is an expected, recoverable condition: the next step is then to call upload-document-show-fallback-widget. Pass all target languages in one call rather than one call per language: the file is then uploaded only once. Each language is translated and billed separately once the file arrives. A language DeepL refuses is listed in 'failures' while the others still translate. An administrator may assign a language system (style profile) to the account, whose glossaries and style rule set can replace the glossaryId and styleId passed here; 'appliedCustomizations' on a target says so when it happened, per target language. |
| `DEEPL_MCP_UPLOAD_DOCUMENT_SHOW_FALLBACK_WIDGET` | Upload-document-show-fallback-widget | Second step of a document translation, for when the file bytes cannot be sent to 'uploadUrl': shows the user an upload widget for the upload session that upload-document already reserved, so they can select the file themselves. Call it with the 'sessionId' returned by upload-document right after that call, whenever you cannot access or transfer the file bytes. The widget tracks the translation and offers the download. |

## Supported Triggers

None listed.

## Troubleshooting

### 1. Why does Claude not use the Composio connector for DeepL?

The connector can show as connected, but Claude must use it in each DeepL conversation.
- Click + at the lower left of the chat, or type /.
- Hover Connectors.
- Turn on Composio.
- Ask Claude to connect to DeepL again.

### 2. Why does Claude show an MCP server error before DeepL connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for DeepL.
- Check that the connector URL is https://connect.composio.dev/mcp.
- Connectors run from Anthropic's cloud, so your device network is usually not the problem.
- Add the connector again from Customize > Connectors, then ask Claude to connect DeepL.
- If it fails again, send the error and the ofid_ reference id to support@composio.dev.

### 3. Why does the DeepL authorization link not work?

The Composio connector is one server. Your DeepL account connects separately when Claude asks for it.
- If the browser does not open, or the link expires, ask Claude to retry the DeepL connection.
- Composio creates a fresh DeepL authorization link.
- Open that link in your browser and finish the DeepL sign-in.

### 4. Why do DeepL actions fail after they worked before?

The DeepL connection can expire or lose permission.
- Ask Claude to inspect the DeepL connection.
- If the connection is unhealthy, disconnect it when Claude prompts you.
- Reconnect the DeepL account and retry the action.
- If Claude shows a permission prompt, approve it before Claude changes data in DeepL.
- If the action still fails with a permission error, check that the connected account has that permission in DeepL itself.

### 5. How do I switch to a different DeepL account?

Claude can manage the DeepL connection for you.
- Ask Claude to disconnect or delete the current DeepL account.
- Ask Claude to connect DeepL again.
- Open the new Composio authorization link for DeepL.
- Sign in with the other DeepL account in the browser.
- After the account connects, ask Claude to retry the DeepL task.

### 6. Why is my DeepL connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your DeepL connection works in Claude Web, Desktop, and Cowork.
- In Claude Desktop, open Customize > Connectors.
- Next to Composio, click ⋮ and click Clear cache.
- If DeepL tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
- On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect DeepL.

## Creating MCP Server - Stand-alone vs Composio SDK

The DeepL MCP server connects Claude Web, Desktop, and Cowork to your DeepL account through Composio. Once connected, Claude can use the available DeepL tools and triggers to complete tasks on your behalf.

## Complete Code

None listed.

## How to build DeepL MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/deepl_mcp/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/deepl_mcp/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/deepl_mcp/framework/atomic-agent)

## Related Toolkits

- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [ActiveMerge](https://composio.dev/toolkits/active_merge) - ActiveMerge is a document automation platform for generating documents, images, merged files, and e-signature workflows. It helps teams turn templates and stored files into finished, shareable documents faster.
- [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.
- [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease.
- [Airparser](https://composio.dev/toolkits/airparser) - Airparser is an AI-powered parser for extracting structured data from emails, documents, PDFs, and files. It turns messy inbound content into clean fields your apps and workflows can use.
- [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training.
- [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses.
- [Archive.org](https://composio.dev/toolkits/archive_org) - Archive.org is the Internet Archive's digital library of websites, books, audio, video, and images. Use it to preserve, explore, and access historical web captures and public-domain media.
- [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files.
- [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently.
- [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price.
- [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere.
- [Box MCP](https://composio.dev/toolkits/box_mcp) - Box MCP is Box's hosted MCP server that exposes enterprise files, folders, and metadata. It provides secure, centralized access to corporate content for search and management.
- [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code.
- [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more.
- [CertSeal](https://composio.dev/toolkits/cert_seal) - CertSeal is an API platform for issuing and managing verifiable digital certificates. Use it to automate trusted certificate workflows for recipients, batches, designs, and webhooks.
- [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place.
- [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and DeepL MCP?

With a standalone DeepL MCP server, the agents and LLMs can only access a fixed set of DeepL tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from DeepL and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right DeepL tools.

### Can I manage the permissions and scopes for DeepL while using Tool Router?

Yes, absolutely. You can configure which DeepL scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your DeepL data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
