Model Context Protocol (MCP) Server for the Open English Translation of the Bible (OET)
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":"oet-mcp-server","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.
# Open English Translation (OET) MCP Server An official **Model Context Protocol (MCP)** server providing Large Language Models (LLMs) with high-speed, structured access to the **Open English Translation (OET)** of the Bible. --- ## What Makes the OET Different? 1. **Dual-Stream Parallel Translation**: * **Readers' Version (OET-RV)**: Natural, idiomatic, thought-for-thought modern English designed for macro-level discourse comprehension and fluency. * **Literal Version (OET-LV)**: Transparent, hyper-literal formal equivalence showing every added copula, article, transitive direct object, and untranslated particle. 2. **Word-Level Lexical Graph & Interlinear**: * Every word token is cross-linked via TSV datasets to Hebrew/Aramaic (`UHB`) and Greek (`SR-GNT`) dictionary entries, lemmas, Strong's numbers, morphological tags, and canonical gloss distributions. 3. **Explicit Translation Decision Tags (`\add`)**: * Encodes the exact reason for every addition or divergence (`@` for referent replacements, `≈` for rewordings, `#` for number changes, `%` for speech shifts, `^` for opposite phrasing, `?` for uncertainty, `≈`/`^`/`→` for Hebrew poetic parallelism, and `⇔` for clause re-ordering). --- ## Quick Start ### Running via `uvx` ```bash uvx oet-mcp-server ``` ### Installation from Source > **Note:** the 191 MB corpus database is a **Git-LFS** file. Without > `git lfs pull` you get only a ~130-byte LFS pointer, and every data tool > fails at runtime. ```bash git clone https://github.com/Freely-Given-org/open-english-translation-mcp-server.git cd open-english-translation-mcp-server git lfs install && git lfs pull # materialize the real corpus database uv sync uv run oet-mcp-server ``` --- ## AI Client Configuration ### 1. Claude Desktop / Antigravity / Cursor Add to your `claude_desktop_config.json` or MCP settings: ```json { "mcpServers": { "oet-bible": { "command": "uvx", "args": ["oet-mcp-server"] } } } ``` Or for…
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.