Bible API MCP. Cross-reference scripture texts and versions instantly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Bible API allows you to search and retrieve scripture across hundreds of versions and languages. It gives your agent the capability to audit verses, list available Bible translations, or pull specific chapter content—all without manual lookups.
You can quickly cross-reference texts for deep theological research or verify quotes for publishing projects.
What your AI agents can do
Get bible chapter
Pulls the complete text content for a specific, defined chapter.
Get bible details
Retrieves metadata about a Bible version, like its official name or unique ID.
Get bible verse
Gets the text for one specific verse using its identifier.
Find specific keywords or phrases across multiple Bible versions to see all instances.
Get the full text for an entire chapter using its unique identifiers.
Pull the exact text of a single verse, saving you time in cross-referencing.
See all Bible versions and languages available for research.
Get a list of every book contained within a specific Bible version.
Retrieve detailed information, descriptions, and abbreviations for any known Bible translation.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Bible API with 6 Tools
This set of tools lets you pull specific chapters, verses, book lists, or run deep keyword searches across multiple Bible versions.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Bible API on Vinkius019d841dget bible chapter
Pulls the complete text content for a specific, defined chapter.
019d841dget bible details
Retrieves metadata about a Bible version, like its official name or unique ID.
019d841dget bible verse
Gets the text for one specific verse using its identifier.
019d841dlist bible books
Lists all book titles contained within a single, specified Bible version.
019d841dlist bibles
Shows every available Bible translation and language supported by the API.
019d841dsearch bible text
Searches for general keywords or phrases across an entire specified Bible version.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Bible API, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Bible API. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Manually checking biblical quotes used to be a nightmare.
Today, verifying a quote means jumping between multiple online Bible sites. You click on the first version, copy the text; then you open the second site and paste it in, just to check for subtle wording differences or translation variations. This process is slow, tedious, and easy to mess up.
With this MCP, your agent handles that comparison instantly. Instead of manual clicking, you ask it to search a phrase across multiple versions. You get the source texts pulled back in one clean response—no more tabs, no copy-pasting, just verified data.
Get Scripture Text and Version Details
The manual steps that vanish include checking if a specific translation even exists; you simply use `list_bibles`. You also skip the need to manually confirm book titles by running `list_bible_books` first.
Now, when your agent provides scripture data, it's immediately verifiable. It’s not just text; it's context with sources and version metadata attached.
What you can do with this MCP connector
Need to compare a verse's meaning across different historical translations? This MCP connects your agent directly to authoritative global scripture data. Instead of opening dozens of browser tabs and copy-pasting text, you ask your AI client to search keywords across multiple versions instantly. Your agent pulls back cleaned metadata, letting you see linguistic nuances side-by-side.
You can use it to list all available Bible translations in a given language or find the full contents of any chapter using unique identifiers. Whether you are writing a devotional series or conducting academic research, your agent acts as an instant biblical library. Once connected via Vinkius, this power is immediately available across any compatible AI client.
It's perfect for verifying quotes—you just ask for the text and the source version. It ensures that every piece of scripture you deal with is grounded in official, accurate translations.
019d841d-befa-7160-8061-0c5e3ae9fb46 
How Bible API MCP Works
- 1 First, subscribe to this MCP and enter your API.Bible Key into your Vinkius client.
- 2 Next, tell your agent the scope of the search—for example, 'Find all mentions of X in the Latin Vulgate.'
- 3 Your agent executes the query using the appropriate tool and returns structured data containing the verses and metadata.
The bottom line is you get a single, organized response from your AI client detailing the requested scripture passages.
Who Is Bible API MCP For?
Anyone who works with sacred texts or academic sources. Think theologians needing to compare translations, writers checking historical quotes, or educators building curriculum materials.
Compares the phrasing of a key verse across five different Bible versions to detect theological shifts.
Needs to audit all books within a specific canon version to understand its organizational structure for a paper.
Verifies the exact translation of a quote from an older source by querying the correct Bible ID and book list.
What Changes When You Connect
- Compare translations instantly. Use the
search_bible_texttool to see how a keyword like 'faith' appears in both Latin and Greek versions, side by side. - Build accurate curriculums. The
list_biblestool lets you know every language available before you even start writing lesson plans. - Cross-reference complex quotes. If you only have a verse citation but not the full text, use
get_bible_verseto pull the exact wording instantly. - Understand canon structure. The
list_bible_bookstool gives you the book titles for any version, helping you map out an entire religious work's organization. - Verify source material. Use
get_bible_detailswhen you need to know more about a specific translation—like its abbreviation or official name—before citing it.
Real-World Use Cases
Comparing Gospel Accounts
A scholar needs to compare the phrasing of Jesus's teachings across four different Greek translations. They ask their agent to use search_bible_text for a specific phrase, instantly receiving 4 distinct sets of results without visiting multiple academic websites.
Writing Comparative Devotionals
A devotional writer wants to base a lesson on 'love' but needs to ensure the quote is from the correct version. They use get_bible_verse with the specific book and chapter ID, getting the text and source metadata in one go.
Curriculum Development
An educator needs a list of all available texts for their program. They first run list_bibles, see that 12 languages are supported, then use list_bible_books to map the chapters in those languages.
Historical Verification
A journalist needs to verify an old quote. Instead of guessing which translation is correct, they run search_bible_text with keywords and let the agent find all potential sources, letting them pick the right one.
The Tradeoffs
Trying to manually check every version
A user opens 15 different Bible websites in a browser window and starts copying text chunks from different tabs, hoping for consistency.
→
Don't copy. Use your agent with search_bible_text. Just tell it the keyword and which versions you want to compare; the tool pulls all the necessary texts into one response.
Searching without context
A user types 'Tell me about love' into a general AI chat, and the agent gives vague philosophical answers with no source backing.
→
Be precise. Use get_bible_verse by specifying the exact book (e.g., John) and chapter/verse number (e.g., 3:16). This forces the tool to pull verifiable scripture text.
Assuming a translation exists
A user assumes that because they know a language, there must be an available version and tries to query it directly.
→
First, run list_bibles. This guarantees the translation actually exists in the catalog before you waste time querying for non-existent data.
When It Fits, When It Doesn't
Use this MCP if your primary need is structured comparison or cross-referencing of source texts. If you are building a tool that requires knowing every available book, start with list_bibles then follow up with list_bible_books. If you know the exact chapter and verse number, use get_bible_chapter or get_bible_verse for maximum efficiency. Don't bother using this if your query is purely interpretive; if you just need an opinion on a topic, use general knowledge tools instead. Only bring in this MCP when verifiable scripture source data is non-negotiable.
Common Questions About Bible API MCP
How do I find out what translations are available using the Bible API? +
Run list_bibles. This tool queries the system and provides a complete list of all supported languages and Bible versions, giving you a full scope of options immediately.
Should I use get_bible_chapter or search_bible_text? +
If you know the exact chapter (e.g., Genesis 1), use get_bible_chapter. If you only know a keyword and want to see every mention across the book, then run search_bible_text.
How do I find out what books are in a Bible version? +
Use list_bible_books. You must first specify which Bible version you want to inspect; the tool then returns all the contained book titles for that specific canon.
What is the best way to find a single verse? +
The most direct method is using get_bible_verse, as long as you have the unique identifiers for the verse. This avoids ambiguity inherent in general searching.
How do I get started with my API key when running `list_bibles`? +
You must pass your unique API Key in the request headers. The first time you call any tool, always authenticate with that key; it’s required for full access to the catalog.
What is the best way to check metadata for a specific version using `get_bible_details`? +
It returns comprehensive details about the entire translation, not just verses. Use this function before running searches; it confirms if your given Bible ID is valid and provides its official name.
If my query fails while using `search_bible_text`, what should I do? +
Check the error code provided in the response body. If you hit a rate limit, wait 60 seconds before trying again. Alternatively, simplify your search phrase or narrow down the Bible version.
When should I use `get_bible_chapter` instead of keyword searching with `search_bible_text`? +
Use this when you need all the text for a known chapter, regardless of what keywords appear in it. This gives you one structured content block rather than scattered search results.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.