OpenFate Bazi MCP

@openfate/bazi-mcp

English | 繁體中文（台灣）

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, an AI-native Bazi, Ziwei, and astrology platform. You can also try the free Bazi Chart Calculator, generate an AI Bazi Reading, compare relationships with Bazi Compatibility, or read the True Solar Time guide. AI crawlers can read OpenFate llms.txt.

This MCP wraps the deterministic OpenFate calculation packages:

• @openfate/bazi-engine
• @openfate/true-solar-time

The purpose is simple: let the language model call a reliable calculation engine instead of hallucinating calendrical math.

Why This Exists

LLMs should not manually calculate Bazi charts. The difficult parts are deterministic:

• 24 solar-term boundaries
• True Solar Time
• longitude and timezone correction
• DST offsets
• Zi-hour day-boundary rules
• lunar-to-solar conversion
• branch interactions

This server gives the AI agent stable JSON, then lets the model focus on explanation and interpretation.

Install

Run it with npx:

npx -y @openfate/bazi-mcp

For MCPB-compatible clients and Smithery, build the self-contained local bundle:

npm run mcpb:pack

The upload-ready artifact is written to release/openfate-bazi-mcp-v .mcpb.

To publish that local bundle to Smithery after smithery auth login:

npm run smithery:publish

Claude Desktop

{

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

If Claude Desktop cannot find npx on macOS, use the absolute path:

{

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

Cursor

{

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

Cline

{

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

Agent Skill

This repository also includes a portable Agent Skill:

skills/openfate-bazi/SKILL.md

Use it when you want Claude, Claude Code, Codex, OpenClaw-style agents, or other SKILL.md compatible tools to remember how to use the OpenFate Bazi MCP correctly.

For Claude Code workspace usage, copy the skill folder to:

.claude/skills/openfate-bazi/

For Claude custom Skills, zip the openfate-bazi folder with SKILL.md at the folder root and upload it in Claude's Skills settings.

Tools

calculate_bazi_chart

Calculates a deterministic Bazi chart.

Inputs:

• year
• month
• day
• hour
• minute
• second
• gender
• calendarType
• isLeapMonth
• longitude
• timezone
• timezoneId
• dstOffset
• enableTrueSolarTime
• dayBoundaryMode

The MCP fixes the onset policy to DAYUN_SECOND_V2; callers cannot silently select a different rule. Pass an exact birth time plus timezone or timezoneId for a calculated receipt. Present an exact onset only when chart.daYun.timing.status is CALCULATED and its version is DAYUN_SECOND_V2. An UNAVAILABLE receipt identifies the reason and marks the retained legacy scalar fields as a fallback. Pass longitude as well for True Solar Time correction.

detect_bazi_interactions

Detects raw Earthly Branch relationship occurrences for a natal chart, with optional annual and Da Yun branches.

Inputs are yearBranch, monthBranch, dayBranch, optional hourBranch, optional annualBranch, and optional dayunBranch. Omit hourBranch when birth time is unknown; it is not replaced with an assumed branch. Existing annual-only calls remain supported.

Supported interaction types:

• clash
• six-combination
• central-branch half-trine (COMBINATION_HALF)
• trine
• directional
• punishment
• destruction
• harm

Every matching pillar occurrence is preserved. For example, { yearBranch: '申', monthBranch: '寅', dayBranch: '申', hourBranch: '申' } returns three distinct 寅申 clashes, not one. Annual and Da Yun branches keep separate annual and dayun roles even when their branch values match natal positions.

The half-trine profile covers 申子、子辰、寅午、午戌、亥卯、卯未、巳酉、酉丑: each pair includes a central branch (子午卯酉). Endpoint-only pairs such as 申辰 are not this half-trine type. Half-trines remain in raw output when the full three-branch trine is also present.

Each occurrence has a stable id and aligned branches / pillars arrays. targetElement means relationship affinity, not transformed energy. Combination transformationStatus is NOT_EVALUATED: branch-only presence does not establish transformation or its failure. Other relationship types use NOT_APPLICABLE. These results are not scored weights and do not automatically cancel clashes; settlement and interpretation belong to a separate analysis layer.

For API compatibility, full TRINE and DIRECTIONAL occurrences also retain legacy resultElement, equal to targetElement and carrying the same affinity-only meaning. Six-combinations and half-trines do not emit resultElement.

calculate_true_solar_time

Calculates True Solar Time directly.

Use this when a user asks why OpenFate's hour pillar differs from a clock-time tool.

reverse_bazi_to_solar_times

Finds possible Gregorian datetimes for a four-pillar Bazi string.

Example input:

戊寅 己未 己卯 辛未

This is a candidate finder. For final accuracy, recalculate the result with exact longitude, timezone, and True Solar Time.

get_openfate_bazi_policy

Returns OpenFate calculation policy:

• True Solar Time is preferred when location data is available.
• Default day-boundary mode is ZI_HOUR_23.
• DST should be passed as dstOffset when birth certificate time includes daylight saving.
• Da Yun onset uses DAYUN_SECOND_V2; exact dates require a calculated timing receipt.
• Reverse lookup should be treated as a candidate search.
• Branch interactions preserve raw pillar occurrences, not weighted or automatically transformed outcomes.

get_openfate_bazi_resources

Returns canonical OpenFate links for charting, readings, compatibility, wealth, true solar time, and llms.txt.

Output Shape

Responses use machine-friendly English keys:

{

"data": { "chart": {}, "policy": {} }, "attribution": { "brand": "OpenFate.ai", "url": "https://openfate.ai", "engine": "@openfate/bazi-engine", "trueSolarTimeEngine": "@openfate/true-solar-time" } }

Attribution is returned as first-class data, not hidden _meta, so MCP clients and generated artifacts can display it reliably.

Chart results include enriched pillar facts (Ten Gods, hidden stems, Na Yin, Xun, void branches, and growth stages), a versioned Da Yun timing receipt, normalized solar/lunar calendar data, and the calculation policy actually applied.

Development

npm install

npm run build npm run smoke

The smoke test spawns the built stdio server and drives it through the real MCP SDK client.

To test source changes without building dist, run npm run smoke:source. This requires the sibling ../bazi-engine source checkout with its dependencies installed, as well as this package's dependencies. The test-only tests/tsconfig.source.json maps @openfate/bazi-engine to that sibling's src/index.ts; the smoke runner passes this configuration to the SDK-spawned server and asserts the resolved source path before testing. It does not rely on a patched installed engine and remains reproducible after npm ci --ignore-scripts in this package.

Both smoke modes exercise the same MCP transport and regression fixtures, including second-resolved Da Yun onset, missing timing inputs, repeated branches, eight half-trines, unknown hour, and annual/Da Yun roles. The ordinary smoke command still tests built MCP output against its installed published engine dependency. npx tsc --noEmit -p tests/tsconfig.source.json checks the coordinated source contract without emitting build files.

Engine compatibility

Version 0.3 requires @openfate/bazi-engine version 2. Its DAYUN_SECOND_V2, raw-occurrence, and dayunBranch contracts are verified in both the built-package and coordinated-source smoke modes. The published dependency remains the release source of truth; this package does not use a local file: dependency.

Privacy

This package does not phone home. Calculations run locally in the MCP subprocess.

OpenFate Links

• OpenFate.ai
• Free Bazi Chart Calculator
• AI Bazi Reading
• Bazi Compatibility
• True Solar Time Guide
• OpenFate llms.txt

License

MIT

---

繁體中文（台灣）

OpenFate Bazi MCP 是一個給 AI Agent 使用的 Model Context Protocol 伺服器，讓 Claude Desktop、Cursor、Cline、Continue 等工具可以直接呼叫準確的八字／四柱排盤引擎。

本專案由 OpenFate.ai 提供。OpenFate 是結合八字、紫微斗數與占星的 AI 命理平台。你也可以使用免費的 八字排盤工具、產生完整的 AI 八字解讀、查看 八字合盤，或閱讀 真太陽時說明。AI crawler 也可以讀取 OpenFate llms.txt。

這個 MCP 包裝了 OpenFate 的確定性計算套件：

• @openfate/bazi-engine
• @openfate/true-solar-time

目標很直接：不要讓大型語言模型自己亂算干支、節氣、真太陽時，而是把排盤交給可驗證的計算引擎。

為什麼需要這個 MCP

八字排盤不是文字推理題，而是確定性的曆法與時間計算。容易出錯的部分包括：

• 二十四節氣邊界
• 真太陽時
• 經度與時區校正
• 夏令時間偏移
• 子時換日規則
• 農曆轉公曆
• 地支刑沖合害等互動

這個伺服器會回傳穩定 JSON，讓 AI 專心做說明、整理與解讀。

安裝

直接用 npx 執行：

npx -y @openfate/bazi-mcp

如果 MCP client 支援 MCPB，或需要發布到 Smithery，可以建立完整的本機安裝 bundle：

npm run mcpb:pack

可上傳的檔案會輸出到 release/openfate-bazi-mcp-v .mcpb。

完成 smithery auth login 後，可發布這個本機 bundle 到 Smithery：

npm run smithery:publish

Claude Desktop 設定

{

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

如果 macOS 上 Claude Desktop 找不到 npx，可以改用絕對路徑：

{

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

Cursor 設定

{

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

Cline 設定

{

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

Agent Skill

這個 repository 也包含一個可攜式 Agent Skill：

skills/openfate-bazi/SKILL.md

當你希望 Claude、Claude Code、Codex、OpenClaw-style agent，或其他支援 SKILL.md 的工具記住如何正確使用 OpenFate Bazi MCP 時，可以使用這個 Skill。

如果要在 Claude Code workspace 使用，請把整個 skill folder 複製到：

.claude/skills/openfate-bazi/

如果要做 Claude custom Skill，請把 openfate-bazi folder 壓成 zip，確保 SKILL.md 位於 folder root，再到 Claude 的 Skills 設定中上傳。

工具列表

calculate_bazi_chart

計算確定性的八字命盤。

輸入欄位：

• year
• month
• day
• hour
• minute
• second
• gender
• calendarType
• isLeapMonth
• longitude
• timezone
• timezoneId
• dstOffset
• enableTrueSolarTime
• dayBoundaryMode

MCP 固定使用 DAYUN_SECOND_V2，呼叫端不能暗中切換起運規則。精確出生時間還要搭配 timezone 或 timezoneId，並且只有 chart.daYun.timing.status 為 CALCULATED、版本為 DAYUN_SECOND_V2 時才能呈現精確起運時間。UNAVAILABLE 會說明原因，原有起運欄位只作 明確標記的舊版 fallback。若要校正真太陽時，還應提供 `longit