KJV Verse MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_passageA | Look up King James Version (1769, public domain) text by reference. Accepts single verses ('John 3:16'), ranges ('1 Cor 13:4-7', 'Gen 1:31-2:3'), whole chapters ('Psalm 23'), and several references separated by ';'. Common abbreviations work (Jn, Ps, 1 Cor, Rev). Max 200 verses per call. |
| search_kjvA | Find KJV verses containing a word or exact phrase (case-insensitive). Optional book filter. Returns total match count and up to |
| verse_of_the_dayA | Deterministic verse for a date (same date always returns the same verse). pool='popular' picks from well-known encouraging verses; pool='all' picks from all 31,102 verses. |
| list_booksA | The 66 books of the KJV protocanon with chapter counts and testament. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct access pattern: reference lookup (get_passage), keyword/phrase search (search_kjv), deterministic daily verse (verse_of_the_day), and canonical book metadata (list_books). An agent can pick the right tool from the name alone; the only near-overlap (passage vs. search) is actually a clean reference-vs-content split.
All names are lowercase snake_case with a verb-first shape (get_, search_, list_) except verse_of_the_day, which is a domain-standard noun phrase but still readable and unambiguous. No mixed casing or vague verbs, so the surface feels uniform.
Four tools is a tight, well-scoped surface for a single-translation scripture server — each tool covers a genuinely different query pattern and none is redundant. Nothing feels padded or conspicuously absent at this scale.
Reference lookup, text search, daily verse, and book listing cover the main workflows for a KJV reader, including ranges and multi-reference lookups. Minor gaps remain: no random-verse tool, no topical/thematic index beyond raw text search, and the 200-verse cap is undocumented as a fallback behavior (e.g., how to page a very long book).