QUL MCP
Related Servers
Alternatives to QUL MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides read-only access to Quran data — reciters, surahs, full-text search, ayah retrieval, prayer times, live radio stations, and Hijri dates — so AI agents can answer Islamic content queries. Runs locally via stdio or remotely over stateless HTTP for Claude, ChatGPT, and other MCP clients.8ISC
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to retrieve canonical Quran text, translations, scholarly tafsir, full-text search, and word-level morphology from verified Quran data.-
- AlicenseAqualityDmaintenanceProvides AI assistants with comprehensive access to Islamic resources including Quran verses with translations, Tafsir commentary, Hadith collections, and audio recitations. Enables users to explore Islamic texts, get daily inspiration, and access scholarly interpretations through natural language queries.1828 npm10MIT
- FlicenseNot gradedqualityCmaintenanceProvides canonical Quran text, translations, and tafsir commentary via MCP for accurate AI citation.125-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants and developers to query Quranic verses, Hadith, Tafsir, and classical Islamic heritage texts through a single federated MCP endpoint with unified tools and caching.-
- AlicenseNot gradedqualityCmaintenanceProvides AI clients with fast, hallucination-free access to the Quran through 13 MCP tools, covering search, navigation, morphology, tafsir, translations, and surah background over stdio and Streamable HTTP.MIT
TDQS
Scored across 9 tools
Each tool targets a fairly distinct resource: chapters, verses, translations, tafsir, audio, timings, resource listings, and a random ayah. The main soft overlap is between qul_get_verses (which can include translations and word-by-word data) and qul_get_translations, plus qul_get_tafsir vs. verse text, but the descriptions explicitly steer usage (ranges/multi-translation compare vs. single ayah fetch).
All tools share the qul_ prefix and a consistent verb_noun pattern (list_chapters, get_chapter, get_verses, get_tafsir, etc.). The only deviation is qul_random_ayah, which omits the verb but remains clear and readable.
Nine tools is well within the sweet spot and each earns its place: listing, fetching, audio, timings, tafsir, translations, and discovery of resource IDs. No obviously redundant or trivial entries.
The surface covers the core Quran domain: chapters, verses (with translations and word data), tafsir, audio, ayah timings, resource discovery, and a random-ayah convenience tool. The notable gap is a text/search tool (e.g., searching verses by keyword), which agents would otherwise have to emulate client-side.