In-depth architectural comparison of the Polytranslator and Xcomet MCP Server 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
Polytranslator
Translation Services · Remote HTTP/SSE
Quality: 36/100 (Fair) | Auth: No auth required
Xcomet MCP Server
Translation Services · Local stdio
Quality: 60/100 (Good) | Auth: other
Verdict Summary: Choose Polytranslator if you need specialized Translation Services tools running via a hosted cloud SSE transport. Choose Xcomet MCP Server 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 Polytranslator when:
You need dedicated capabilities in the Translation Services domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
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).
Polytranslator is categorized under Translation Services and uses a remote streaming HTTP/SSE transport. In contrast, Xcomet MCP Server belongs to Translation Services using local stdio subprocess. Select Polytranslator when you need capabilities focused on translation services and Xcomet MCP Server when you require tools for translation services.