quran-mcp-server
Related Servers
Alternatives to quran-mcp-server
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
- AlicenseNot gradedqualityBmaintenanceProvides 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
- AlicenseNot gradedqualityBmaintenanceRemote MCP server exposing Wasilah's Islamic reference data, enabling prayer-time, Qibla, Hijri-date, and Quran-audio queries via natural language.MIT
- FlicenseNot gradedqualityBmaintenanceProvides read-only access to Quranic verses and tafsir from Dorar, enabling retrieval of ayahs, surah tafsir, and search over tafsir content through MCP tools via a Streamable HTTP endpoint.-
- FlicenseAqualityCmaintenanceServes a scholar-approved Islamic corpus of Qur'an and hadith passages to any MCP client with server-side refusal enforcement. Enables natural-language questioning, retrieval, policy checking, and honest corpus coverage reporting while preventing fabricated answers.6-
- AlicenseNot gradedqualityCmaintenanceMCP server to search and retrieve passages from a corpus of 7,872 classical Islamic books via the Sahifah API, with full citations and mu'tabar filtering.13 npmMIT
TDQS
Scored across 20 tools
Most tools have distinct purposes, but there is some overlap between 'GET-chapter', 'info', and 'list-chapters' that could cause confusion, as they all relate to chapter information. The verses retrieval tools are well-differentiated by their indexing methods (e.g., chapter number, juz number).
Naming is inconsistent with mixed conventions: some use snake_case (e.g., 'random_verse'), some use kebab-case (e.g., 'chapter-reciters'), some use camelCase (e.g., 'verses-by_chapter_number'), and one uses uppercase prefix ('GET-chapter'). There is no uniform verb_noun pattern, making it harder to predict tool names.
With 20 tools, the count is borderline high for a Quran-focused server, but it covers various aspects like chapters, verses, recitations, tafsirs, and translations. It feels slightly heavy but still manageable given the domain's complexity.
The tool set provides comprehensive coverage for accessing Quranic content, including chapters, verses by multiple indices, recitations, translations, tafsirs, and search functionality. There are no obvious gaps for typical agent workflows in this domain.