In-depth architectural comparison of the Xcomet MCP Server and Live Translate MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Xcomet MCP Server
Translation Services · Local stdio
Quality: 60/100 (Good) | Auth: other
Live Translate MCP
Translation Services · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Xcomet MCP Server if you need specialized Translation Services tools running via a local process. Choose Live Translate MCP if your workspace requires Translation Services integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Xcomet MCP Server when:
You need dedicated capabilities in the Translation Services domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: XCOMET_PYTHON_PATH.
Translation quality evaluation using xCOMET models. Provides quality scoring (0-1), error detection with severity levels (minor/major/critical), and optimized batch processing with 25x speedup.
Real-time English ↔ Mandarin Chinese speech translation. Transcribes audio locally with Whisper, translates via Claude API, and synthesises speech locally with Piper TTS. Pass a WAV file path and Claude handles the rest.
Category & Scope
Tools & Capabilities Breakdown
Xcomet MCP Server Tools (3)
xcomet_evaluate
Evaluate the quality of a translation using xCOMET model.
This tool analyzes a source text and its translation, providing:
- A quality score between 0 and 1 (higher is better)
- Detected error spans with severity levels (minor/major/critical)
- A human-readable quality summary
Args:
- source (string): Original source text to translate from
- translation (string): Translated text to evaluate
- reference (string, optional): Reference translation for comparison
- source_lang (string, optional): Source language code (ISO 639-1)
- target_lang (string, optional): Target language code (ISO 639-1)
- response_format ('json' | 'markdown'): Output format (default: 'json')
- use_gpu (boolean, optional): Use GPU for inference if available (default: false)
Returns:
For JSON format:
{
"score": number, // Quality score 0-1
"errors": [ // Detected errors
{
"text": string,
"start": number,
"end": number,
"severity": "minor" | "major" | "critical"
}
],
"summary": string // Human-readable summary
}
Examples:
- Evaluate EN→JA translation quality
- Check if MT output needs post-editing
- Compare translation against reference
xcomet_detect_errors
Detect and categorize errors in a translation.
This tool focuses on error detection, providing detailed information about
translation errors with their severity levels and positions.
Args:
- source (string): Original source text
- translation (string): Translated text to analyze
- reference (string, optional): Reference translation
- min_severity ('minor' | 'major' | 'critical'): Minimum severity to report (default: 'minor')
- response_format ('json' | 'markdown'): Output format (default: 'json')
- use_gpu (boolean, optional): Use GPU for inference if available (default: false)
Returns:
{
"total_errors": number,
"errors_by_severity": {
"minor": number,
"major": number,
"critical": number
},
"errors": [
{
"text": string,
"start": number,
"end": number,
"severity": "minor" | "major" | "critical"
}
]
}
Examples:
- Find critical errors before publication
- Identify areas needing post-editing
- Quality gate for MT output
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Xcomet MCP Server is categorized under Translation Services and uses a local stdio subprocess. In contrast, Live Translate MCP belongs to Translation Services using local stdio subprocess. Select Xcomet MCP Server when you need capabilities focused on translation services and Live Translate MCP when you require tools for translation services.
Evaluate multiple translation pairs in a batch.
This tool processes multiple source-translation pairs and provides
aggregate statistics along with individual results.
Args:
- pairs (array): Array of translation pairs, each with:
- source (string): Original source text
- translation (string): Translated text
- reference (string, optional): Reference translation
- source_lang (string, optional): Source language code
- target_lang (string, optional): Target language code
- response_format ('json' | 'markdown'): Output format (default: 'json')
- use_gpu (boolean, optional): Use GPU for inference if available (default: false)
- batch_size (number, optional): Inference batch size, 1-64 (default: 8).
Larger = faster but uses more memory.
Returns:
{
"average_score": number,
"total_pairs": number,
"results": [
{
"index": number,
"score": number,
"error_count": number,
"has_critical_errors": boolean
}
],
"summary": string
}
Examples:
- Evaluate entire translated document
- Compare MT system quality across test set
- Identify segments needing attention
Live Translate MCP Tools (3)
translate_file
Translate a WAV audio file. Pass an absolute path — the server transcribes it, translates the text via Claude, synthesises speech, saves `<name>_translated.wav` next to the original, and plays it automatically.
translate_speech
Translate raw audio passed as a base64-encoded WAV string. Returns the transcription, translation, and synthesised audio as base64 WAV — useful for programmatic workflows.
health_check
Verify that all dependencies (Whisper model cache, Piper voice files, `espeak-ng`) are present and ready before making a translation request.