Install
$ agentstack add mcp-shuji-bonji-xcomet-mcp-server ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
xCOMET MCP Server
[](https://www.npmjs.com/package/xcomet-mcp-server) [](https://github.com/shuji-bonji/xcomet-mcp-server/actions/workflows/ci.yml) [](https://modelcontextprotocol.io) [](https://opensource.org/licenses/MIT)
[日本語版 README はこちら](README.ja.md)
> ⚠️ This is an unofficial community project, not affiliated with Unbabel.
Translation quality evaluation MCP Server powered by xCOMET (eXplainable COMET).
🎯 Overview
xCOMET MCP Server provides AI agents with the ability to evaluate machine translation quality. It integrates with the xCOMET model from Unbabel to provide:
- Quality Scoring: Scores between 0-1 indicating translation quality
- Error Detection: Identifies error spans with severity levels (minor/major/critical)
- Batch Processing: Evaluate multiple translation pairs efficiently (optimized single model load)
- GPU Support: Optional GPU acceleration for faster inference
graph LR
A[AI Agent] --> B[Node.js MCP Server]
B -- stdio JSON-RPC --> C[Python Worker]
C --> D[xCOMET ModelPersistent in Memory]
D --> C
C --> B
B --> A
style D fill:#9f9
🔧 Prerequisites
Python Environment
- Python 3.9 - 3.12 recommended (3.13+ is not yet supported by xCOMET dependencies)
xCOMET requires Python with several packages. We recommend using a virtual environment:
# If using uv (recommended - auto-downloads the correct Python version)
uv venv ~/.xcomet-venv --python 3.12
source ~/.xcomet-venv/bin/activate
uv pip install "unbabel-comet>=2.2.0"
# Or using standard venv (requires Python 3.9-3.12 already installed)
python3 -m venv ~/.xcomet-venv
source ~/.xcomet-venv/bin/activate # Windows: ~/.xcomet-venv\Scripts\activate
pip install "unbabel-comet>=2.2.0"
> Note (v0.5.0+): The Python worker now talks to Node.js over stdin/stdout > (line-delimited JSON-RPC). FastAPI, uvicorn, and pydantic are no longer > required — only unbabel-comet is.
> Note: When using with Claude Desktop or other MCP hosts, set XCOMET_PYTHON_PATH to point to the venv Python (see [Configuration](#-configuration)).
Model Download
> Important: XCOMET-XL and XCOMET-XXL are gated models on HuggingFace. You must: > 1. Create a HuggingFace account > 2. Visit Unbabel/XCOMET-XL and request access > 3. Login via CLI: > ``bash > source ~/.xcomet-venv/bin/activate > huggingface-cli login > ` > > Unbabel/wmt22-comet-da` does not require authentication (but requires reference translations).
After authentication, download the model (~14GB for XL, ~42GB for XXL):
source ~/.xcomet-venv/bin/activate
python -c "from comet import download_model; download_model('Unbabel/XCOMET-XL')"
Node.js
- Node.js >= 22.0.0 (matches
engines.nodeinpackage.json; CI runs on 22 and 24) - npm or yarn
📦 Installation
> Note: If you just want to use xCOMET MCP Server, you do not need to clone this repository. Install the Python environment and model (see [Prerequisites](#-prerequisites)), then use npx (see [Usage](#-usage)). The section below is for contributors and local development only.
Local Development
For contributors and local development:
# Clone the repository
git clone https://github.com/shuji-bonji/xcomet-mcp-server.git
cd xcomet-mcp-server
# Set up Python virtual environment and install dependencies
uv venv .venv --python 3.12 # or: python3 -m venv .venv
source .venv/bin/activate
pip install -r python/requirements.txt
# Install Node.js dependencies and build
npm install
npm run build
🚀 Usage
With Claude Desktop (npx)
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"xcomet": {
"command": "npx",
"args": ["-y", "xcomet-mcp-server"],
"env": {
"XCOMET_PYTHON_PATH": "~/.xcomet-venv/bin/python3"
}
}
}
}
> Tip: If you installed Python packages system-wide or use pyenv, XCOMET_PYTHON_PATH may be omitted (auto-detection will find it). See [Python Path Auto-Detection](#python-path-auto-detection) for details.
With Claude Code
claude mcp add xcomet --env XCOMET_PYTHON_PATH=~/.xcomet-venv/bin/python3 -- npx -y xcomet-mcp-server
Global Installation
If you prefer installing globally:
npm install -g xcomet-mcp-server
Then configure:
{
"mcpServers": {
"xcomet": {
"command": "xcomet-mcp-server",
"env": {
"XCOMET_PYTHON_PATH": "~/.xcomet-venv/bin/python3"
}
}
}
}
Local Development Build
If you cloned and built the repository locally (see [Installation](#-installation-local-development)):
{
"mcpServers": {
"xcomet": {
"command": "node",
"args": ["/path/to/xcomet-mcp-server/dist/index.js"],
"env": {
"XCOMET_PYTHON_PATH": "~/.xcomet-venv/bin/python3"
}
}
}
}
🛠️ Available Tools
xcomet_evaluate
Evaluate translation quality for a single source-translation pair.
Parameters: | Name | Type | Required | Description | |------|------|----------|-------------| | source | string | ✅ | Original source text | | translation | string | ✅ | Translated text to evaluate | | reference | string | ❌ | Reference translation | | source_lang | string | ❌ | Source language code (ISO 639-1) | | target_lang | string | ❌ | Target language code (ISO 639-1) | | response_format | "json" \| "markdown" | ❌ | Output format (default: "json") | | use_gpu | boolean | ❌ | Use GPU for inference (default: false) |
Example:
{
"source": "The quick brown fox jumps over the lazy dog.",
"translation": "素早い茶色のキツネが怠惰な犬を飛び越える。",
"source_lang": "en",
"target_lang": "ja",
"use_gpu": true
}
Response:
{
"score": 0.847,
"errors": [],
"summary": "Good quality (score: 0.847) with 0 error(s) detected."
}
xcomet_detect_errors
Focus on detecting and categorizing translation errors.
Parameters: | Name | Type | Required | Description | |------|------|----------|-------------| | source | string | ✅ | Original source text | | translation | string | ✅ | Translated text to analyze | | reference | string | ❌ | Reference translation | | min_severity | "minor" \| "major" \| "critical" | ❌ | Minimum severity (default: "minor") | | response_format | "json" \| "markdown" | ❌ | Output format | | use_gpu | boolean | ❌ | Use GPU for inference (default: false) |
xcomet_batch_evaluate
Evaluate multiple translation pairs in a single request.
> Performance Note: With the persistent server architecture (v0.3.0+), the model stays loaded in memory. Batch evaluation processes all pairs efficiently without reloading the model.
Parameters: | Name | Type | Required | Description | |------|------|----------|-------------| | pairs | array | ✅ | Array of {source, translation, reference?} (max 500) | | source_lang | string | ❌ | Source language code | | target_lang | string | ❌ | Target language code | | response_format | "json" \| "markdown" | ❌ | Output format | | use_gpu | boolean | ❌ | Use GPU for inference (default: false) | | batch_size | number | ❌ | Batch size 1-64 (default: 8). Larger = faster but uses more memory |
Example:
{
"pairs": [
{"source": "Hello", "translation": "こんにちは"},
{"source": "Goodbye", "translation": "さようなら"}
],
"use_gpu": true,
"batch_size": 16
}
🔗 Integration with Other MCP Servers
xCOMET MCP Server is designed to work alongside other MCP servers for complete translation workflows:
sequenceDiagram
participant Agent as AI Agent
participant DeepL as DeepL MCP Server
participant xCOMET as xCOMET MCP Server
Agent->>DeepL: Translate text
DeepL-->>Agent: Translation result
Agent->>xCOMET: Evaluate quality
xCOMET-->>Agent: Score + Errors
Agent->>Agent: Decide: Accept or retry?
Recommended Workflow
- Translate using DeepL MCP Server (official)
- Evaluate using xCOMET MCP Server
- Iterate if quality is below threshold
Example: DeepL + xCOMET Integration
Configure both servers in Claude Desktop:
{
"mcpServers": {
"deepl": {
"command": "npx",
"args": ["-y", "@anthropic/deepl-mcp-server"],
"env": {
"DEEPL_API_KEY": "your-api-key"
}
},
"xcomet": {
"command": "npx",
"args": ["-y", "xcomet-mcp-server"],
"env": {
"XCOMET_PYTHON_PATH": "~/.xcomet-venv/bin/python3"
}
}
}
}
Then ask Claude: > "Translate this text to Japanese using DeepL, then evaluate the translation quality with xCOMET. If the score is below 0.8, suggest improvements."
⚙️ Configuration
Environment Variables
| Variable | Default | Description | |----------|---------|-------------| | XCOMET_MODEL | Unbabel/XCOMET-XL | xCOMET model to use | | XCOMET_PYTHON_PATH | (auto-detect) | Python executable path (see below) | | XCOMET_PRELOAD | false | Pre-load model at startup (v0.3.1+) | | XCOMET_DEBUG | false | Enable verbose debug logging (v0.3.1+) | | XCOMET_NUM_WORKERS | 1 | DataLoader workers for model.predict() (v0.6.0+). Increase to better utilize idle CPU cores when running large batches, especially on GPU. Invalid values silently fall back to 1. |
Model Selection
Choose the model based on your quality/performance needs:
| Model | Parameters | Size | Memory | Reference | HF Auth | Quality | Use Case | |-------|------------|------|--------|-----------|---------|---------|----------| | Unbabel/XCOMET-XL | 3.5B | ~14GB | ~8-10GB | Optional | ✅ Required | ⭐⭐⭐⭐ | Recommended for most use cases | | Unbabel/XCOMET-XXL | 10.7B | ~42GB | ~20GB | Optional | ✅ Required | ⭐⭐⭐⭐⭐ | Highest quality, requires more resources | | Unbabel/wmt22-comet-da | 580M | ~2GB | ~3GB | Required | Not required | ⭐⭐⭐ | Lightweight, faster loading |
> Important: XCOMET-XL and XCOMET-XXL are gated models on HuggingFace. Each model requires separate access approval. See [Model Download](#model-download) for authentication setup.
> Important: wmt22-comet-da requires a reference translation for evaluation. XCOMET models support referenceless evaluation.
> Tip: If you experience memory issues or slow model loading, try Unbabel/wmt22-comet-da for faster performance with slightly lower accuracy (but remember to provide reference translations).
To use a different model, set the XCOMET_MODEL environment variable:
{
"mcpServers": {
"xcomet": {
"command": "npx",
"args": ["-y", "xcomet-mcp-server"],
"env": {
"XCOMET_MODEL": "Unbabel/XCOMET-XXL"
}
}
}
}
Python Path Auto-Detection
The server automatically detects a Python environment with unbabel-comet installed:
XCOMET_PYTHON_PATHenvironment variable (if set)- pyenv versions (
~/.pyenv/versions/*/bin/python3) - checks forcometmodule - Homebrew Python (
/opt/homebrew/bin/python3,/usr/local/bin/python3) - Fallback:
python3command
This ensures the server works correctly even when the MCP host (e.g., Claude Desktop) uses a different Python than your terminal.
Example: Explicit Python path configuration
{
"mcpServers": {
"xcomet": {
"command": "npx",
"args": ["-y", "xcomet-mcp-server"],
"env": {
"XCOMET_PYTHON_PATH": "/Users/you/.pyenv/versions/3.11.0/bin/python3"
}
}
}
}
⚡ Performance
Persistent Worker Architecture (v0.3.0+, stdio since v0.5.0)
The server uses a persistent Python worker process that keeps the xCOMET model loaded in memory. The Node.js MCP server talks to the worker over stdin/stdout using a line-delimited JSON-RPC protocol — no local HTTP listener, no port binding, no FastAPI.
| Request | Time | Notes | |---------|------|-------| | First request | ~25-90s | Model loading (varies by model size) | | Subsequent requests | ~500ms | Model already loaded |
This provides a 177x speedup for consecutive evaluations compared to reloading the model each time.
Eager Loading (v0.3.1+)
Enable XCOMET_PRELOAD=true to pre-load the model at server startup:
{
"mcpServers": {
"xcomet": {
"command": "npx",
"args": ["-y", "xcomet-mcp-server"],
"env": {
"XCOMET_PRELOAD": "true"
}
}
}
}
With preload enabled, all requests are fast (~500ms), including the first one.
graph LR
A[MCP Request] --> B[Node.js Server]
B -- stdio JSON-RPC --> C[Python Worker]
C --> D[xCOMET Modelin Memory]
D --> C
C --> B
B --> A
style D fill:#9f9
Batch Processing Optimization
The xcomet_batch_evaluate tool processes all pairs with a single model load:
| Pairs | Estimated Time | |-------|----------------| | 10 | ~30-40 sec | | 50 | ~1-1.5 min | | 100 | ~2 min |
GPU vs CPU Performance
| Mode | 100 Pairs (Estimated) | |------|----------------------| | CPU (batchsize=8) | ~2 min | | GPU (batchsize=16) | ~20-30 sec |
> Note: GPU requires CUDA-compatible hardware and PyTorch with CUDA support. If GPU is not available, set use_gpu: false (default).
Best Practices
1. Let the persistent server do its job
With v0.3.0+, the model stays in memory. Multiple xcomet_evaluate calls are now efficient:
✅ Fast: First call loads model, subsequent calls reuse it
xcomet_evaluate(pair1) # ~90s (model loads)
xcomet_evaluate(pair2) # ~500ms (model cached)
xcomet_evaluate(pair3) # ~500ms (model cached)
2. For many pairs, use batch evaluation
✅ Even faster: Batch all pairs in one call
xcomet_batch_evaluate(allPairs) # Optimal throughput
3. Memory considerations
- XCOMET-XL requires ~8-10GB RAM
- For large batches (500 pairs), ensure sufficient memory
- If memory is limited, split into smaller batches (100-200 pairs)
Auto-Restart (v0.3.1+)
The server automatically recovers from failures:
- Monitors health every 30 seconds
- Restarts after 3 consecutive health check failures
- Up to 3 restart attempts before giving up
📊 Quality Score Interpretation
| Score Range | Quality | Recommendation | |-------------|---------|----------------| | 0.9 - 1.0 | Excellent | Ready for use | | 0.7 - 0.9 | Good | Minor review recommended | | 0.5 - 0.7 | Fair | Post-editing needed | | 0.0 - 0.5 | Poor | Re-translation recommended |
🔍 Troubleshooting
Common Issues
"No module named 'comet'"
Cause: Python environment without unbabel-comet installed.
Solution:
# Check which Python is being used
python3 -c "import sys; print(sys.executable)"
# If using a virtual environment, make sure it's activated
source .venv/bin/activate
pip install -r python/requirements.txt
# For MCP hosts (e.g., Claude Desktop), specify the venv Python path
export XCOMET_PYTHON_PATH=~/.xcomet-venv/bin/python3
Model download fails or times out
Cause: Large model files (~14GB for XL) require stable internet connection. XCOMET models also require HuggingFace authentication (see [Model Download](#model-download)).
Solution:
# Login to HuggingFace (required for XCOMET-XL/XXL)
huggingface-cli login
# Pre-download the model manually
python -c "from comet import download_model; download_model('Unbabel/XCOMET-XL')"
GPU not detected
Cause: PyTorch not installed with CUDA support.
Solution:
# Check CUDA availability
python -c "import torch; print(torch.cuda.is_available())"
# If False, reinstall PyTorch with CUDA
pip install torch --index-url https://download.pytorch.org/whl/cu118
Slow performance on Mac (MPS)
Cause: Mac MPS (Metal Performance Shaders) has compatibility issues with some operations.
**Solu
…
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: shuji-bonji
- Source: shuji-bonji/xcomet-mcp-server
- License: MIT
- Homepage: https://www.npmjs.com/package/xcomet-mcp-server
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.