
GetBirthChart MCP
io.github.getbirthchart-com由 GitHub 帳號 getbirthchart-com 發布v0.1.1更新於 Oct 24, 2026
Official MCP server for GetBirthChart astrology calculations.
概覽
GetBirthChart 官方 MCP 伺服器,讓助理透過 GetBirthChart API 計算出生星盤、行星位置、星座、相位與合盤。
- 可以做什麼
- 依出生資料計算完整出生星盤、行星位置、相位,以及太陽/月亮/上升「三巨頭」
- 查詢月亮星座或上升星座,出生時間未知時明確標示不確定性
- 計算兩人星盤之間的合盤相位與摘要
- 套用宮位制、交點類型、相位預設、黃道與歲差等計算選項
- 讀取方法論、資料來源與引擎資訊等參考資源
- 適用情境
- 適合希望助理依出生日期、時間與座標產生結構化占星計算結果的情境,包括出生時間未知的人,而不必自行建置占星引擎。
- 執行需求
- 透過 npx 以 stdio 在本機執行,需要 Node.js 20 或更新版本。必須在 GETBIRTHCHART_API_KEY 環境變數中提供 GetBirthChart 開發者 API 金鑰。需要連線至 GetBirthChart 公開 API 的網路;開發時可選擇以 GETBIRTHCHART_API_BASE_URL 覆寫位址。輸入需提供數值經緯度與 IANA 時區,地名不會進行地理編碼。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 GetBirthChart MCP,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
@getbirthchart/mcp
Official MCP server 0.2.0 for GetBirthChart astrology calculations. It gives
MCP-compatible AI clients access to structured calculations through the public
GetBirthChart API; it does not contain or reimplement the astrology engine.
Requirements
- Node.js 20 or newer
- A GetBirthChart developer API key
Create a key at getbirthchart.com/developers. Keep it private and do not commit MCP host configuration containing the real key.
Quick start
The package runs over MCP stdio and can be launched with npx:
This is the standard command-based configuration for hosts that support MCP stdio servers. Use your client’s current documentation for the exact configuration file or UI location; this repository has been protocol-tested with the official MCP TypeScript client, not vendor-specific clients.
Environment variables
The key is read at startup, never accepted as a tool argument, and never written to stdout, logs, resources, or tool results.
Available tools
All tools are read-only and return structured calculation facts. Inputs use strict fields: date, optional time and place, required latitude, longitude, and timezone, plus optional unknown_time and calculation settings documented below.
The current public API does not geocode place; provide latitude, longitude,
and an IANA timezone even when a place label is included. The MCP server never
invents a birth time. The backend may use local midnight as the labeled
calculation anchor for an unknown-time assessment, but it never presents that
anchor as the person's birth time and never guesses houses, the Ascendant, or
an ambiguous Moon sign.
Example input:
Unknown time:
Calculation options
The natal tools accept the exposed core gbc-astro 1.13.0 options house_system,
node_type, aspect_preset, custom_aspect_rules, additional_points,
fold, zodiac, and ayanamsa. Omit them for the legacy-compatible defaults:
Tropical, Placidus, True Node, Standard aspects, Chiron on, and Lilith off.
Sidereal calculations require a named ayanamsa; Lahiri is the recommended
product choice. Custom aspects require custom_aspect_rules and each rule uses
type, exact_angle, and orb.
The implementation exposes the core's product-relevant house systems
(placidus, whole_sign, equal) plus the registered engine systems, Mean
Node, Standard/Extended/Custom natal aspects, Mean/True Lilith, Vertex and Part
of Fortune requests, and named sidereal ayanamsas. The MCP contract does not
add calculation logic or interpretation. Composite and Davison are core/SDK
operations but are not MCP tools in this release.
Synastry accepts a relationship-level node_type so both charts use one node
convention, plus optional relationship_type, topic, and target_instant.
The server preserves response metadata and additive schema 1.x fields. A natal
HTTP response may omit calculationHash; that is valid and is never required.
The server preserves a returned v2: calculation hash without changing or
truncating it. Core compatibility is natal schema 1.9.0 and synastry schema
1.5.0.
Resources
getbirthchart://methodology— calculation conventions and unknown-time boundaries.getbirthchart://data-sources— ephemeris, timezone, and location-input provenance.getbirthchart://engine-info— provider and public API metadata.
Authoritative web references: Methodology and Data Sources.
Errors
Tool failures use structured error data with a safe machine-readable code, message, retryable, and optional retry_after. Common codes include validation_error, authentication_required, birth_time_required, location_not_found, ambiguous_location, rate_limit_exceeded, timeout, and internal_error.
Troubleshooting
- Missing API key: set
GETBIRTHCHART_API_KEYin the MCP host's server environment; it is never a tool argument. - Authentication or rate-limit errors: use the structured error
codeandretry_afterwhen present. Do not put the key in a tool call or client log. - Unknown-time validation: omit
timewhenunknown_timeistrue; the server will not substitute noon or invent a Rising sign. - Location validation: include numeric WGS84
latitude,longitude, and an IANAtimezone;placeis only a label and is not geocoded here. - Local development: use
GETBIRTHCHART_API_BASE_URLonly with HTTPS, or HTTP on localhost. Never send a production key to an untrusted host.
Privacy and security
Birth data is passed only to the configured public API for the requested calculation. This package does not persist, cache, or log birth inputs, and it has no analytics or telemetry. The optional base URL override changes the trust boundary; do not send a production key to an untrusted host.
Report security issues privately through the process in SECURITY.md. Do not include API keys in bug reports.
Development
Tests use mocked clients and do not call the production API. To run the built server locally, set GETBIRTHCHART_API_KEY and execute node dist/cli.js; normal protocol traffic stays on stdout, while startup failures are written to stderr.
Links
- Developer hub
- GitHub repository
- Core 1.13.0 GitHub release
- Core 1.13.0 on PyPI
- Core OpenAPI source
- Concept DOI · Version DOI
- npm package
MCP Registry metadata
Registry metadata is prepared in server.json with server name io.github.getbirthchart-com/getbirthchart-mcp. Publish the npm package first, then authenticate with the official mcp-publisher tool and publish the metadata. Registry submission is intentionally not part of the package build or CI workflow.
來源:README.md,提交 c8c93dd
工具
0版本歷史
1- v0.1.1最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分