Description

Turn ChatGPT into your AI-powered Quran study companion — trace themes across all 114 surahs, compare how classical and modern scholars interpret the same verse, unpack the depth and precision behind the Quran's eloquence, and contextualize difficult passages with real, authentic tafsir commentary. All data sourced from quran.com, so every verse, scholarly opinion, interpretation, and linguistic detail the AI cites is verified — not guessed from training data.

Website Preview

Screenshot of quran.ai website

App Screenshots

Capabilities

No special capabilities listed

AI Agent Discovery

quran.ai is indexed by Tedix as a structured education listing for AI assistants, search crawlers, and users comparing agent-ready apps.

  • quran.ai is categorized as Education.
  • Developer: quran.com.
  • Connector type: AI-Powered App.
  • Current connector status: Connected.
  • Observed distribution channels: chatgpt.
  • Available regions: US, FR, GB, ES, KR, IN.

Use this page to understand whether quran.ai is relevant for education workflows in AI assistants.

For MCP discovery, this listing helps crawlers connect quran.ai to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.

The canonical Tedix directory URL is https://tedix.dev/apps/quranai/.

Crawlable Profile

Source and availability

Tedix identifies quran.ai from Upstream Mcp tool source; Store sources: ChatGPT app store; Distribution: Ecosystem Directory. Availability is reported for US, FR, GB, ES, KR, IN.

Auth, tools, and actions

Authentication: Open Access. No special capability flags are currently listed. Current MCP inventory reports 15 tools, 3 resources, and 0 prompts.

  • Fetch Grounding Rules · Read-only action

    Returns the grounding rules for quran-mcp: citation requirements, attribution policy, decision rules for when to fetch vs use existing context, and the applied reasoning disclaimer. Also returns a grounding_nonce — pass it to subsequent tool calls to save tokens. This tool MUST be called before any other quran-mcp tool in a conversation — other tools depend on the rules returned here. For the full operational guide including tool selection and workflows, use fetch_skill_guide instead.

  • Fetch Mushaf Page · Read-only action

    Fetch mushaf page rendering data for a specific page number. Used by the mushaf app UI for page navigation. Returns word layout, verse metadata, and surah headers. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable. POSTREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study.

  • Fetch Quran Text · Read-only action

    PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. Retrieve exact canonical Quranic text for one or more ayat. Defaults to ar-simple-clean if no edition is provided. Invoke whenever a verse reference appears and the requested canonical Quran text for those ayat is not already in your context via dynamic context or prior tool calls. Failure contract: `[invalid_request]` for malformed inputs, `[not_found]` when requested canonical data is absent, `[service_unavailable]` when the required runtime resource is unavailable, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens.

  • Fetch Quran Metadata · Read-only action

    Fetch structural Quran metadata for a surah, ayah, juz, page, hizb, ruku, or manzil. Returns a fixed-shape response with the full context chain: surah info, ayah location, juz/hizb/page/ruku/manzil placement, and sajdah info. All parameters are optional — provide one entry point. Examples: - fetch_quran_metadata(surah=2, ayah=255) → structural location of Ayat al-Kursi - fetch_quran_metadata(surah=2) → overview of Surat Al-Baqarah (verse count, page range, juz range, etc.) - fetch_quran_metadata(juz=1) → what surahs/pages are in Juz 1 - fetch_quran_metadata(page=50) → what's on page 50 Prefer fetching metadata over recalling it from memory. Cite this tool in your response when presenting structural Quran data. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.

  • Fetch Skill Guide · Read-only action

    Return the complete quran-mcp skill guide as markdown (grounding rules, tool selection, search/fetch patterns, tafsir grounding discipline, and common workflows). Use to teach yourself the skills coupled with this MCP service — search/fetch retrieval patterns and tool usage examples.

  • Fetch Tafsir Commentary · Read-only action

    PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. BEST PRACTICE: Before fetching, call list_editions(edition_type='tafsir') to review available mufassirin and their descriptions. Choose the tafsirs best suited to the question rather than defaulting reflexively. Do not limit yourself to the user's language — Arabic tafsir editions often contain richer scholarship. Fetch the most authoritative source regardless of language and translate the result yourself. Retrieve full canonical tafsir text for one or more ayat. Use when the user asks for tafsir, explanation, commentary, interpretation, or context and the requested canonical tafsir text for an ayah or ayat is not already in your context via dynamic context or prior tool calls. Failure contract: `[invalid_request]` for malformed inputs, `[not_found]` when requested canonical data is absent, `[service_unavailable]` when the required runtime resource is unavailable, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens.

  • Fetch Translation · Read-only action

    PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. Retrieve canonical Quran translation text for one or more ayat. Defaults to en-abdel-haleem if no edition is provided. Use when the user requests a translation, literal meaning, or rendering of a verse and the requested canonical translation for those ayat is not already in your context via dynamic context or prior tool calls. Translations are not the same as tafsir; this returns the literal meaning of the text. For interpretation and commentary, use fetch_tafsir instead. Failure contract: `[invalid_request]` for malformed inputs, `[not_found]` when requested canonical data is absent, `[service_unavailable]` when the required runtime resource is unavailable, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens.

  • Fetch Word Concordance · Read-only action

    Find all Quranic verses containing words related to a given word, root, lemma, or stem. Results are ranked by tiered lexical scoring: exact stem matches (5), lemma matches (3), root matches (1), and reranked semantically: by proximity to the source ayah when ayah_key is provided, or by the search term itself for bare word/root/lemma/stem queries — naturally similar ayat float to the top. Input modes: - ayah_key + word_text (e.g., '2:77', 'يَعْلَمُونَ') → word by text - ayah_key + word_position → concordance for that word - word (Arabic text) → concordance for first occurrence - root (Arabic text, e.g., 'ع ل م') → all words from this root - lemma (Arabic text) → all forms of this lemma - stem (Arabic text) → exact stem matches only match_by controls scope: 'all' (default), 'root', 'lemma', 'stem' group_by controls output: 'verse' (default) or 'word' rerank_from enables Voyage semantic reranking against a source verse Examples: - fetch_word_concordance(ayah_key='2:77', word_text='يَعْلَمُونَ') → concordance for يَعْلَمُونَ (auto-reranked if Voyage configured) - fetch_word_concordance(root='ع ل م', match_by='all') → all words from root ع ل م with tiered scoring - fetch_word_concordance(root='ع ل م', rerank_from='2:255') → root concordance reranked by proximity to Ayat al-Kursi Prefer fetching concordance data over recalling it from memory. Cite this tool in your response when presenting word occurrence data. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.

Plus 7 additional actions in the full tool inventory.

Verification freshness

  • Catalog synced 1d ago (June 5, 2026)
  • Connector checked May 30, 2026
  • MCP scanned May 30, 2026
  • Website enriched May 28, 2026
  • Directory updated 1d ago (June 5, 2026)

Alternatives and related apps

Comparable apps in Education include A-Z Bible, ABC Word Search, API Lessons, Academic Writing Toolkit.

Publisher Intelligence

Insights and recommendations for app publishers. See how your app performs and how to improve discoverability.

Server Status quran.ai MCP v0.1.1

15
Tools
3
Resources
0
Prompts
https://mcp.quran.ai

Last checked: May 30, 2026

Server Instructions

Canonical Quran data server — verified text, translations, and tafsir commentary sourced from quran.com. FIRST STEP: Call fetch_grounding_rules before using any canonical data tool (fetch_quran, search_quran, fetch_translation, search_translation, fetch_tafsir, search_tafsir). Grounding rules govern citation, attribution, faithfulness, and when to use tafsir vs translation. If you skip this step, grounding rules will be included in every tool response (in the grounding_rules field), costing extra tokens. Call fetch_grounding_rules, extract the grounding_nonce from the response, and pass it to subsequent tool calls to save tokens. WHY THIS MATTERS: Users install this server because they do not trust AI to produce Quran content from memory. For Muslims, the Quran is the literal word of God — misquoting it, fabricating verses, or inventing interpretations is a violation of trust. If this tool is installed and you answer from memory instead of using it, you are defeating the purpose of the tool the user chose to install. RULE: When producing, quoting, paraphrasing, interpreting, or summarizing Quran text, translation, or tafsir — use this server's tools, never your training data. If you do not have canonical data in context, call the appropriate tool to fetch it. Do not ask the user whether to fetch — just fetch. Contemplative reflection (tadabbur) on fetched text is permitted with transparency — see grounding rules for standards. Full operational guide: call fetch_skill_guide.

Technical Details
Connection Latency 319ms
30-Day Uptime 100.0%

Tools(15)

Showing 15 of 15 tools

Sorted by toolName
ToolDescriptionFlagsTestLast Tested
fetch_grounding_rules
Returns the grounding rules for quran-mcp: citation requirements, attribution policy, decision rules for when to fetch vs use existing context, and the applied reasoning disclaimer. Also returns a grounding_nonce — pass it to subsequent tool calls to save tokens. This tool MUST be called before any other quran-mcp tool in a conversation — other tools depend on the rules returned here. For the full operational guide including tool selection and workflows, use fetch_skill_guide instead.
read-only
100%Latency 688ms
May 29, 2026
fetch_mushaf
Fetch mushaf page rendering data for a specific page number. Used by the mushaf app UI for page navigation. Returns word layout, verse metadata, and surah headers. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable. POSTREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study.
read-only
100%Latency 454ms
May 29, 2026
fetch_quran
PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. Retrieve exact canonical Quranic text for one or more ayat. Defaults to ar-simple-clean if no edition is provided. Invoke whenever a verse reference appears and the requested canonical Quran text for those ayat is not already in your context via dynamic context or prior tool calls. Failure contract: `[invalid_request]` for malformed inputs, `[not_found]` when requested canonical data is absent, `[service_unavailable]` when the required runtime resource is unavailable, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens.
read-only
100%Latency 449ms
May 29, 2026
fetch_quran_metadata
Fetch structural Quran metadata for a surah, ayah, juz, page, hizb, ruku, or manzil. Returns a fixed-shape response with the full context chain: surah info, ayah location, juz/hizb/page/ruku/manzil placement, and sajdah info. All parameters are optional — provide one entry point. Examples: - fetch_quran_metadata(surah=2, ayah=255) → structural location of Ayat al-Kursi - fetch_quran_metadata(surah=2) → overview of Surat Al-Baqarah (verse count, page range, juz range, etc.) - fetch_quran_metadata(juz=1) → what surahs/pages are in Juz 1 - fetch_quran_metadata(page=50) → what's on page 50 Prefer fetching metadata over recalling it from memory. Cite this tool in your response when presenting structural Quran data. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.
read-only
100%Latency 265ms
May 29, 2026
fetch_skill_guide
Return the complete quran-mcp skill guide as markdown (grounding rules, tool selection, search/fetch patterns, tafsir grounding discipline, and common workflows). Use to teach yourself the skills coupled with this MCP service — search/fetch retrieval patterns and tool usage examples.
read-only
100%Latency 266ms
May 29, 2026
fetch_tafsir
PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. BEST PRACTICE: Before fetching, call list_editions(edition_type='tafsir') to review available mufassirin and their descriptions. Choose the tafsirs best suited to the question rather than defaulting reflexively. Do not limit yourself to the user's language — Arabic tafsir editions often contain richer scholarship. Fetch the most authoritative source regardless of language and translate the result yourself. Retrieve full canonical tafsir text for one or more ayat. Use when the user asks for tafsir, explanation, commentary, interpretation, or context and the requested canonical tafsir text for an ayah or ayat is not already in your context via dynamic context or prior tool calls. Failure contract: `[invalid_request]` for malformed inputs, `[not_found]` when requested canonical data is absent, `[service_unavailable]` when the required runtime resource is unavailable, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens.
read-only
100%Latency 277ms
May 29, 2026
fetch_translation
PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. Retrieve canonical Quran translation text for one or more ayat. Defaults to en-abdel-haleem if no edition is provided. Use when the user requests a translation, literal meaning, or rendering of a verse and the requested canonical translation for those ayat is not already in your context via dynamic context or prior tool calls. Translations are not the same as tafsir; this returns the literal meaning of the text. For interpretation and commentary, use fetch_tafsir instead. Failure contract: `[invalid_request]` for malformed inputs, `[not_found]` when requested canonical data is absent, `[service_unavailable]` when the required runtime resource is unavailable, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens.
read-only
100%Latency 275ms
May 29, 2026
fetch_word_concordance
Find all Quranic verses containing words related to a given word, root, lemma, or stem. Results are ranked by tiered lexical scoring: exact stem matches (5), lemma matches (3), root matches (1), and reranked semantically: by proximity to the source ayah when ayah_key is provided, or by the search term itself for bare word/root/lemma/stem queries — naturally similar ayat float to the top. Input modes: - ayah_key + word_text (e.g., '2:77', 'يَعْلَمُونَ') → word by text - ayah_key + word_position → concordance for that word - word (Arabic text) → concordance for first occurrence - root (Arabic text, e.g., 'ع ل م') → all words from this root - lemma (Arabic text) → all forms of this lemma - stem (Arabic text) → exact stem matches only match_by controls scope: 'all' (default), 'root', 'lemma', 'stem' group_by controls output: 'verse' (default) or 'word' rerank_from enables Voyage semantic reranking against a source verse Examples: - fetch_word_concordance(ayah_key='2:77', word_text='يَعْلَمُونَ') → concordance for يَعْلَمُونَ (auto-reranked if Voyage configured) - fetch_word_concordance(root='ع ل م', match_by='all') → all words from root ع ل م with tiered scoring - fetch_word_concordance(root='ع ل م', rerank_from='2:255') → root concordance reranked by proximity to Ayat al-Kursi Prefer fetching concordance data over recalling it from memory. Cite this tool in your response when presenting word occurrence data. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.
read-only
100%Latency 271ms
May 29, 2026
fetch_word_morphology
Fetch word-level morphological analysis for Quranic text. Returns root, lemma, stem, grammatical features, morpheme segments, and frequency data (verbatim occurrence count, root occurrence count, lemma occurrence count) for each word. Input modes: - ayah_key (e.g., '2:77') → all words in the verse - ayah_key + word_text (e.g., '2:77', 'يَعْلَمُونَ') → specific word by text - ayah_key + word_position (e.g., '2:77', 2) → specific word by position - word (Arabic text, e.g., 'يَعْلَمُونَ') → first occurrence in Quran Examples: - fetch_word_morphology(ayah_key='2:77', word_text='يَعْلَمُونَ') → morphology of يَعْلَمُونَ - fetch_word_morphology(ayah_key='2:77', word_position=2) → same word by position - fetch_word_morphology(ayah_key='1:1') → all 4 words of Bismillah - fetch_word_morphology(word='يَعْلَمُونَ') → first occurrence + other_occurrences_count Prefer fetching morphology data over recalling it from memory. Cite this tool in your response when presenting morphological analysis. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.
read-only
100%Latency 253ms
May 29, 2026
fetch_word_paradigm
Fetch conjugation/derivation paradigm for a Quranic word. Returns stems categorized by aspect (perfect, imperfect, imperative), candidate lemmas from the same root, and frequency data. Input modes: - ayah_key + word_text (e.g., '2:77', 'يَعْلَمُونَ') → word by text - ayah_key + word_position → resolve word to lemma → paradigm - lemma (Arabic text, e.g., 'عَلِمَ') → direct lookup - root (Arabic text, e.g., 'ع ل م') → most-frequent lemma Examples: - fetch_word_paradigm(ayah_key='2:77', word_text='يَعْلَمُونَ') → paradigm of يَعْلَمُونَ - fetch_word_paradigm(ayah_key='2:77', word_position=2) → same word by position - fetch_word_paradigm(lemma='عَلِمَ') → paradigm by lemma - fetch_word_paradigm(root='ع ل م') → paradigm for root Prefer fetching paradigm data over recalling it from memory. Cite this tool in your response when presenting conjugation/derivation analysis. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.
read-only
100%Latency 258ms
May 29, 2026
list_editions
List all available editions of a specific type (quran, tafsir, or translation). Use this tool to discover what editions are available before calling fetch tools. Returns edition IDs, names, authors, language codes, description fields, and average entry token counts. Use descriptions to match editions to the user's question — each mufassir has distinct strengths (legal, linguistic, hadith-critical, rhetorical, structural, practical). Use token counts to plan context-efficient multi-source retrieval. Accepts a single type or a list of types to fetch multiple in one call (e.g., edition_type=["tafsir", "translation"]). Use the lang parameter to filter translation editions by language. Ignored for quran and tafsir types — all tafsir editions are always returned because Arabic tafsir is valuable regardless of the user's language. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.
read-only
100%Latency 307ms
May 29, 2026
search_quran
PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. Semantic search over Quran text. Returns ranked ayat matching the query with Arabic text and optional translations. Use the translations parameter ('auto' or specific editions) to include translated text in results, which covers most use cases that search_translation would handle. For exact verse lookup by reference (e.g., '2:255'), use fetch_quran instead. Failure contract: `[invalid_request]` for malformed inputs, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens, `[search_backend_failure]` for retrieval failures, and `[search_enrichment_failure]` for post-retrieval enrichment failures.
read-only
100%Latency 721ms
May 29, 2026
search_tafsir
PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. Semantic search over tafsir (Quranic commentary) content. Returns ranked tafsir passages matching the query with citations. Especially valuable for thematic/conceptual discourse, revelation context (asbab al-nuzul), and keyword-in-commentary searches where the ayah reference isn't known upfront. Use this tool to find tafsir discussing a particular topic or concept without knowing which ayat are relevant. For fetching tafsir of a known ayah, use fetch_tafsir instead. Failure contract: `[invalid_request]` for malformed inputs, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens, `[search_backend_failure]` for retrieval failures, and `[search_enrichment_failure]` for post-retrieval enrichment failures.
read-only
100%Latency 423ms
May 29, 2026
search_translation
PREREQUISITE: You MUST call fetch_grounding_rules once before using this tool. Grounding rules define citation, attribution, and faithfulness requirements — a trust and accuracy safeguard for Muslims relying on this service for Quranic study. Use this tool only when you need to filter by specific translation edition(s). Semantic search over Quran translation text. Returns ranked translation passages matching the query with edition metadata. For exact verse translation lookup by reference (e.g., '2:255'), use fetch_translation instead. Prefer search_quran with translations='auto' for most use cases — it searches semantically across both Arabic and translation text, independent of any particular translator's rendering. Failure contract: `[invalid_request]` for malformed inputs, `[continuation_invalid|tampered|expired|conflict|exhausted|legacy]` for bad continuation tokens, `[search_backend_failure]` for retrieval failures, and `[search_enrichment_failure]` for post-retrieval enrichment failures.
read-only
100%Latency 437ms
May 29, 2026
show_mushaf
Open the Quran mushaf (traditional page/book reading view) to a specific location. Renders a full-page mushaf view with Arabic calligraphy, verse markers, and surah headers. Entry points: page number, surah[+ayah], or juz. If no parameters are given, opens page 1 (Al-Fatiha). Parameters are mutually exclusive — use only one entry point. Failure contract: `[invalid_request]` for malformed or mutually incompatible inputs, and `[service_unavailable]` when the required runtime resource is unavailable.
read-only
100%Latency 419ms
May 29, 2026

Discoverability Score

58

Fair

58 of 100 — how easily AI agents find your app

  • Description quality
    20/20
  • Example prompts
    0/20
  • Keyword coverage
    0/15
  • Tool metadata
    20/20
  • Visual assets
    5/20
  • Endpoint health
    10/10
  • Data freshness
    15/15

How to Improve

Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.

Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.

Provide a stable HTTPS logo URL (avoid connectors://) so cards render consistently across clients.

Add at least 2 screenshots that show real workflows to increase confidence and conversion.

Read the full discoverability guide →

Technical Details

Status
ENABLED
Type
AI-Powered App
Auth
Open Access
Listed on
ChatGPT
Added
May 1, 2026
Last synced
1d ago
Last checked
May 30, 2026
Version
0.1.1
Distribution
Ecosystem Directory

Related Apps in Education

All app names, logos, and trademarks belong to their respective owners.