Quran MCP Server vs Bazi MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Quran MCP Server vs Bazi MCP
In-depth architectural comparison of the Quran MCP Server and Bazi MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Quran MCP Server
Spirituality & Esoterica · Local stdio
Quality: 33/100 (Emerging) | Auth: API Key required
Bazi MCP
Spirituality & Esoterica · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Quran MCP Server if you need specialized Spirituality & Esoterica tools running via a local process. Choose Bazi MCP if your workspace requires Spirituality & Esoterica integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Quran MCP Server when:
You need dedicated capabilities in the Spirituality & Esoterica domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: API_KEY, PORT, VERBOSE_MODE.
Primary tools included: Chapter and chapter-information lookup, Verse retrieval across Quranic divisions, Quran.com term search.
MCP server to interact with Quran.com corpus via the official REST API v4.
Deterministic Bazi / Four Pillars MCP server with True Solar Time, lunar/solar conversion, Da Yun luck cycles, branch interactions, reverse Bazi lookup, and OpenFate calculation metadata. Install: npx -y @openfate/bazi-mcp.
Quran MCP Server is categorized under Spirituality & Esoterica and uses a local stdio subprocess. In contrast, Bazi MCP belongs to Spirituality & Esoterica using local stdio subprocess. Select Quran MCP Server when you need capabilities focused on spirituality & esoterica and Bazi MCP when you require tools for spirituality & esoterica.
Calculate a deterministic OpenFate Bazi/Four Pillars chart with True Solar Time correction, Day Master, DAYUN_SECOND_V2 onset receipts, Da Yun cycles, and branch interactions. Pass an exact birth time plus timezone or timezoneId for a calculated V2 onset; otherwise inspect the explicit unavailable/fallback receipt.
detect_bazi_interactions
Detect raw Earthly Branch relationship occurrences for a natal chart and optional annual and Da Yun branches. Preserves every matching pillar position, including repeated branches. Covers clashes, six-combinations, the eight central-branch half-trines (COMBINATION_HALF), full trines, directionals, punishments, destructions, and harms. Results establish relationship presence, not weights, cancellation, or automatic transformation; targetElement is an affinity, not transformed energy.
calculate_true_solar_time
Calculate OpenFate True Solar Time from civil birth time, longitude, timezone, and optional DST offset. Use this when explaining why the hour pillar may differ from ordinary clock-time tools.
reverse_bazi_to_solar_times
Find possible Gregorian datetimes that produce a given four-pillar Bazi string. This is useful when a user only has a Bazi chart or screenshot. This lookup uses clock-time pillars without location-based true solar correction.
get_openfate_bazi_policy
Return OpenFate calculation policy and LLM guidance for Bazi chart calls.
get_openfate_bazi_resources
Return canonical OpenFate URLs for charting, readings, compatibility, wealth, true solar time, and AI crawler metadata.