translate
Translate plain text or HTML while choosing the source language, target language, and global or EU processing.
Model Context Protocol
Give AI assistants a reliable translation tool
Connect Langbly to ChatGPT, Claude, or another MCP-compatible client. Translate text and HTML, detect languages, and keep eligible workloads on an EU processing path—all through one remote MCP endpoint.
Directory publication is in progress. You can use the endpoint when your client or workspace allows custom remote MCP servers.
Remote MCP endpoint
Server URL
https://mcp.langbly.com/mcpRemote Streamable HTTP transport
OAuth account authorization
Global and EU processing paths
Account usage and spending controls still apply
Three focused tools
A small tool surface that is easy to understand
The first release stays deliberately narrow. Every tool has a clear job, structured input and output, and explicit behavior for errors and account limits.
detect_language
Detect the most likely language before an assistant decides how the content should be handled.
list_languages
Return the supported languages so an assistant can validate a workflow before translating.
From a prompt to an account-controlled tool call
- 1
Add the endpoint
Enter the Langbly MCP URL in a client that supports custom remote servers.
- 2
Approve OAuth access
Sign in to Langbly and approve the requested connection for your account.
- 3
Ask for a translation
The assistant selects a tool and sends only the arguments needed for that call.
- 4
Use the result
Langbly returns structured output that the assistant can use in the conversation or workflow.
Example prompts
“Translate this product description from English to German.”
“Detect the language of this customer message, then translate it to Dutch.”
“Translate this HTML to French while preserving the markup.”
“Which target languages are supported before I build this workflow?”
OAuth instead of pasted API keys
The connection is tied to the user’s existing Langbly account. OAuth tokens are restricted to the MCP resource and are not forwarded to the translation service.
Existing controls stay active
Plan entitlement, monthly usage, spending limits, rate limits, and disabled-account checks remain part of every account-bound translation request.
Optional EU processing
Choose EU data residency for eligible calls. The request is then routed to the dedicated EU translation path instead of the global path.
FAQ
Langbly MCP server questions
What is the Langbly MCP server?
It is a remote Model Context Protocol server that gives compatible AI assistants access to Langbly translation, language detection, and supported-language tools.
Does the MCP server work with ChatGPT and Claude?
The server follows the remote MCP standard and is being prepared for ChatGPT, Claude, and other compatible clients. Directory publication is still in progress, so availability depends on the client and workspace settings.
How do users sign in?
Users connect through OAuth and approve access to their existing Langbly account. They do not paste a Langbly API key into the AI client.
Can translation processing stay in the EU?
Yes. A tool call can request EU data residency, which routes translation through Langbly’s dedicated EU processing path.
Can MCP translation create usage charges?
Yes. Successful translation calls count toward the connected Langbly account’s usage and may be billable under its current plan. Language detection and listing supported languages do not translate content.