DeepL MCP Server for VS Code CopilotGive VS Code Copilot instant access to 14 tools to Create Glossary, Delete Glossary, Get Document Status, and more
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this App Connector for VS Code Copilot
The DeepL app connector for VS Code Copilot is a standout in the Ai Frontier category — giving your AI agent 14 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install DeepL and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"deepl-alternative": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About DeepL MCP Server
Connect your DeepL account to any AI agent and access neural machine translation through natural conversation.
GitHub Copilot Agent mode brings DeepL data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 14 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
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
The DeepL MCP Server exposes 14 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 14 DeepL tools available for VS Code Copilot
When VS Code Copilot connects to DeepL through Vinkius, your AI agent gets direct access to every tool listed below — spanning machine-translation, language-processing, glossary-management, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect DeepL to VS Code Copilot via MCP
Follow these steps to wire DeepL into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using DeepL
Why Use VS Code Copilot with the DeepL MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with DeepL through the Model Context Protocol.
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
DeepL + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the DeepL MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for DeepL in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with DeepL immediately.
"Translate 'Welcome to our platform. We look forward to working with you.' into German (formal) and Brazilian Portuguese (informal)."
"Create a glossary for EN→FR with our brand terms and then translate a marketing paragraph using it."
"Check my DeepL API usage and list all available target languages."
Troubleshooting DeepL MCP Server with VS Code Copilot
Common issues when connecting DeepL to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
DeepL + VS Code Copilot FAQ
Common questions about integrating DeepL MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.