Nothing here is invented — it is the official v4 REST API turned into tools, which means the assistant can answer "what does this tafsir say about that verse" by making the two calls itself instead of asking you for an endpoint.
An MCP server generated from the Quran.com REST API v4 OpenAPI specification. Each covered endpoint becomes a tool, so an assistant can pull chapters, verses, translations, tafsirs and audio resources directly.
- Chapters: the full list, a single chapter, and its background info
- Verses fetched the way you actually refer to them — by chapter, by Madani Mushaf page, by juz, by hizb, by rub el hizb, by verse key, or at random
- Full-text search across the corpus
- The catalogue of available translations and tafsirs, the details of any one of them, and a single tafsir retrieved in full
- Audio resources: chapter reciters and the available recitation styles
- The list of juzs, and the list of supported languages
Node.js 22+, and Docker if you take the container path — build the image with `docker build -t quran-mcp-server .`, or build the project and run `dist/src/server.js` with Node. `API_KEY` is passed through for the Quran.com API when one is needed, and `VERBOSE_MODE=true` logs every request, response and error with a timestamp. MIT.
One command — docker build -t quran-mcp-server .