
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 分