by intento
Provides translation capabilities via the Intento API through an MCP server, exposing a translate tool and a language‑codes resource for agents.
The server implements an MCP endpoint that allows clients to translate text between any languages supported by the Intento API. It also publishes a resource containing the latest mapping of language names to ISO codes, keeping language support up‑to‑date automatically.
pip install -r requirements.txt
.env
file in the project root with INTENTO_API_KEY=your_api_key
or specify the key in the env
section of your MCP client configuration.python server.py
translate
tool
result = await translate("Hello world", target_language="Spanish")
# or with explicit source language
result = await translate("Hello world", target_language="es", source_language="en")
language_codes = await get_resource("mcp://intento-translate/language-codes")
spanish_code = language_codes["codes"]["spanish"]
logs/intento-translate.log
with clear messages for API failures and invalid codes.Q: Do I need to specify a source language?
A: No. Leaving source_language
empty triggers automatic detection by the Intento API.
Q: How often are language codes refreshed? A: The server fetches them each time it starts; you can restart the server to pick up any new languages added by Intento.
Q: What happens if the Intento API call fails? A: The server returns a descriptive error message and falls back to a minimal common‑language set for continued operation.
Q: Can different MCP clients use different API keys?
A: Yes. Set the INTENTO_API_KEY
in the env
section of each client’s MCP config JSON to override the server‑wide key.
Q: Where are logs stored?
A: All logs are written to logs/intento-translate.log
under the project directory.
This is an MCP server that provides translation capabilities using the Intento API.
pip install -r requirements.txt
There are two options:
2.a. Setting Intento API credentials for the MCP server (all your MCP clients will use the same credentials)
To set up Intento API credentials for the MCP server:
.env
file in the project rootINTENTO_API_KEY=your_api_key_here
2.b. Setting Intento API credentials for the specific MCP integration, say, Claude Desktop (different MCP clients may use different credentials)
To set up Intento API credentials for the specific MCP integration:
python server.py
Translates text between languages. Accepts both language names and ISO codes.
Parameters:
text
(required): The text to translatetarget_language
(required): Target language (e.g., "Spanish" or "es")source_language
(optional): Source language (defaults to empty string for automatic detection)Example:
# Translate with automatic language detection
result = await translate("Hello world", target_language="Spanish")
# Translate with specific source language
result = await translate("Hello world", target_language="Spanish", source_language="English")
Resource URL: mcp://intento-translate/language-codes
Provides a mapping of language names to their ISO codes as supported by the Intento API.
This resource allows agents to:
Example of using the resource:
# Get the language codes resource
language_codes = await get_resource("mcp://intento-translate/language-codes")
# Look up a language code
spanish_code = language_codes["codes"]["spanish"] # Returns "es"
# Use the code in a translation
result = await translate("Hello world", target_language=spanish_code)
The server dynamically fetches language codes from the Intento API and makes them available as a resource. This approach has several advantages:
When the source_language
parameter is empty (the default), the server will:
If the API request fails, the server falls back to a minimal set of common language codes.
The server includes comprehensive error handling and logging:
logs/intento-translate.log
To use this MCP server with Claude Desktop:
Create a claude-mcp-config.json
file in your Claude Desktop configuration directory:
%APPDATA%\Claude\claude-mcp-config.json
~/Library/Application Support/Claude/claude-mcp-config.json
~/.config/Claude/claude-mcp-config.json
Add the following configuration (adjust paths to match your installation):
{
"mcpServers": {
"intento-translate": {
"command": "python",
"args": ["/path/to/your/mcp-intento-translate/server.py"],
"cwd": "/path/to/your/mcp-intento-translate",
"env": {
"INTENTO_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
The "env" part with "INTENTO_API_KEY" is required only if you want to use specific credentials for the integration and not use MCP server-specific credentials.
The server will now be available to Claude Desktop, providing translation capabilities and language code information through the MCP protocol.
Please log in to share your review and rating for this MCP.
Explore related MCPs that share similar capabilities and solve comparable challenges
by DeepLcom
Provides translation and rephrasing capabilities powered by the DeepL API via a Model Context Protocol server.
by vlinr
Provides automated translation of localization files (.ts, .js, .json) using large language models, extracting the target language from the filename and supporting both single‑file and directory batch processing.
by zed-industries
A high‑performance, multiplayer code editor designed for speed and collaboration.
by modelcontextprotocol
A Model Context Protocol server that provides web content fetching capabilities.
by modelcontextprotocol
Model Context Protocol Servers
by modelcontextprotocol
An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process.
by modelcontextprotocol
A Model Context Protocol server for Git repository interaction and automation.
by modelcontextprotocol
A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.
by modelcontextprotocol
A Model Context Protocol server that provides time and timezone conversion capabilities.