Theological Research MCP Server — PostgreSQL-backed Bible study with 140+ translations, lexicons, commentaries, and extra-biblical texts
Theosis MCP demonstrates solid tool design with consistent naming (verb_noun pattern), comprehensive descriptions (avg 180 chars), and proper JSON Schema with type definitions. All 12 tools have ToolAnnotations (readOnlyHint=true). However, several tools lack required parameter descriptions, output schemas are undocumented, and error handling guidance is absent. Tool #12 (get_study_notes) has an empty input schema and minimal description, dragging the average. Parameter descriptions are inconsistent: lookup_verse and search_lexicon are well-documented, but get_cross_references omits 'reference' description, and lookup_name lacks 'type' description. No pagination guidance despite tools returning lists (search_by_strongs, find_similar_passages). Missing output schema documentation across all tools.
Explore biblical events with participants and locations. 79 major events from Creation to the Early Church, in chronological order. Each event shows participants and locations.
Explore biblical genealogies — ancestors, descendants, or siblings of a person.
Explore biblical places — search by name, filter by type, or list all. 110 locations with coordinates and verse references. Types include city, mountain, river, sea, region, valley, and site.
Find semantically similar passages using AI embeddings (pgvector). Discovers thematic connections beyond explicit cross-references. Uses vector similarity to find passages with related meaning, imagery, or theological concepts. IMPORTANT: Semantic similarity does NOT equal theological connection. Always verify context, genre, and authorial intent before using parallels in interpretation.
Find passages connected to a verse through curated cross-references. Sources include Harrison/Romhild curated dataset, Treasury of Scripture Knowledge, and thematic chains. Use before drawing theological conclusions from a single verse.
Tool #12 (get_study_notes) has empty input schema, trivial description ('Study Notes'), and no documentation of what it returns or when to use it. Violates pattern:tool-description and pattern:tool.
Output schemas are undocumented for all 12 tools. LLMs cannot plan downstream calls or extract required fields without knowing return structure. Violates pattern:tool and mxe:response-field-naming.
Parameter descriptions missing or incomplete: get_cross_references omits 'reference' description; lookup_name omits 'type' description; explore_genealogy omits 'direction' description. Violates pattern:tool-description.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | <=2025-11-25 | v2 |
Study Notes
Look up biblical persons, places, or things with relationship data. Returns family connections (parents, siblings, spouse, children), geographical info, and biblical significance. Database contains 4,000+ persons and 1,000+ places.
Get a Bible verse with original Greek/Hebrew text and word-by-word breakdown. ALWAYS use this when any Bible verse is mentioned. Returns: - English text - Original Greek/Hebrew (when available) - Word-by-word morphology with Strong's numbers - Genre-specific interpretation guidance Supports: 'John 3:16', 'Gen 1:1', 'Romans 3:21-26', etc.
Explain a grammatical parsing code. Greek: Robinson codes (e.g., 'V-AAI-3S' = Verb, Aorist, Active, Indicative, 3rd Singular) Hebrew: Westminster/OpenScriptures codes
Find all verses where a specific Greek/Hebrew word appears. After identifying a key word via word_study, use this to see how biblical authors actually used it in context.
Search across Greek and Hebrew lexicons for English concepts or terms. Finds original language words behind English concepts (e.g., 'love' → agape, phileo). Includes LSJ (Liddell-Scott-Jones) Greek, BDB (Brown-Driver-Briggs) Hebrew, and Abbott-Smith NT Greek lexicons.
Study a Greek or Hebrew word by Strong's number or English word. Returns full lexical data: original script, transliteration, Strong's number, definition, and key passages showing usage.
Tools returning lists (search_by_strongs, find_similar_passages, explore_places, explore_events) lack pagination parameters (limit, offset, cursor) and do not document result limits. Violates pattern:paginated-result and mxe:enforce-result-limits.
No error handling guidance. Tools do not document what errors are possible, whether they are retryable, or what the LLM should do next. Violates pattern:recovery-guide and pattern:error-classification.