Fast JSON i18n translator with AI support (Google Gemini, OpenAI & Ollama), incremental caching, multi-file deduplication, and MCP support
Translator Ai MCP server exists for a simple reason — assistants are far more useful when they can act on Translator Ai directly instead of describing what you should do. Fast JSON i18n translator with AI support (Google Gemini, OpenAI & Ollama), incremental caching, multi-file deduplication, and MCP support.
Once Translator Ai is connected, these are the calls the assistant has available:
inputFile — Path to source filetargetLanguage — Target language codeoutputFile — Output file pathpattern — File pattern or pathsoutputPattern — Output pattern with {dir}, {name}, {lang} variablesshowStats — Show deduplication statistics (optional)Examples — The Examples tool exposed by this serverOllama — The Ollama tool exposed by this serverYou will need 3 environment variables: GEMINI_API_KEY, TRANSLATOR_PROVIDER, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at js-yaml on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Translator Ai's toolset — inputFile, targetLanguage, outputFile and 5 more — is a fair guide to whether it matches your workflow. It is maintained by DatanoiseTV; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| inputFile | Path to source file |
| targetLanguage | Target language code |
| outputFile | Output file path |
| pattern | File pattern or paths |
| outputPattern | Output pattern with {dir}, {name}, {lang} variables |
| showStats | Show deduplication statistics (optional) |
| Examples | The Examples tool exposed by this server. |
| Ollama | The Ollama tool exposed by this server. |
{
"mcpServers": {
"translator-ai": {
"command": "npx",
"args": [
"-y",
"translator-ai-mcp"
],
"env": {
"GEMINI_API_KEY": "your-gemini-api-key-here"
// Or for Ollama:
// "TRANSLATOR_PROVIDER": "ollama"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GEMINI_API_KEY | Credential the server authenticates with. | Yes |
| TRANSLATOR_PROVIDER | Configuration value read at startup. | Optional |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.