Openfate Bazi Mcp

What is OpenFate Bazi MCP?

OpenFate Bazi MCP is a Model Context Protocol server for accurate Bazi / Four Pillars calculation inside AI agents such as Claude Desktop, Cursor, Cline, and Continue. Powered by OpenFate.ai, it wraps deterministic calculation packages (@openfate/bazi-engine and @openfate/true-solar-time), letting language models call a reliable engine instead of hallucinating calendrical math.

How to use OpenFate Bazi MCP?

Run with npx -y @openfate/bazi-mcp. Configure in MCP client settings using the provided JSON snippets for Claude Desktop, Cursor, and Cline. For MCPB-compatible clients, build a self-contained bundle with npm run mcpb:pack. An Agent Skill (SKILL.md) is included for use with Claude, Claude Code, Codex, and similar tools.

Key features of OpenFate Bazi MCP

• Deterministic Bazi chart calculation with AI agents.
• True Solar Time, longitude, timezone, and DST corrections.
• Supports Earthly Branch interactions (clash, combination, trine, etc.).
• Reverse lookup from four pillars to possible Gregorian datetimes.
• Returns attribution as first-class data in output.
• Runs locally with no data sent to external servers.

Use cases of OpenFate Bazi MCP

• Chat assistants that need accurate Bazi chart generation.
• Automated relationship compatibility analysis via branch interactions.
• Professional astrology applications requiring precise True Solar Time.
• Educational tools demonstrating Bazi calculation principles.
• Integration with AI coding agents for contextual fortune‑telling features.

FAQ from OpenFate Bazi MCP

Why does this server exist instead of having the LLM calculate the chart directly?

LLMs should not manually calculate Bazi charts. The difficult parts (solar terms, True Solar Time, timezone corrections, DST, Zi‑hour rules, lunar‑solar conversion, branch interactions) are deterministic and better handled by a dedicated engine.

Does this server send my data to a remote server?

No. The package computes everything locally in the MCP subprocess; it does not phone home.

What runtime does it require?

Node.js is required. Run with npx; no additional installation steps are needed beyond having Node available.

Which transports and authentication does it use?

The server communicates via stdio (standard input/output). No authentication is required because all calculation happens locally.

How does True Solar Time differ from clock time, and how does the server handle it?

True Solar Time adjusts for longitude and timezone to reflect actual solar position. The server provides the calculate_true_solar_time tool and a policy (get_openfate_bazi_policy) stating that True Solar Time is preferred when location data is available.