
Bible Study
io.github.mctx-aiPublished by GitHub account mctx-aiv1.11.3Updated Oct 24, 2026
Study the Bible in its original languages, trace themes across both testaments, and compare five tra
Overview
A remote MCP server for Bible study: original-language study, tracing themes across both testaments, and comparing five translations.
- What you can do
- The registry description is brief and no tools are listed, so capabilities are described at a high level. The assistant can support study of the Bible in its original languages. It can trace themes across both testaments. It can compare five translations.
- When to use it
- Useful when you want an assistant to help with Bible study, original-language word work, thematic tracing across the Old and New Testaments, or side-by-side translation comparison.
- Requirements
- Connects to a remote endpoint over SSE; no local package, environment variables or headers are declared. No authentication is declared.
Installation
In SourceWeft
- Open Bible Study in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.mctx-ai%2Fbible-study/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"bible-study": {
"type": "sse",
"url": "https://bible-study.mctx.ai/v1.11.3"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.11.3LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.