Add translation listing and verse fetching to Bible MCP server

[KallynGowdy]

Summary

This PR enhances the Bible MCP server with new capabilities for discovering available translations and fetching individual verses, while also refactoring the chapter fetching to use a simplified JSON format.

Key Changes

• New listTranslations() tool: Lists available Bible translations from the API with optional filtering by language (ISO 639-3 codes or language names) and translation name. Includes caching of the translations list and case-insensitive substring matching.

• New fetchVerse() tool: Directly retrieves the text of a single verse or verse range (e.g., "John 3:16" or "John 3:16-18") without requiring a separate reference lookup step.

• Refactored chapter fetching: Replaced fetchChapterJson() with fetchSimpleChapterJson() that uses the simplified .simple.json endpoint where verse content is pre-flattened into single text strings, eliminating the need for complex content parsing.

• Removed complex verse parsing: Deleted flattenVerseContent() function since the simplified format already provides text as a single string per verse.

• Tool naming improvements: Renamed search → getBibleReference and fetch → fetchChapter for clarity and consistency.

• New data structures: Added TranslationSummary interface and filterTranslations() utility function for flexible translation filtering.

• Enhanced error handling: Added error() helper function for consistent error responses in MCP tools.

Notable Implementation Details

• Translation filtering supports both exact language code matching and partial name matching across multiple fields (id, name, englishName, shortName, languageName, languageEnglishName).
• The fetchVerse() tool automatically strips the verse number prefix for single-verse results for cleaner output.
• Translations are cached per API base URL to avoid repeated fetches.
• Updated README to document all four tools and their capabilities.

https://claude.ai/code/session_01J6xhi8xAhoc83gHsJj2Luf