DeepL MCP. Translate text and audit multilingual content on the fly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
DeepL MCP Server handles professional, multi-language translation and text auditing. Your agent can instantly translate text across dozens of languages, adjusting the tone from formal business to casual.
It also lets you query configured glossaries and monitor API usage, keeping your global communication precise and budget-controlled.
What your AI agents can do
Get account glossaries
Lists all the translation glossaries you have set up.
Get api usage
Retrieves your current API usage and the remaining character limit.
Get glossary dictionary
Gets the specific term mapping entries for a given glossary ID.
Your agent translates text, enforcing a formal, informal, or standard business tone.
Your agent translates text while preserving the original HTML element structure.
Your agent lists all supported source and target languages for translation.
Your agent lists and queries configured glossaries to ensure consistent brand terminology is used.
Your agent gets your current API usage and character limit constraints.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
DeepL MCP Server: 9 Tools for Multilingual Content
These tools let your agent translate text in different tones, preserve HTML structure, check language support, and manage glossaries.
019d842dget account glossaries
Lists all the translation glossaries you have set up.
019d842dget api usage
Retrieves your current API usage and the remaining character limit.
019d842dget glossary dictionary
Gets the specific term mapping entries for a given glossary ID.
019d842dget source languages
Lists every language that can be used as the source for translation.
019d842dget target languages
Lists every language that DeepL can translate into.
019d842dtranslate html markup
Translates text while safely preserving the original HTML tag structure.
019d842dtranslate text formal
Translates text using a formal or professional business tone.
019d842dtranslate text informal
Translates text using a casual, conversational tone.
019d842dtranslate text standard
Translates text using a standard, neutral tone.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with DeepL, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
DeepL gives your AI client the chops to handle professional, multi-language translation and content auditing. Your agent can translate text across dozens of languages, dialing the tone from formal business to casual. It also lets you check configured glossaries and monitor API usage, keeping your global comms tight and your budget on track.
Tone Control and Translation
Your agent translates text using specific tones: translate_text_formal handles professional business language, translate_text_informal uses a casual, conversational voice, and translate_text_standard keeps things neutral.
Web Structure Translation
When you use translate_html_markup, your agent translates text while keeping the original HTML tag structure safe. translate_text_standard translates text, and the agent can also get the source language metadata using get_source_languages.
Language Scope
Your agent lists every language that can be used as the source for translation with get_source_languages, and it lists every language DeepL can translate into with get_target_languages.
Glossary Management
For consistent brand terminology, your agent first lists all the translation glossaries you've set up using get_account_glossaries, then it gets the specific term mapping entries for a given glossary ID with get_glossary_dictionary.
How DeepL MCP Works
- 1 Subscribe to the DeepL server and enter your DeepL API Key (Free or Pro).
- 2 Connect your AI client (Claude, Cursor, or any MCP-compatible client) to the server.
- 3 Start managing translation and auditing by asking your agent questions or providing text directly.
The bottom line is, you connect your AI agent to this server and start talking to it about translation, just like you'd talk to a person.
Who Is DeepL MCP For?
Localization Managers, Content Writers, and Operations Leads need this. If your job involves translating content for international markets, you run into consistency problems. Your agent solves that by keeping brand terminology consistent (using glossaries) and making sure the tone is right for the platform—whether it's a formal business document or a casual social media post.
Uses get_account_glossaries to monitor translation consistency and retrieves glossary metadata directly within their workflow.
Verifies translated segments and uses get_source_languages to audit language support before global campaigns launch.
Automates translation data querying to coordinate cross-functional global teams and track usage with get_api_usage.
What Changes When You Connect
- Translates text using specific tones. You don't have to guess if your content should sound formal or casual; your agent handles the tone using
translate_text_formal,translate_text_informal, ortranslate_text_standard. - Handles complex web content. If you're translating a webpage,
translate_html_markupkeeps the HTML tags intact. The output is structured, not just a block of text. - Stops terminology drift. You can query your brand's rules using
get_glossary_dictionaryand ensure the translation uses the exact term you defined, every time. - Tracks costs instantly.
get_api_usagegives you a clear count of characters used against your monthly limit, so you never hit an unexpected paywall. - Covers all bases. You can check supported languages using
get_source_languagesandget_target_languagesbefore you write a single word, knowing exactly what options are open. - Automates the process. Instead of writing complex code for every tone or format, you just tell your agent to translate it, and it uses the right tool internally.
Real-World Use Cases
Translating a formal corporate policy document
A corporate communications specialist needs to translate a policy from English to German, but it must sound official. They ask their agent to translate the text using the translate_text_formal tool. The agent sends the output, guaranteeing the appropriate, professional tone, which is critical for internal legal documents.
Localizing a dynamic website component
A web developer needs to translate a component that contains HTML tags (like <strong> or <a>). They run the text through translate_html_markup. The agent returns the translated text with all the original tags perfectly preserved, so the component works right when deployed.
Auditing consistent brand names in a global campaign
A marketing team is running a global campaign and needs to verify that 'Product X' is translated the same way in Spanish and French. They use get_account_glossaries to list the available glossaries and then query get_glossary_dictionary to check the official mapping for the brand name.
Comparing translation options for a new market
A content lead is planning expansion into Brazil. They first use get_target_languages to confirm that Portuguese (PT-BR) is supported. Then, they use the standard translation tool to get a baseline translation, ensuring they don't start a project based on limited language support.
The Tradeoffs
Treating all translation as plain text
Pasting a chunk of code or a web snippet into a generic translator and hoping the formatting stays the same. You end up with broken tags and unusable output.
→
Always use translate_html_markup. This tool handles the translation while safely keeping your HTML tags and structure intact. It’s the right way to handle web content.
Ignoring tone requirements
Translating a CEO announcement using a standard tool when it needs to be highly formal. The result sounds awkward, unprofessional, and misses the intended impact.
→
If the communication is professional or business-critical, use translate_text_formal. If it’s for a casual platform, use translate_text_informal instead. Tone matters.
Overlooking the API limit
Running a massive batch job without checking your usage. The job fails mid-process, and you have no idea why until you hit an error code.
→
Check your budget first. Use get_api_usage to see your remaining character count. This keeps your workflow running smoothly and prevents unexpected service halts.
When It Fits, When It Doesn't
Use this if your primary need is reliable, multi-faceted language translation that respects context, tone, and format. You need to move beyond simple word-for-word translation.
Use it when:
* You are localizing web content and need HTML tags preserved (translate_html_markup).
* Your brand requires strict terminology control (use get_glossary_dictionary).
* The tone of the message is critical (use translate_text_formal or translate_text_informal).
Don't use it if:
* You just need a quick, one-off translation of a single sentence and don't care about consistency or tone. (A basic, single-purpose API call might be enough).
* Your core problem is data extraction (e.g., pulling structured data from a PDF). This server is for language, not data.
It's the best choice for full content pipelines where quality control is non-negotiable.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DeepL. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
The hardest part of global content is consistency.
Today, if you're managing global content, you're constantly jumping between spreadsheets, style guides, and various translation platforms. You copy a term from the source, paste it into the translator, then manually check it against your style guide. If you forget to check the tone, the translated text can sound wildly off, making your brand look unprofessional.
With this MCP server, you let your agent handle the whole flow. You just give it the text and the context. It handles the tone, the language, and the structure. You get perfectly localized, consistent content without leaving your chat window.
DeepL MCP Server: Translate with Tone and Structure
Manual localization requires you to run the same text through separate tools for tone (formal vs. informal) and then separately run it through a markup tool for web content. This is a slow, error-prone process that requires multiple API calls and tracking.
Now, your agent manages this complexity. It uses the appropriate tools—like `translate_text_formal` or `translate_html_markup`—to deliver the exact output you need in one go. You just ask for it.
Common Questions About DeepL MCP
How do I make sure my brand uses the right terms with DeepL MCP Server? +
You must query the glossaries. Use get_account_glossaries to list your available glossaries, then use get_glossary_dictionary to check the exact term mapping for consistency.
Can I translate a full webpage using DeepL MCP Server? +
Yes, use translate_html_markup. This tool preserves the HTML tags while translating the text, so your webpage structure won't break after translation.
What are the best tones to use with DeepL MCP Server? +
The best tone depends on the platform. Use translate_text_formal for legal or business communications, and translate_text_informal for social media posts.
How do I check my translation budget using DeepL MCP Server? +
Use get_api_usage. This tool gives you a real-time count of your characters used and your remaining limit, preventing unexpected billing issues.
How do I list all the languages DeepL MCP Server supports for translation? +
You use the get_source_languages and get_target_languages tools. These functions list every language DeepL can translate from or to, helping you maintain a clear view of options.
What should I do if I encounter an API usage error with DeepL MCP Server? +
Check the current usage using get_api_usage. This tool reports your character count and remaining API limits, so you know exactly when you need to pause or upgrade.
How can I preserve HTML tags when using the DeepL MCP Server? +
You call the translate_html_markup tool. This handles translating content while safely keeping the original HTML structure and tags intact. It's perfect for web content.
Does DeepL MCP Server support translating specific document formats? +
The server handles text strings, not file formats. Use the core translation tools—like translate_text_formal or translate_text_standard—to process text excerpts you copy and paste into your agent.
How do I find my DeepL API Key? +
Log in to your DeepL account, and you will find your Authentication Key under the 'Account' tab. Copy and paste it below.
Does this work with both Free and Pro API keys? +
Yes. This server automatically detects if you are using a Free key (ending in :fx) or a Pro key and routes requests to the correct endpoint.
Can the agent use glossaries? +
Yes. You can list your existing glossaries via the get_glossaries tool and identify their IDs to maintain consistency in your agent-led translations.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Ellie Planner
Plan projects visually with AI-assisted task breakdowns, timelines, and team coordination that adapts as your work evolves.
SproutVideo
Automate video hosting and management via SproutVideo — manage videos, playlists, and analytics directly from any AI agent.
QR Code Generator
Generate and decode QR codes for URLs, text, and data directly within your AI workflow.
You might also like
Miro
Manage Miro boards, items and comments via API — create boards, add sticky notes, browse items and manage members from any AI agent.
OilPrice
Access real-time and historical oil, gas, and energy commodity prices — WTI, Brent, Natural Gas, Diesel, and 40+ more via OilPriceAPI.
Shipmondo
Ship packages across Scandinavia and Europe with multi-carrier label printing, tracking, and return management from one platform.