Yiditu MCP Server

If you already use Yiditu, the yiditu mcp server is the piece that lets your assistant work with it directly. I Ching hexagram analysis and geographic feng shui for Taiwan locations.

What the server does

本 MCP Server 讓 AI 助手（如 Claude、Cursor、Windsurf）能直接呼叫易．地圖的分析服務，為使用者提供台灣任意地點的卦象分析、地理風水評估與相關知識文章。

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• lat — number
• lng — number
• category — string
• tag — string
• limit — number
• fengshui_location_report — 為某地點產生完整風水選址報告（卦象 + 商圈）
• compare_two_locations — 比較兩地卦象與地理條件，依用途給出建議
• explain_my_hexagram — 用白話解讀某卦象並結合使用者情境
• calculate_hexagram — The calculate_hexagram tool exposed by this server
• analyze_location — The analyze_location tool exposed by this server
• search_articles — The search_articles tool exposed by this server

Installation

yiditu-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Yiditu's toolset — lat, lng, category and 8 more — is a fair guide to whether it matches your workflow. It is maintained by kingbbs; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Yiditu.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.