FLOGVIT.bible MCP server
Commit Nov 14, 2026Lets an AI assistant read and search the Bible, including Hebrew and Greek source texts, study notes, and historical timelines.
Also known as flogvit/bible.flogvit.com, bible
- Stars
- 0
- Tools
- 17
- Downloads, 30 days
- —
- Latest version
- 1.1.0
- Last commit
- Nov 14, 2026
- License
- —
What is FLOGVIT.bible MCP?
FLOGVIT.bible lets an AI assistant read and search the Bible, including Hebrew and Greek source texts, study notes, and historical timelines. It exposes 17 tools, such as get_passage, search_bible, get_original_text.
Summary generated from the project's README
About FLOGVIT.bible MCP server
FLOGVIT.bible provides an interface for AI assistants to interact with extensive biblical resources. It allows users to access various translations including OSNB, OSNN, and OSEN, alongside original Hebrew and Greek source texts. The server is designed for researchers and students who need deep linguistic insights, historical context, or specific study notes.
This is a remote server accessible via streamable HTTP, requiring no account or API keys to use. Developers can connect it to clients like Claude Desktop, ChatGPT, Cursor, or VS Code by providing the specific URL. It supports complex queries involving verse mappings across 1158 different numbering systems, ensuring accuracy across various editions.
Beyond simple reading, the server offers specialized tools for studying people, topics, and prophecies. It can generate timelines, provide gospel parallels, and even retrieve specific Church of Norway readings. Every response includes links back to the original source material for verification.
What you can do with it
- 1Analyze original biblical languagesAsk the assistant to retrieve the Greek or Hebrew text of a specific passage with word-by-word explanations.
- 2Conduct comparative scripture studiesRequest to see multiple Bible versions side by side for a specific verse or passage.
- 3Explore historical and thematic contextHave the AI summarize a chapter including its key themes, people, and historical timeline.
Written from the project's README. Every use case is checked against a quote from it.
How to install FLOGVIT.bible MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall FLOGVIT.bible MCP in Claude Code
$ claude mcp add --transport http bible https://mcp.bible.flogvit.com/mcpInstall FLOGVIT.bible MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"bible": {
"url": "https://mcp.bible.flogvit.com/mcp"
}
}
}Install FLOGVIT.bible MCP in VS Code
.vscode/mcp.json
{
"servers": {
"bible": {
"type": "http",
"url": "https://mcp.bible.flogvit.com/mcp"
}
}
}Install FLOGVIT.bible MCP in VS Code CLI
$ code --add-mcp '{"name":"bible","type":"http","url":"https://mcp.bible.flogvit.com/mcp"}'Install FLOGVIT.bible MCP in Codex
$ codex mcp add bible --url https://mcp.bible.flogvit.com/mcpInstall FLOGVIT.bible MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.bible] url = "https://mcp.bible.flogvit.com/mcp"
Install FLOGVIT.bible MCP in Gemini CLI
$ gemini mcp add -s user --transport http bible https://mcp.bible.flogvit.com/mcpInstall FLOGVIT.bible MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"bible": {
"url": "https://mcp.bible.flogvit.com/mcp",
"type": "http"
}
}
}FLOGVIT.bible MCP tools 17
Detected from the READMEget_passagesearch_bibleget_original_textsearch_original_wordget_cross_referencesget_chapter_studyget_book_overviewget_daily_versecheck_referencesget_church_year_readingsget_timelineget_prophecies
| get_passage | — | |
| search_bible | — | |
| get_original_text | — | |
| search_original_word | — | |
| get_cross_references | — | |
| get_chapter_study | — | |
| get_book_overview | — | |
| get_daily_verse | — | |
| check_references | — | |
| get_church_year_readings | — | |
| get_timeline | — | |
| get_prophecies | — |
Show all 17 toolsShow fewer tools
get_storyget_numberget_gospel_parallelslist_editionslist_verse_mappings
| get_story | — | |
| get_number | — | |
| get_gospel_parallels | — | |
| list_editions | — | |
| list_verse_mappings | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableflogvit/bible.flogvit.com is public and reachablegithub.com/flogvit/bible.flogvit.com ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-13github.com/flogvit/bible.flogvit.com ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 1172 msPass
README
View on GitHubbible.flogvit.com MCP server
Lets an AI assistant read and search the Bible on bible.flogvit.com: the open OSNB, OSNN and OSEN translations, the Hebrew and Greek source texts, and the site's study material. Every answer links back to the page it came from.
Address: https://mcp.bible.flogvit.com/mcp — Streamable HTTP, no account,
no key.
Connect an assistant
The full guide, for every client and in all eight languages, is
bible.flogvit.com/en/mcp. A browser that
opens https://mcp.bible.flogvit.com/ gets the short version of it. Both are
rendered from ../src/lib/mcp-info.ts and the mcp.* keys in
../src/lib/dictionaries-mcp.ts, and test/landing.test.ts holds the tool
list there against tools/list.
Claude (desktop app and claude.ai): Settings → Connectors → Add custom connector. Paste the address, leave authentication empty.
ChatGPT: turn on developer mode under Settings → Apps & Connectors, then create a connector with the address and no authentication.
Claude Code:
claude mcp add --transport http flogvit-bible https://mcp.bible.flogvit.com/mcp
Cursor (~/.cursor/mcp.json):
{ "mcpServers": { "flogvit-bible": { "url": "https://mcp.bible.flogvit.com/mcp" } } }
VS Code (.vscode/mcp.json):
{ "servers": { "flogvit-bible": { "type": "http", "url": "https://mcp.bible.flogvit.com/mcp" } } }
Then ask as you normally would — "what does John 3:16 say in the Greek?", "where does the Bible talk about forgiveness?", "who was Tamar?". The assistant picks the tools itself.
Without MCP — in a terminal, a script, or an agent that reads skills — the
same tools are the command line client flogvit-bible, with a skill and a
Claude Code plugin around it: ../cli/README.md.
The tools
| Tool | What it answers |
|---|---|
get_passage |
One or more passages, side by side in up to five editions, optionally with the translators' notes |
search_bible |
Verses containing all the given words, in one edition, optionally one book or testament |
get_original_text |
The Hebrew or Greek of a passage, word by word with explanations (in Norwegian) |
search_original_word |
Every verse where a Hebrew or Greek word occurs |
get_cross_references |
Related passages for each verse |
get_chapter_study |
Summary, context, key words, people, themes, stories, prophecies, parallels and timeline for a chapter |
get_book_overview |
An introduction to a book |
search_people, get_person |
People of the Bible, their family and key events |
search_topics, get_topic |
Stories, themes, prophecies and gospel parallels |
get_daily_verse |
Today's verse |
check_references |
Every Bible reference in a piece of text — line, column, the verses, and a problem for one that does not exist |
get_church_year_readings |
The Church of Norway's readings for a Sunday or feast day, by date or by the day's name (Norwegian, or English for the major feasts), optionally quoted |
get_timeline |
Timeline events for a period, a span of years, or a person or place named in them; the Bible's timeline or the world's alongside it |
get_prophecies |
Prophecies made or fulfilled in a passage, or in a category, with their fulfilment and optionally both texts |
get_story |
A Bible story by name, where it is told, and the text |
get_number |
What a number means in the Bible and where it occurs; with no number, every number that has an entry |
get_gospel_parallels |
The gospel parallels that cover a passage, every Gospel's passage side by side, optionally quoted one after the other |
list_editions |
The editions and their licences |
list_verse_mappings |
The 1158 verse numberings (KVN mappings) the mapping argument takes, found by edition name or language |
References are read in English and Norwegian style alike — John 3:16-18,
Joh 3,16.18, 1 Cor 13:4-7, Gen 1:1-2:3, several separated by ; — and
book names in all eight site languages, plus the Norwegian letter names
(«Romerbrevet»).
Verse numbering. Every tool that takes or gives a verse reference has a
mapping argument: an id from list_verse_mappings (english_kj,
dnb2024_nb, …) or a short name (kjv, dnb2024). A reference is read in
that numbering and the answer is numbered in it, so "Mal 4:5" with kjv is
osnb's Malachi 3:23. The tools do no remapping of their own: a reference goes
through mapChapter(), as /api/chapter?mapping= does, and an osnb address
comes out through osnbToMapping(), the cross mapping /api/mappings/kvn/:id
builds its verseMap from (src/lib/verse-mapper.ts). Unlike the API, which
only knows the 13 named numberings, the MCP takes any of the 1158 mapping
files. That is why the caches in verse-mapper.ts have a cap (32).
Quoted Bible text carries its source line. The translations are CC BY 4.0, and the attribution has to follow the text wherever the assistant puts it.
Releasing a new version
Every change a client can see — a tool added or removed, an argument, a description — is a release, and the directories that list the server have to follow it. They do not all get their data the same way:
| Directory | Where its data comes from | What a release needs |
|---|---|---|
| MCP Registry | server.json, published by us |
publish the new version |
| mcptry.com | name, description and version copied from the registry every 30 minutes; the tool list from its own scheduled tools/list check of the live server |
nothing to submit — it follows the registry and the server |
| Glama, PulseMCP | the registry | nothing |
| mcpservers.org | a form submitted by hand once; the page text is a copy of websiteUrl (https://bible.flogvit.com/en/mcp) |
press Request update on the listing (no login, one click, sent at once) after the site is out |
- In the PR that changes the tools, raise the version —
SERVER_VERSIONinsrc/server.tsandversioninserver.json, whichtest/landing.test.tsholds equal. The registry never accepts the same version twice. A new tool or argument is a minor version (1.1.0 → 1.2.0); a removed tool or argument a major one. Changedescriptioninserver.jsontoo if what the server does has changed: it is what every directory shows, and at most 100 characters. - Merge. The orchestra's deployer rolls out bibel and
bibel-mcpfrom the same commit. - After the rollout, publish to the registry:
It refuses while the live server still runs another version or other tools, so it cannot announce what is not out. It logs in withcd mcp && bun --env-file=../.env scripts/listings.ts publishgh auth token(gh must be logged in asflogvit; the namespace isio.github.flogvit) and needs nothing installed. - Press Request update on https://mcpservers.org/servers/bible-flogvit-com-en-mcp. It is anonymous and takes effect at once, so press it only after the site is out — pressed earlier, they re-read the old page. Their review takes up to two weeks. The short description there is the one submitted in the form; whether Request update refreshes it too is not known. To change it, email contact@mcpservers.org.
- Check, about 30 minutes later:
Every line should saycd mcp && bun --env-file=../.env scripts/listings.ts checkok.mcptry toolsfollows mcptry's own schedule and can lag; "Connect live" on its page refreshes it. mcpservers.org sits behind a Cloudflare check and cannot be read by the script: open the page and see that the tool list matches.
Where it is listed, and how to take it down
The namespace is GitHub (io.github.flogvit/…), not DNS (com.flogvit/…):
flogvit.com's DNS is edited by hand at Domeneshop, and a GitHub login is
something a script can do.
| Where | Status (2026-10-26) | Take it down |
|---|---|---|
| MCP Registry | published; the current version is what scripts/listings.ts check reports |
mcp-publisher status --status deleted --all-versions --message "<why>" io.github.flogvit/bible (brew install mcp-publisher, mcp-publisher login github --token "$(gh auth token)") — hides it; --status active brings it back. The registry never deletes metadata. |
| Glama | listed, read from the registry | goes with the registry entry |
| PulseMCP | reads the registry by itself (its own form is closed) | goes with the registry entry |
| mcptry.com | listed, read from the registry; checks the live server on a schedule | goes with the registry entry |
| mcp.so | submitted: chatmcp/mcpso#6153 | close the issue and ask there |
| mcpservers.org | listed (submitted through the free form) | email contact@mcpservers.org |
| awesome-remote-mcp-servers | PR punkpeye/awesome-remote-mcp-servers#2991, from the fork flogvit/awesome-remote-mcp-servers |
close the PR; once merged, a PR removing the three lines. Remote-only servers go in this list, not in awesome-mcp-servers — its CONTRIBUTING says so. |
| Smithery | not submitted — needs a login as flogvit | delete the server in Smithery's settings |
| cursor.directory | not submitted — needs a login | remove it there |
| Claude's connector directory | not submitted — only a Pro/Max/Team account can submit, at claude.ai/directory/manage → Submit new → MCP connector |
remove the listing in the same portal |
The three that are not submitted need nothing but the login: the address, the description and every field Anthropic's form asks for (one-liner, description, documentation and privacy URLs, support contact, use cases, example prompts) are written out in issue #157.
What each one got, and when, is in issue #157 on GitHub.
The guide page is /mcp in ../src/routes/pages/mcp.tsx. Removing it means
removing the route, the footer link in ../src/views/layout.tsx, /mcp in
../src/lib/sitemap-paths.ts and test/pages.ts, and the pointer in
llms.txt (../src/routes/seo.ts) — then deploying bibel.
Run it locally
Needs the local database the site uses (../.env, DB_PORT=3326).
cd mcp
bun install
bun run dev # http://localhost:8080/mcp
Try it with the MCP Inspector (npx @modelcontextprotocol/inspector, transport
Streamable HTTP, URL http://localhost:8080/mcp), or by hand:
curl -s -X POST localhost:8080/mcp \
-H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_passage","arguments":{"reference":"John 3:16"}}}'
GET /healthz checks that the database user can read every content table and
reads John 3:16: 200 with the verse, or 503 with the reason — a missing grant is
named.
Tests
cd mcp && bun run test && bun run typecheck
test/server.test.ts calls every tool over HTTP against the local database and
checks that each answer links only to localised pages on bible.flogvit.com (or
the sources the licence names) and never shows the site's [ref:…] markup.
test/grants.test.ts creates a local MySQL user with exactly the grants the
server gets in production, runs every tool as that user, and checks that the
user tables refuse it — a tool that needs a table outside the grants fails
there — and that /healthz names a table whose grant is revoked. test/books.test.ts checks that every book name and abbreviation the
site shows, in every language, finds its own book. test/find-references.test.ts
finds every book by every name inside a sentence, and its last verse as the
last. test/cli.test.ts runs the command line client (../cli/) as its own
program, with node and bun, against a listening server.
test/lookups.test.ts holds the six direct lookups to every row of their
tables. test/mapping.test.ts holds mapping to mapChapter() over every
chapter where the King James numbering differs from osnb, plus Malachi 4,
cross-references in and out, and check_references.
test/tool-quality.test.ts reads tools/list and fails on a tool without a
title, a description or all four annotation hints, an argument or output field
without a description, an optional argument that does not say its default, or
an allowed value its description does not name — what a client, and mcptry.com's
Tool quality score, read before calling anything.
bibel's own bun test in the repo root does not run these (bunfig.toml):
this package has its own dependencies.
How it is built
- Its own package, its own image.
@modelcontextprotocol/sdkand its dependencies live here and never reach the site's image. The image is built from the repo root (docker build -f mcp/Dockerfile .) because the server reads the database through the site's own getters insrc/lib/— an answer here is the page there. - The image carries the vendored
@free-bible/kvn(kvn-package/, 109 MB of mapping files), for the verse numberings. Stage it first —bun run oppsettin bibel, which bibel's deploy does before it builds — or the build stops at theCOPY.test/image.test.tsfollows every import fromsrc/index.tsand fails when the image would lack a file or a package; the tests themselves cannot see it, since they resolve through bibel's ownnode_modules. - Its own database user, read-only on content.
src/grants.tsgrants SELECT on the tables the import owns (CONTENT_TABLES) and nothing else, so users' notes, manuscripts and shares are out of reach. - Stateless. One MCP server per request; any request can land on any process.
- A global cap, not a per-IP one. Claude and ChatGPT call connectors from
their own servers, so one IP is many users. Over the cap the server answers
503 with
Retry-Afterinstead of queueing without end. The command line client is the one caller it can tell apart, and the one most likely to come in a loop, so it may hold onlyMCP_MAX_CONCURRENT_CLIof the slots.
Configuration
| Variable | Default | |
|---|---|---|
PORT |
8080 | |
DB_HOST, DB_PORT, DB_USER, DB_PASSWORD, DB_NAME |
as the site | the database user should have only grantStatements() |
DB_TLS |
off | 1 connects over TLS — for a database user that is refused in plain text |
DB_POOL_MAX |
5 | |
MCP_MAX_CONCURRENT |
4 | requests served at once |
MCP_MAX_CONCURRENT_CLI |
2 | of those, how many the command line client may hold (User-Agent: flogvit-bible-cli/…) |
bun scripts/grants.ts <database> prints the GRANT statements for the
database user. They are derived from CONTENT_TABLES, but applied only when
someone runs them: when the import gets a new content table, run them again as
the database admin. Until then /healthz answers 503 and names the table.
FLOGVIT.bible MCP questions
How do I add FLOGVIT.bible MCP to Claude Code?
Run claude mcp add --transport http bible https://mcp.bible.flogvit.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add FLOGVIT.bible MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does FLOGVIT.bible MCP provide?
It exposes 17 tools, including get_passage, search_bible, get_original_text, search_original_word, get_cross_references.
How do I connect this to Claude?
Go to Settings → Connectors → Add custom connector, paste the address, and leave authentication empty.
Does this server require an API key?
No, the server uses streamable HTTP and requires no account or key.
Can I search for specific Hebrew or Greek words?
Yes, you can use the search_original_word tool to find every verse where a specific Hebrew or Greek word occurs.
What Bible translations are available?
The server provides access to the open OSNB, OSNN, and OSEN translations.