MCP server for GitHub Copilot CLI — provides access to the Church of Jesus Christ Gospel Library (scriptures, General Conference talks, handbooks, and more)
Gospel Library MCP has well-structured tool definitions with clear naming (verb_noun pattern), comprehensive descriptions (150-300 chars each), and complete JSON schemas with typed parameters. All four tools are read-only and properly documented. However, output schemas are not explicitly documented in the code, parameter descriptions lack format constraints and validation guidance, and error handling patterns are absent. No tool annotations (readOnlyHint) despite all being read-only. Descriptions are good but could be more concise for LLM optimization.
List articles and talks available in a Gospel Library category or collection. Returns titles and URLs. Useful for browsing conference sessions, scripture books, or magazine issues. IMPORTANT: Category paths must be exact. For manuals, paths are often year-specific — if you are unsure of the exact path, use search_gospel_library first to discover the correct URL. Come Follow Me paths include the year and audience, e.g. 'manual/come-follow-me-for-individuals-and-families-new-testament-2023' or 'manual/come-follow-me-for-sunday-school-new-testament-2023'. Do NOT guess a generic path like 'manual/come-follow-me' — it will 404. Specify lang to retrieve content in a different language. Defaults to OS locale language.
Fetch the full content of a specific Gospel Library article, talk, manual chapter, or policy page by URL. Returns clean markdown text. Use this after search_gospel_library to read the full content of an article. Specify lang to retrieve content in a different language (e.g. 'spa' for Spanish). Defaults to the OS locale language.
Fetch a specific scripture passage by reference. Supports the Bible (Old and New Testament), Book of Mormon, Doctrine & Covenants, and Pearl of Great Price. Returns only the requested verse(s) as markdown. Specify lang to retrieve the passage in a different language. Defaults to OS locale language.
Search the Church of Jesus Christ Gospel Library (churchofjesuschrist.org) for articles, talks, scriptures, manuals, and policies. Returns a list of matching articles with titles and URLs. No API key required. Use this proactively when answering questions about Church doctrine, policies, scriptures, or general conference talks.
Output schemas not documented. Tool descriptions explain what is returned (e.g., 'Returns a list of matching articles with titles and URLs') but the actual response structure (field names, types, pagination) is not specified in the tool definition. LLMs cannot plan downstream operations or extract fields without knowing the response schema.
No tool annotations despite all tools being read-only. The MCP spec supports readOnlyHint, destructiveHint, and idempotentHint annotations. All four tools should declare readOnlyHint: true to signal to agents that these are safe, non-mutating operations.
Parameter descriptions lack format constraints and validation rules. E.g., 'maxResults' has no min/max bounds stated (description says '1-10, default 5' but this is not enforced). 'lang' parameter lists examples but no enum constraint. 'category' parameter warns about exact paths but provides no regex pattern or validation guidance.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | B | 73 | 2026-07-28+ | v2 |
No error handling or recovery guidance in tool descriptions. If a URL is invalid, a category path returns 404, or a scripture reference is malformed, the tool descriptions do not explain what the LLM should do next (e.g., 'Try search_gospel_library first to discover the correct URL').
browse_category description is verbose (>300 chars) and includes example values ('manual/come-follow-me-for-individuals-and-families-new-testament-2023') that LLMs may reuse literally. Should use enum or pattern constraint instead of inline examples.