Bazi MCP vs Freebazi — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Bazi MCP vs Freebazi
In-depth architectural comparison of the Bazi MCP and Freebazi 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
Bazi MCP
Spirituality & Esoterica · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Freebazi
Spirituality & Esoterica · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Bazi MCP if you need specialized Spirituality & Esoterica tools running via a local process. Choose Freebazi 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 Bazi MCP when:
You need dedicated capabilities in the Spirituality & Esoterica domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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.
Offline Bazi (八字, Four Pillars) chart: True Solar Time, Ten Gods, Shen Sha, luck pillars.
Bazi MCP is categorized under Spirituality & Esoterica and uses a local stdio subprocess. In contrast, Freebazi belongs to Spirituality & Esoterica using local stdio subprocess. Select Bazi MCP when you need capabilities focused on spirituality & esoterica and Freebazi when you require tools for spirituality & esoterica.
Returns canonical OpenFate links for charting, readings, compatibility, wealth, true solar time, and `llms.txt`.
Freebazi Tools (2)
compute_bazi_chart
Compute a full chart.
search_cities
Search about 490 major world cities by English or Chinese name. Returns each match's country, longitude, and IANA time zone, so you can pass an exact city to `compute_bazi_chart`.