How yayasan-digital-islami-indonesia/quran-api-go works
Quran API Go serves Quran text, translations, surah/juz metadata, and full-text search through REST and MCP interfaces. The main request flow is an HTTP client or MCP client calling its respective server entry point, which delegates to feature services and repositories backed by SQLite. The README documents capabilities beyond the sampled implementation excerpts; those are represented at subsystem level. Wiring is visible in the API entry point, while only search and MCP service calls are directly shown in the excerpts.
Main entry points: main.go REST API · server.go MCP tools · search_service.go Search service · search_repository.go Search repository
Components 20
Quran content
- Ayah routes
internal/handler/ayah_handler.go - Ayah service
internal/service/ayah_service.go - Ayah repository
internal/repository/ayah_repository.go - Surah routes
internal/handler/surah_handler.go - Surah service
internal/service/surah_service.go - Surah repository
internal/repository/surah_repository.go - Juz routes
internal/handler/juz_handler.go - Juz service
internal/service/juz_service.go - Juz repository
internal/repository/juz_repository.go
Search and status
- Search route
internal/handler/search_handler.go - Search service
internal/service/search_service.go - Search repository
internal/repository/search_repository.go - Health routes
internal/handler/healthcheck_handler.go - Health service
internal/service/healthcheck_service.go - Health repository
internal/repository/healthcheck_repository.go
Data access
- SQLite database
internal/database/database.go
Other components
- HTTP client
- MCP client
Connections 27
- HTTP client → REST API: calls
- MCP client → MCP tools: calls
- REST API → Ayah routes: routes
cmd/api/main.go - REST API → Surah routes: routes
cmd/api/main.go - REST API → Juz routes: routes
cmd/api/main.go - REST API → Search route: routes
cmd/api/main.go - REST API → Health routes: routes
cmd/api/main.go - REST API → MCP tools: mounts
cmd/api/main.go - REST API → SQLite database: opens
cmd/api/main.go - REST API → Ayah repository: wires
cmd/api/main.go - REST API → Surah repository: wires
cmd/api/main.go - REST API → Juz repository: wires
cmd/api/main.go - REST API → Search repository: wires
cmd/api/main.go - REST API → Health repository: wires
cmd/api/main.go - REST API → Ayah service: wires
cmd/api/main.go - REST API → Surah service: wires
cmd/api/main.go - REST API → Juz service: wires
cmd/api/main.go - REST API → Search service: wires
cmd/api/main.go - REST API → Health service: wires
cmd/api/main.go - MCP tools → Ayah service: calls
internal/mcpserver/server.go - MCP tools → Surah service: calls
internal/mcpserver/server.go - MCP tools → Juz service: calls
internal/mcpserver/server.go - MCP tools → Search service: calls
internal/mcpserver/server.go - Search route → Search service: calls
internal/handler/search_handler.go - Search service → Search repository: delegates
internal/service/search_service.go - Search repository → SQLite database: queries
internal/repository/search_repository.go - Ayah repository → SQLite database: queries
internal/repository/ayah_repository.go