GetBible MCP / Package 2.0 documentation
One connection. All GetBible APIs.
Scripture, query and search v2/v3; dictionaries, commentaries and public topic bookmarks v1. Available through hosted Streamable HTTP and local stdio.
Public access requires no account or API key. Every operation is read-only, including search POST.
Protocol endpoint: /mcp, at the URL supplied by the consuming application.
Scripture tools default to upstream v3, with v2 available explicitly. This documentation covers MCP package 2.0 and every listed upstream API version.
Local command: getbible-mcp --transport stdio
Documentation
Compact entry point for AI systems. manifest.json
Transports, tools, resources, and canonical URLs. API guide
All services, versions, data structures and integration patterns. Public use policy
Open access, translation rights, and synchronization agreement. Cache policy
Mandatory revalidation and invalidation rules. Examples
Representative tool selections and calls. OpenAPI catalog
All nine upstream documents and exact included snapshots. Tool catalog
Static overview of the live MCP tools.
Choose a connection
Connect a Python, JavaScript or PHP MCP client to an application's published MCP URL using Streamable HTTP. An ordinary application can also call the existing REST APIs directly.
To run the MCP server locally, install the Python package with pipx install getbible-mcp and configure your AI client to launch getbible-mcp --transport stdio.
This project ships one Python server package. It does not require separate npm or Composer server implementations.
Required cache integrity
Never retain upstream data beyond 30 days without refreshing it. Honor shorter HTTP freshness and no-store; validate published checksums and replace changed records atomically. The MCP keeps no persistent result cache, and query/search results are non-cacheable by default.
Preserve rights and provenance from translation catalogs and study-module metadata. Read the full cache and usage policies before building an offline integration.