BibleMCP
Production-ready MCP server that lets LLMs explore, analyze, and reason over the Bible using local ChromaDB stores and Mistral embeddings.
README
BibleMCP
Production-ready MCP server that lets LLMs explore, analyze, and reason over the Bible using local ChromaDB stores and Mistral embeddings.
Supported translations
Each translation is stored in its own isolated local Chroma directory (never mixed):
| Alias | helloao ID | Display name |
|---|---|---|
BSB |
BSB |
Berean Standard Bible |
ASV |
eng_asv |
American Standard Version (1901) |
BBE |
eng_bbe |
Bible in Basic English |
KJAV |
eng_kjv |
King James (Authorized) Version |
Architecture
MCP client (Cursor / Claude Desktop)
│ stdio
▼
biblemcp/server.py → tools → services → storage (Chroma per translation)
↓
helloao API (ingest)
Mistral API (embeddings)
Setup
1. Install
uv sync --extra dev
This creates .venv, installs the project in editable mode, and adds dev dependencies (pytest).
Note:
onnxruntimeis pinned to<=1.19.2because newer releases dropped Intel Mac (x86_64) wheels. BibleMCP uses Mistral for embeddings, not Chroma's built-in ONNX embedder — this pin only satisfies ChromaDB's install requirement.
Run project commands through uv without activating the venv:
uv run biblemcp ingest --help
uv run pytest
uv run python -m biblemcp.server
2. Configure environment
Copy .env.example to .env and set your Mistral key:
cp .env.example .env
Required for ingest and semantic search:
MISTRAL_API_KEY
Optional:
BIBLEMCP_DATA_DIR(default./data/chroma)BIBLEMCP_DEFAULT_TRANSLATION(defaultBSB)
3. Ingest Bible text
Before semantic tools work, populate the local databases:
uv run biblemcp ingest --translation BSB
uv run biblemcp ingest --all
This fetches text from helloao, embeds verses with mistral-embed, and upserts into data/chroma/{bsb,asv,bbe,kjav}/.
Re-running ingest is safe (upsert).
MCP client configuration
Cursor
Add to your MCP settings:
{
"mcpServers": {
"biblemcp": {
"command": "uv",
"args": ["--directory", "/absolute/path/to/BibleMCP", "run", "python", "-m", "biblemcp.server"],
"env": {
"MISTRAL_API_KEY": "your_key",
"BIBLEMCP_DATA_DIR": "/absolute/path/to/BibleMCP/data/chroma"
}
}
}
}
Claude Desktop
{
"mcpServers": {
"biblemcp": {
"command": "uv",
"args": ["--directory", "/absolute/path/to/BibleMCP", "run", "python", "-m", "biblemcp.server"],
"env": {
"MISTRAL_API_KEY": "your_key",
"BIBLEMCP_DATA_DIR": "/absolute/path/to/BibleMCP/data/chroma"
}
}
}
}
Use absolute paths for --directory and BIBLEMCP_DATA_DIR. If uv is not on your PATH for the MCP host, use the full path to the uv binary.
Screenshots
Configured in Cursor
Once connected, biblemcp shows as active with all 10 tools available:

In action
Ask for verses on a theme — the agent searches and fetches passages through the MCP tools:


The 10 tools
| Tool | What it does |
|---|---|
search_verse |
Semantic keyword/phrase search |
get_verse |
Exact single-verse lookup |
get_passage |
Exact verse range within a chapter |
cross_reference |
Semantic neighbors for a reference (not curated TSK) |
topic_lookup |
Semantic topic search |
original_language_lookup |
Semantic search framed by a term (not Strong's) |
character_profile |
Relevant verses about a character (no biography DB) |
timeline_event_lookup |
Relevant verses for an event (no date database) |
summarize_passage |
Chapter text + instructions for the host LLM to summarize |
theological_analysis |
Primary + related passages + question for host LLM analysis |
All tools accept an optional translation field (BSB, ASV, BBE, KJAV).
Development
Run tests:
uv run pytest
Run the server locally:
uv run python -m biblemcp.server
CLI help:
uv run biblemcp ingest --help
Project layout
src/biblemcp/
bible/ # book aliases, reference parsing
clients/ # helloao + Mistral embeddings
models/ # Pydantic types
services/ # ingest, retrieval, search, context
storage/ # per-translation Chroma store
tools/ # MCP tool schemas, handlers, registry
server.py # FastMCP entrypoint
cli.py # ingest CLI
tests/ # unit, service, and tool tests
data/chroma/ # local vector stores (gitignored)
License
Apache-2.0 — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。