Turath MCP
Related Servers
Alternatives to Turath MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI clients fast, accurate access to turath.io's books and resources, with tools for author biographies, book metadata, full texts, parsed pages, and catalog search over stdio or HTTP.25 npm1MIT
- 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 gradedqualityDmaintenanceMCP 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.MIT
- AlicenseAqualityCmaintenanceEnables browsing, searching, and quote verification of a local ebook library via MCP, providing deterministic RAG with no embeddings or network.62MIT
- AlicenseNot gradedqualityDmaintenanceEnables fetching and searching canonical hadith texts (Arabic and English) with cross-references and citation-safe URLs for assistants, built on FastMCP.3GPL 3.0
- AlicenseNot gradedqualityDmaintenanceProvides 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 12 tools
Most tools target distinct resources (search, book, author, category, catalog, export), but the page-fetching family — turath_get_page, turath_get_pages, turath_fetch_pages_task, and turath_get_book_file — overlaps in purpose and is differentiated only by size/mechanism. turath_search (full-text) vs turath_find_in_catalog (catalog name search) could also be briefly confused, though the descriptions do draw the line.
All twelve tools follow a turath_ prefix with snake_case verb_noun structure (get_page, list_categories, export_pages), which is highly predictable. Minor deviation: get vs fetch verbs are mixed for page retrieval (turath_get_pages vs turath_fetch_pages_task), but the pattern remains readable.
Twelve tools is well within the ideal 3-15 range for a library server. Each tool earns its place: search, browsing hierarchy (categories → category → book → author), page retrieval at three scales, plus summarize/export/task utilities.
The read-only domain is well covered: search, category listing and drill-down, book metadata/TOC, author details, page retrieval at multiple granularities, plus export and summarization. Minor gaps: no dedicated author listing/browse tool (only catalog name search) and no way to navigate pages relative to a search hit, but agents can work around these.