Weglot MCP for AI. Automate multilingual content translation from any chat interface.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Weglot MCP automates website translation and localization workflows directly through your AI agent. Check API status, get a list of supported languages, validate specific language pairs, and translate large arrays of text—all without leaving your chat interface.
What AI agents can do with Weglot Automation
Check language support
Confirms if a specific source-to-target language pair is supported for translation.
List languages
Returns a full list of all language codes recognized by the platform.
Get status
Checks the overall operational status of the Weglot API service.
Checks if the Weglot translation service is currently operational before starting a large batch job.
Retrieves a complete list of all language codes that the platform supports, helping you scope your project.
Confirms whether a specific translation direction, like English to Japanese, is supported by Weglot.
Translates large amounts of source text with full control over the output format and metadata.
Ask an AI about this
Waiting for input…
What AI agents can do with Weglot MCP: 4 Tools for Localization
These four tools let you manage multilingual web content by checking status, listing languages, validating pairs, or executing bulk translations.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Weglot on VinkiusCheck Language Support
Confirms if a specific source-to-target language pair is supported for translation.
List Languages
Returns a full list of all language codes recognized by the platform.
Get Status
Checks the overall operational status of the Weglot API service.
Translate Text
Translates multiple sentences provided in an array format, requiring your API key.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 Weglot, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Weglot. 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
Built on the Model Context Protocol (MCP) for 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 connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually managing content for every market is a massive time sink., Solved with Vinkius AI Gateway
Right now, if you launch globally, your team spends days clicking through translation dashboards. You pull source strings from the CMS, dump them into a spreadsheet, then copy-paste those snippets into a translator API or even an external web tool. Every time you hit 'translate,' you're dealing with context loss and manual error checking.
With this MCP, your AI agent handles that entire sequence inside one conversation thread. You just tell the agent what needs translating, and it calls the necessary tools to manage the process. The result is accurate, structured data ready for use—no more copy-pasting required.
The Weglot MCP gives you verifiable language support.
Before translating anything, a developer used to waste time checking if the API was even up. They'd run through multiple translation attempts until one finally worked or failed with an ambiguous error code.
Now, they start by calling `get_status` and then use `list_languages`. This gives immediate confirmation that both the service is running and that all required language codes are valid before a single line of content is sent.
What your AI can actually do with this
This connector gives you direct access to Weglot’s powerful translation engine, making multilingual content management part of your daily workflow. Instead of hopping between the Weglot console and your local editor, you run translations right where you're prompting your AI agent. You can validate if a language pair is supported before running a full batch, or you can feed it an array of strings for high-volume translation.
The real power comes when you start chaining this MCP with others in the Vinkius catalog; you could pass content from a CMS MCP to Weglot and then send confirmation messages via a messaging MCP—all through one automated flow. Since your API keys pass through a zero-trust proxy, you never have to worry about them sitting on disk.
You just connect once from any MCP-compatible client and start moving global content.
019ea60f-5f45-7237-91bb-2558da3b4c9a Here's how it actually works
The bottom line is you get instant, API-driven localization results without switching applications.
Subscribe to this MCP and provide your Weglot API key.
Use your AI client to check the platform status or list supported languages. This validates that everything is ready to go.
Execute the translation by providing the text array, source language, and target language.
Who is this actually for?
Product Managers who manage global launches, Localization Engineers running CI/CD checks, and Technical Writers dealing with UI strings for dozens of markets. If manual translation checking slows down your sprint reviews, you need this.
Uses the MCP to quickly check language support or validate if specific translations are ready before handoff.
Feeds raw text strings into the tool to get instant, context-aware translations for documentation drafts.
Integrates translation checks into automated pipelines by verifying API status and language support before deployment.
What Changes When You Connect
Stop guessing if a language pair works. Use check_language_support to confirm support before writing code, eliminating failed deployment builds.
Need to know what languages you can target? Running the list_languages tool gives you the full roster of supported codes in one prompt.
Manage high volumes easily. The translate_text action handles entire arrays of strings, letting you process UI text that used to take hours of copy-pasting.
Know if the service is up? Use get_status first. This quick check prevents your workflow from failing midway through a major content dump.
It's designed for automation. Because it runs on Vinkius, you can easily chain this MCP with another platform's MCP to build full localization pipelines.
See it in action
Pre-flight Localization Check
Before running a major content migration, the agent first calls get_status and then uses list_languages. This confirms both service uptime and that all necessary language codes are available before any translation work starts.
Documentation String Translation
A technical writer needs to translate 50 UI strings for a new feature. Instead of using an external tool, they prompt the agent to execute translate_text with all the strings in an array, getting instant results.
Market Expansion Planning
A PM needs to know if their target market (e.g., Icelandic) is supported. They use the agent to call check_language_support for a known pairing, confirming feasibility before committing resources.
Cross-Platform Content Sync
The user chains this MCP with a CMS MCP. The content gets pulled from the CMS, and then the agent automatically executes translate_text, pushing the finished, localized text back into the system.
The honest tradeoffs
Translating everything at once
Running a massive translation job without first checking if the target language is actually supported. The call fails and leaves you hanging.
Always check compatibility first. Use list_languages to confirm your codes, then run check_language_support before attempting any full translate_text action.
Ignoring service downtime
Starting a large translation job and having it fail halfway through because the Weglot API is temporarily down or under maintenance.
Always start with an API health check. Call get_status first to ensure the platform is running smoothly before you dedicate time to translating.
Manual copy/pasting
Copying 10 different snippets into a spreadsheet and manually pasting them one by one into an external translator.
Use the translate_text tool. It accepts arrays, allowing you to send dozens of strings in a single structured call.
When It Fits, When It Doesn't
You need this MCP if your workflow requires automating content localization at scale. Specifically, use it when you must confirm API status (get_status), check language availability (list_languages), or process many texts (using translate_text). Don't use it if all you are doing is translating one sentence for a friend. If your needs boil down to simple copy-paste text, an external tool works fine. But if you're building actual automation—the kind that connects content from a database to a messaging system and then translates it—this MCP is essential. Remember, by using Vinkius, your keys are protected in transit through the zero-trust proxy, so you don't have to worry about local security risks when automating these critical paths.
Questions you might have
How do I check if Weglot supports English to German using the translate_text tool? +
You shouldn't use translate_text for checking compatibility. Instead, run check_language_support first. This confirms the pair works before you attempt the actual translation.
Is `list_languages` limited to my current API key? +
list_languages pulls a comprehensive list of all languages supported by the platform generally, not just what's available in your specific account. It gives you the full scope.
What is the best first step when I connect Weglot MCP? +
Always run get_status immediately. This simple check verifies that the API connection is live and operational, preventing unnecessary failures later on.
Can I use translate_text for non-string content like images? +
No. The translate_text tool is designed only for translating arrays of text strings. It cannot process file types or other media.
How do I use `get_status` to verify Weglot's API health before a large translation batch? +
It immediately checks the current operational status of the Weglot API. This prevents wasted calls and ensures your agent won't fail mid-job, giving you confidence for high-volume content deployment.
What if I need to verify a specific translation pair, like French to Portuguese? How do I use `check_language_support`? +
You pass the two language codes into check_language_support. It gives a definitive yes or no answer on support. This saves you from running a full translation job only for it to fail later.
Are there rate limits when I run many translations using `translate_text`? +
The MCP handles connection management, but you should batch your calls logically. If you hit an API limit, the tool returns a specific error code that tells you exactly how long to wait before trying again.
How can I use `list_languages` to create a master list of all supported language codes? +
Calling list_languages generates an exhaustive roster of every locale Weglot supports. This is essential for planning your content scope and ensuring no target market gets overlooked during initial setup.
How can I verify if the Weglot API is currently online? +
You can use the get_status tool. It performs a real-time health check to ensure the Weglot API is responsive and operational.
Can I check if a specific translation pair like English to German is supported? +
Yes! Use the check_language_support tool by providing the source (languageFrom) and destination (languageTo) ISO codes.
What format should I use to translate multiple sentences at once? +
The translate_text tool requires a words_json parameter. This should be a JSON array of objects, for example: [{"t": 1, "w": "Hello world"}].
We've already built the connector for Weglot. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 4 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.