MCP server
DeepL
Translate through DeepL inside an assistant while keeping DeepL plan rules and the assistant's own data handling visible.
Published by the company that makes the product.
What it can access
Remote mode uses DeepL sign-in. Local server mode uses a DeepL API key. Both send selected text or documents to DeepL; the surrounding AI client also sees the request and result.
Security note
The connector is available with DeepL accounts, but data handling still depends on the DeepL plan and the AI client. Never use the free translation service for personal or confidential data.
Do you need it?
Connect only if translation is repeated inside the assistant. For occasional public text, the DeepL website is easier to understand and revoke.
Capability and permissions
DeepL’s remote MCP can translate text and documents, rephrase text, and use glossaries after DeepL sign-in. The local MCP server uses a DeepL API key. Both send selected content to DeepL, and the assistant also sees the request and result.
Least-privilege setup
As of 2026-09-01, use the official remote address from DeepL’s AI-agent page for account sign-in, or install the official deepl-mcp-server only when an administrator can protect the API key. Begin with a personal glossary containing no confidential terms.
Harmless success test
Translate a public 50-word announcement into Arabic or Sorani. Ask for no file write. Have a fluent reviewer mark all errors.
Disable, revoke, remove
Disconnect the MCP in the assistant, revoke the DeepL AI connection in DeepL account settings, and delete any local API key from the client configuration. Rotate the key if it was ever copied elsewhere.
When not to connect
Do not connect for one translation, or send personal or confidential data through DeepL Free. Do not publish high-stakes translation without bilingual review.