EzanVakti.MCP.Server

The EzanVakti MCP Server exposes a set of endpoints via the MCP (Model Context Protocol) interface to access Islamic prayer times from the EzanVakti API (Diyanet). It supports operations to list available countries, search cities within a country, look up districts within a city, retrieve monthly prayer times for a district, perform smart searches by city name, and obtain today's prayer times for a district. Tools include GetCountries, GetCities, GetDistricts, GetPrayerTimes, SearchCityPrayerTimes, and GetTodayPrayerTimes. Clients can interact with these tools through the configured MCP client (for example in VS Code or Claude Desktop) by issuing natural language prompts or the predefined command patterns shown in the documentation. With proper configuration, the server handles API communication, data formatting, and caching where appropriate, returning structured prayer time data with Hijri and Gregorian dates, as well as times like Imsak, Gunes, Ogle, Ikindi, Aksam, and Yatsi.

To use it, configure an MCP client with the provided server name (ezanvakti) and point it to the running server process. Send requests such as “Show me all countries with prayer times” or “Get prayer times for district 9535” to retrieve the corresponding data in a standardized response format.

Prerequisites:

• .NET 8.0 SDK or later
• A compatible MCP client (e.g., VS Code with Copilot, Claude Desktop, etc.)

Installation steps:

1. Clone or download the repository containing EzanVakti.MCP.Server.
2. Ensure the .NET SDK is installed (dotnet --version should show 8.x).
3. Restore dependencies:

   dotnet restore
   

4. Build the project:

   dotnet build
   

5. Run the server during development:

   dotnet run
   

6. For production, publish the project and run the published binary:

   dotnet publish -c Release
   ./bin/Release/net8.0/publish/EzanVakti.MCP.Server
   

Notes and tips:

• The server relies on the EzanVakti API; be mindful of API rate limits (30 requests per 5 minutes and 200 requests per day). Since prayer times are monthly, you typically need one request per location per month.
• Docker support is available via standard .NET publish in a Linux image if you need containerized deployment.
• Ensure your MCP client configuration includes the correct project path when using the dotnet run approach (as shown in the example configuration).
• If you encounter 429 errors, consider caching prayer times per district for a month to reduce API calls.
• The server outputs data with both Hijri and Gregorian dates, including all standard prayer times (Imsak, Gunes, Ogle, Ikindi, Aksam, Yatsi) and supplementary fields like KibleSaati and sunrise/sunset times.