Skip to main content
Glama

Bible MCP 服务器

一个 MCP(模型上下文协议)服务器,让 AI 助手能够从 MyBible 格式的 SQLite 数据库中获取圣经经文、段落和章节。

功能

  • list_bibles — 列出所有已安装的圣经译本

  • list_books — 列出某个译本中的所有书卷

  • get_passage — 获取单节经文或经文范围(例如:约翰福音 3:16,罗马书 8:1-3)

  • get_chapter — 获取包含章节标题的完整章节

Related MCP server: bible-mcp

设置

安装依赖

npm install

添加圣经译本

将 MyBible 格式的 .SQLite3 文件放入 Bibles/ 目录中,每个译本一个文件夹:

Bibles/
├── NIV'11/
│   ├── NIV'11.SQLite3
│   └── NIV'11.commentaries.SQLite3
├── KJV/
│   └── KJV.SQLite3
└── ...

每个子文件夹必须至少包含一个 *.SQLite3 文件(主圣经数据库)。注释数据库(*.commentaries.SQLite3)是可选的。文件夹名称将成为工具调用中使用的译本 ID。

配置你的 AI 客户端

添加到你的 MCP 客户端配置中:

{
  "mcpServers": {
    "bible": {
      "command": "node",
      "args": ["path/to/BibleMCP/dist/index.js"]
    }
  }
}

用于开发:

{
  "mcpServers": {
    "bible": {
      "command": "npx",
      "args": ["tsx", "path/to/BibleMCP/src/index.ts"]
    }
  }
}

配置

环境变量

默认值

描述

BIBLES_DIR

./Bibles

包含圣经译本文件夹的目录路径

开发

npm run build      # Compile TypeScript to dist/
npm run dev        # Run server in dev mode (tsx)
npm test           # Run all tests
npm run test:watch # Run tests in watch mode
npm run typecheck  # Type-check without compiling

MyBible 格式

此服务器读取标准的 MyBible SQLite 模式:

  • info 表 — 元数据(描述、语言)

  • books 表 — 书卷编号、短/长名称(66 卷书,编号 10–730)

  • verses 表 — book_number, chapter, verse, text(文本可能包含 HTML 标记)

  • stories 表 — 章节标题 / 分段标题

  • introductions 表 — 书卷介绍

经文文本以干净的纯文本形式返回,所有 HTML 标记均被剥离。

许可证

此服务器代码根据 MIT 许可证授权。请参阅 LICENSE。

Bibles/ 目录中的圣经译本模块不受此许可证覆盖——它们受各自版权保护,且不随此仓库分发。

Available Tools

4 tools
get_chapterA

Get an entire chapter of the Bible with all verses and section titles.

Inputs: book (required), chapter (required), translation (required).

get_passageA

Get a single Bible verse or a range of verses by book, chapter, and verse number(s).

Inputs: book (required), verse (required), chapter (required), translation (required), +1 more.

list_biblesA

List all available Bible translations installed in the Bibles directory.

Inputs: no named parameters.

list_booksB

List all books in a specific Bible translation.

Inputs: translation (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct purpose: browsing translations, listing books, retrieving a specific passage, or fetching a full chapter. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_bibles, list_books, get_passage, get_chapter), making the set predictable and easy to navigate.

    Tool Count4/5

    With 4 tools, the server feels well-scoped for its purpose. While minimal, it covers browsing and reading operations without unnecessary bloat. One or two additional tools (e.g., search) could be expected but not required.

    Completeness3/5

    The server covers basic lookup workflows (list translations, list books, retrieve passages/chapters), but lacks search, cross-reference, or note capabilities. Users can successfully read verses but may encounter dead ends for discovery beyond hierarchical listing.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to retrieve Bible passages from multiple translations (ESV, NIV, KJV, NASB, NKJV, NLT, AMP, MSG). Supports querying single or multiple passages and provides both MCP protocol integration and REST API endpoints.
      1
      13
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to look up Bible verses, search across translations, and compare different versions locally without API keys.
      1
      -