Bring Machine Translation
to Cursor
Learn how to connect DeepL to Cursor and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the DeepL MCP Server?
Connect your DeepL account to any AI agent and access neural machine translation through natural conversation.
What you can do
- Text Translation — Translate text into 30+ languages with optional formality control (formal, informal, or default)
- Glossary-Powered Translation — Apply custom glossaries to ensure consistent terminology across translations
- Glossary Management — Create, list, inspect, and delete custom glossaries with TSV term pairs
- Language Discovery — List all supported source and target languages, and glossary language pair combinations
- API Usage Monitoring — Track character count consumed, remaining quota, and billing period
- Document Translation — Monitor the progress of submitted document translations
How it works
1. Subscribe to this server
2. Enter your DeepL API Key from your account dashboard
3. Start translating from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Localization Teams — translate marketing copy, product descriptions, and documentation with consistent terminology via glossaries
- Content Creators — translate blog posts and social media content with appropriate formality for each market
- Developers — integrate high-quality translation into AI workflows and monitor API consumption
Built-in capabilities (14)
Create a glossary
Delete a glossary
Check document translation status
Get glossary details
Get glossary entries
Check API usage
List glossaries
List glossary language pairs
List source languages
List target languages
Translate with formal tone
Translate with informal tone
Translate text
Translate using glossary
Why Cursor?
Cursor's Agent mode turns DeepL into an in-editor superpower. Ask Cursor to generate code using live data from DeepL and it fetches, processes, and writes. all in a single agentic loop. 14 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
DeepL in Cursor
DeepL and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect DeepL to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for DeepL in Cursor
The DeepL MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 14 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
DeepL for Cursor
Every tool call from Cursor to the DeepL MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I control the formality of translations (formal vs. informal)?
Yes! Use translate_formal for professional communications (e.g., contracts, official correspondence) or translate_informal for casual content (e.g., social media, chat). The standard translate_text tool also accepts an optional formality parameter ('more', 'less', or 'default'). Note: formality control is available for select target languages including DE, FR, ES, PT-BR, and others.
Can I create custom glossaries to ensure consistent terminology?
Yes. Use create_glossary with a name, source language, target language, and TSV entries (tab-separated source→target pairs). Then use translate_with_glossary to apply the glossary during translation. Use list_glossaries to see all glossaries, get_glossary_entries to inspect term pairs, and list_glossary_language_pairs for supported combinations.
How does DeepL authentication differ from standard Bearer tokens?
DeepL uses a custom Authorization header format: DeepL-Auth-Key YOUR_KEY (not Bearer). Your API key is generated from the DeepL account dashboard. Free accounts use api-free.deepl.com, while Pro accounts use api.deepl.com. Use get_usage to check your current character consumption and plan limits.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.