
Wraps the Bible API in a streamable HTTP endpoint, giving Claude direct access to biblical text without authentication. Part of the Pipeworx gateway ecosystem, which aggregates 673+ data sources behind a single MCP interface. You can wire it up standalone for scripture lookups or use the full Pipeworx gateway and query it conversationally through ask_pipeworx. The source documentation doesn't list specific tools, but given the API wrapper nature, expect verse retrieval, passage search, and translation access. Useful if you're building study tools, reference assistants, or anything that needs programmatic access to biblical content without managing API keys.
Bible MCP — wraps the Bible API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_verse | Get a specific Bible verse or range by reference (e.g., "john 3:16", "romans 8:28", "psalm 23:1-6"). Returns verse text in World English Bible translation. |
get_passage | Get a Bible passage in your choice of translation (KJV, WEB, OEB, BBE, Cherokee, DRA, and more). Returns full text with reference and translation metadata. |
random_verse | Fetch a random Bible verse from the World English Bible (WEB) translation. Returns the reference, full verse text, translation ID, and per-verse breakdown with book, chapter, and verse number. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bible": {
"url": "https://gateway.pipeworx.io/bible/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/bible/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Bible data" })
The gateway picks the right tool and fills the arguments automatically.
MIT