Skip to main content
Glama
justinsovine

bible

by justinsovine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to bible

No user-submitted related servers found.

    Related Servers

    • SolaGuard MCP Server

      jissac
      A
      license
      A
      quality
      D
      maintenance
      Provides comprehensive Biblical research tools including scripture lookup, interlinear Greek/Hebrew data, and Strong's concordance within a Protestant theological framework. It enables AI applications to perform full-text biblical searches, topical studies, and cross-referencing using authoritative theological data.
      4
      MIT

    • biblical-atlas-mcp

      GeiserX
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with nine read-only tools to search and explore Bible people, places, events, reigns, letters, journeys and passages, including relationships, timelines, geography, Bible references, and source-linked atlas records.
      78 npm
      1
      MIT

    • kjv-bible-mcp-server

      saficky98
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude.ai to access and retrieve Bible verses, passages, chapters, and lists of books or translations from public domain versions like KJV, using the free bible-api.com.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly distinct resources: passage (text), word (Strong's/lemma study), commentary, church_fathers, translation_notes, xrefs, dictionary, and search each have a distinct corpus or action. There is mild overlap between word and dictionary (both return lexicon entries for a Strong's number/lemma) and between search and dictionary (dictionary falls back to full-text search), plus four tools that all answer 'what does X say about this passage' — differentiated only by corpus, which the descriptions do clarify.

    Naming Consistency4/5

    Names follow a consistent resource-oriented convention (passage, word, search, commentary, dictionary, xrefs, sources, schema), with the *_modules suffix used predictably for commentary_modules and dictionary_modules. Minor deviations are check_quote (verb_noun) and the sql/schema escape-hatch pair, but everything remains readable and predictable.

    Tool Count5/5

    14 tools sits squarely in the well-scoped 3-15 range for a domain as broad as Bible study. Each tool covers a distinct corpus or operation, and the schema/sql pair serves as a deliberate escape hatch rather than filler.

    Completeness4/5

    Coverage is strong: text, original language, interlinear morphology, word studies, full-text search, three commentary corpora, dictionaries, cross-references, translation notes, provenance (sources), and a SQL fallback for anything uncovered. Minor gaps: passage appears to expose only the BSB translation even though sources tracks multiple versions, and grammatical/morphology search is only reachable through raw sql rather than a first-class tool.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources