An MCP server for translating long-form text in chunks.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-translator","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Translator Server This project provides an MCP (Model Context Protocol) server designed to facilitate the translation of long-form text documents. ## Features * Accepts paths to multiple text files for concurrent translation jobs. * Splits each text file into manageable chunks. * Stores chunks and their translation status in a SQLite database (`translation_progress.db`), keeping track of which file each chunk belongs to. * Provides tools to: * Initialize or restart the translation process for a specific file (`start_translation file_path=...`). Clears previous progress for that file if it existed. * List all ongoing translation jobs and their progress (`list_jobs`). * Fetch the next untranslated chunk for a specific file (`get_next_chunk file_path=...`). * Submit the translation for a specific chunk ID (`submit_translation chunk_id=... translated_text=...`). ## Setup 1. Install dependencies: ```bash pip install . # Or pip install -e . for development mode ``` 2. Download the spaCy model: ```bash python -m spacy download xx_sent_ud_sm ``` ## Running the Server ```bash mcp-translator ``` This will start the MCP server, listening for client connections. The database file (`translation_progress.db`) will be created in the same directory as `server.py`. ## Usage Connect an MCP client (like a compatible AI assistant or script) to the running server. The client can then use the available tools, making sure to specify the `file_path` where required (`start_translation`, `get_next_chunk`), to manage the translation workflow for different files.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.