holy-bible-mcp
Related Servers
Alternatives to holy-bible-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePostgreSQL-backed MCP server for deep Bible study, integrating 140+ translations, Greek/Hebrew lexicons, cross-references, and semantic search.MIT
- FlicenseNot gradedqualityAmaintenanceAn 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.2-
- AlicenseAqualityAmaintenanceFree, no-key MCP server for reading scripture from 35+ public-domain translations in 8 languages. Lets users fetch verses, chapters, and passages via natural language from any MCP client.7MIT
- AlicenseBqualityCmaintenanceProduction-ready MCP server that lets LLMs explore, analyze, and reason over the Bible using local ChromaDB stores and Mistral embeddings.10Apache 2.0
- AlicenseNot gradedqualityCmaintenanceThin Cloudflare Workers MCP server for navigating Bible Aquifer content, enabling Bible verse retrieval, content search, and entity profiling through MCP tools.2MIT
- 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
TDQS
Scored across 28 tools
Several tools have substantially overlapping purposes: search_keyword, search_semantic, search_topic, search_scripture_hybrid, and ask_holy_bible all cover similar ground, and get_strongs_definition, get_strongs_etymology, analyze_greek_hebrew_word, and get_interlinear_verse have unclear boundaries. Meta/infrastructure tools like extract_vector_context and get_model_recommendations add further confusion by sitting alongside core scripture tools.
The vast majority of tools follow a snake_case verb_noun pattern (get_verse, search_keyword, set_response_mode), and related groups use consistent prefixes. The main deviation is ask_holy_bible, which does not follow the get_/search_/set_ convention, but this is a minor inconsistency in an otherwise predictable naming scheme.
At 28 tools, the server exceeds the 25-tool threshold for a coherent set, and many tools are auxiliary or meta-oriented rather than core scripture functionality (get_p2p_swarm_status, get_model_recommendations, sanitize_scripture_markdown, set_show_metrics). This inflates the surface area significantly and makes the toolset feel broader than its core Bible-study purpose.
The core read-only Bible study domain is thoroughly covered: chapter/verse retrieval, full-text and semantic search, cross-references, original-language analysis, translations, commentary, thematic chains, and prophecy fulfillment are all present. Minor gaps exist, such as no direct multi-verse passage range retrieval and no canonical book/chapter listing, but agents can generally work around these.