This server gives AI assistants and agents the prayer times of time.quranmajeed.com: Fajr, Sunrise, Dhuhr, Asr, Maghrib and Isha for any city, today or a whole month. Times come from official published timetables where one exists (London Central Mosque, Jordan's Ministry of Awqaf, UAE, Oman, Malaysia, Indonesia, Morocco and others) or are calculated for the city's coordinates with the method the Prayer Times app applies for that country. Daylight saving is included and every answer names the page to cite. It is free to use, by the makers of the Quran Majeed app.
claude mcp add --transport http prayer-times https://time.quranmajeed.com/mcp
Settings → Connectors → Add custom connector, name Prayer Times, URL https://time.quranmajeed.com/mcp, no OAuth. Then enable it in a chat with the + button.
Settings → Connectors → Create (developer mode), MCP server URL https://time.quranmajeed.com/mcp, authentication None.
mcp.json clients{
"mcpServers": {
"prayer-times": { "url": "https://time.quranmajeed.com/mcp" }
}
}
{
"servers": {
"prayer-times": { "type": "http", "url": "https://time.quranmajeed.com/mcp" }
}
}
| Tool | Input | Answer |
|---|---|---|
get_prayer_times | city (name or site slug: london, new-york, london-ca) or place_id (GeoNames id from search_city); optional date YYYY-MM-DD in the city's local calendar, default today there; optional month true for every day of that month | Local times for the six prayers, UTC offset, Hijri date, the method or official timetable, and the page URL; structured JSON alongside the text |
search_city | query (any spelling, e.g. Makkah or Mecca); optional country ISO code, limit up to 20 | Candidate places with country, region, coordinates, time zone and GeoNames id |
Both tools are annotated read-only. There are no prompts or resources.
The same data is a plain JSON call: https://time.quranmajeed.com/api/prayer-times.php?city=london (add &date=YYYY-MM-DD, &month=1 or use ?id=<GeoNames id>), and every city has a page under /city/. Crawler notes: llms.txt.
Requests are rate-limited per caller; answers are cached per city for the day, so heavy use is welcome within reason. The server logs the caller's address, client identification and the tool called, receives nothing else from the conversation, and trains nothing. Details: privacy policy. Health check: /mcp/health.