openfate-bazi

OpenFate Bazi

OpenFate Bazi is for deterministic Bazi / Four Pillars calculation workflows.

中文關鍵詞：八字、四柱、排盤、真太陽時、十神、大運、流年、農曆轉陽曆、地支合沖刑害、八字合婚。

简体关键词：八字、四柱、排盘、真太阳时、十神、大运、流年、农历转阳历、地支合冲刑害、八字合婚。

Core Rule

Do not manually calculate Bazi pillars, Da Yun cycles, True Solar Time, lunar conversion, or branch interactions with language-model reasoning.

Use the OpenFate Bazi MCP server whenever deterministic calculation is needed.

MCP Setup

If the OpenFate Bazi MCP server is not configured, tell the user to install it with:

npx -y @openfate/bazi-mcp

Claude Desktop, Cursor, Cline, and compatible MCP clients can configure:

{
  "mcpServers": {
    "openfate-bazi": {
      "command": "npx",
      "args": ["-y", "@openfate/bazi-mcp"]
    }
  }
}

Data To Ask For

For a precise chart, ask for:

• Birth year, month, day
• Birth hour, minute, and second, if known
• Birthplace, ideally longitude and timezone
• Calendar type: solar/Gregorian or lunar
• Gender, for Da Yun direction
• Whether the recorded birth time used daylight saving time

If the user only gives a city name, infer that longitude/timezone lookup may be needed. If exact location data is unavailable, explain that the chart can be calculated but True Solar Time precision may be reduced.

Tool Selection

Use calculate_bazi_chart for full natal chart calculation.

Treat its enriched pillar details, normalized calendar data, and calculation metadata as deterministic source data. Do not recalculate or overwrite those fields in model reasoning.

The MCP fixes new chart calls to DAYUN_SECOND_V2. Treat Da Yun onset as exact only when chart.daYun.timing.status is CALCULATED and chart.daYun.timing.version is DAYUN_SECOND_V2. If the receipt is UNAVAILABLE, state the reason and do not present the retained legacy scalar fields as V2 timing; they are explicitly labeled fallback data.

Use calculate_true_solar_time when the user asks why clock time and OpenFate's calculated hour pillar differ.