Nabu
Related Servers
Alternatives to Nabu
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceAn MCP server for Christian scholarship and research, providing read-only access to a SQLite corpus of 66-book BSB and 83-book WEB Bibles, original-language Greek/Hebrew word studies with Strong's and morphology, cross-references, patristic citations (Irenaeus, Justin Martyr, Apostolic Fathers), verse alignments, semantic and hybrid search over ~55,800 embeddings, and multi-work passage retrieval, interlinear lookup, and research-brief synthesis prompts.3-
- AlicenseNot gradedqualityCmaintenanceSemantic search and comparative retrieval over a multi-tradition corpus of sacred and foundational texts, exposed as an MCP server.MIT
- AlicenseBqualityDmaintenanceProvides Hebrew & Greek word study, full morphological parsing, cross-references, LXX alignment, and more from open-licensed data sources, usable by any MCP-compatible client.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables local reading, searching, and scholarly study of the Bible through MCP tools, including passage lookup, literal search, topical research, word study, related-passage discovery, passage comparison, and corpus overviews.22 npmMIT
- AlicenseNot gradedqualityDmaintenanceBiblical text analysis with textual criticism support. An MCP server for morphological analysis, manuscript variants, and concordance searches across Hebrew and Greek biblical texts.MIT
- AlicenseNot gradedqualityBmaintenancePostgreSQL-backed MCP server for deep Bible study, integrating 140+ translations, Greek/Hebrew lexicons, cross-references, and semantic search.MIT
TDQS
Scored across 14 tools
Most tools occupy clearly distinct niches, and the descriptions actively police the tricky boundaries: nabu_search (ranked relevance) vs nabu_concord (corpus-order KWIC), nabu_parallels (on-the-fly intertext) vs nabu_links (persisted batch edges), nabu_etym (reconstruction crosswalk) vs nabu_define (dictionary shelf). The weakest pairs are nabu_char vs nabu_signs (single glyph card vs token-by-token ATF resolution) and nabu_cognates vs nabu_etym (verse-level vs lemma-level), which are separated in prose but could still be misselected by an agent skimming names.
Every tool follows the same `nabu_` prefix plus a single lowercase token in snake_case, with no camelCase or casing drift, so the namespace is highly predictable. The only minor deviation is grammatical style: a mix of verbs (search, show, align, define, clarify) and nouns (parallels, status, concord, etym, cognates, links, char, place, signs) rather than a uniform verb_noun pattern.
At 14 tools the surface sits comfortably in the well-scoped range, and each tool maps to a genuine research operation (search, read, coverage, concordance, alignment, parallels, links, lexicon, etymology, cognates, glyph, place, signs, reference resolution). No tool looks like filler, and none of the heavy multi-lane behavior is duplicated across tools.
The read-only research lifecycle is well covered: discovery (search/concord/clarify), retrieval (show), cross-witness and intertext comparison (align/parallels/links), lexical and etymological depth (define/etym/cognates), and specialized desks (char/signs/place), plus status for coverage interpretation. The main gap is catalog browsing/enumeration — there is no explicit list-works or list-sources tool, so agents must reach the catalog through nabu_status counts, nabu_clarify completions, or citation-prefix browsing in nabu_show.