Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-astrology get my natal chart for 1990-05-15 12:00 Seoul"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
출생 정보를 받아 서양 점성술 네이탈 차트(행성별 별자리·하우스, ASC·MC 텍스트 + 차트 PNG)를 반환하는 MCP 서버. "내 네이탈 차트 그려줘"라고 하면 차트 휠 이미지를 돌려준다.
구조·네이밍·PNG·설치 규약은
STANDARD.md를 따른다.mcp-qrskeleton 복제본.
계산: celestine — Swiss Ephemeris / JPL Horizons 대조 검증된 천체력.
렌더: @astrodraw/astrochart(SVG) → jsdom으로 헤드리스 구동 → sharp로 PNG 변환.
결정론적: 같은 입력 → 같은 차트.
Related MCP server: mcp-ziwei
get_natal_chart파라미터 | 타입 | 필수 | 설명 |
| string | ✅ | 생년월일 |
| string | ✅ | 출생시각 (24시간) |
| number | ✅ | 위도 (북위 +, 남위 −) |
| number | ✅ | 경도 (동경 +, 서경 −) |
| number | string | ✅ | 숫자 오프셋( |
IANA 존을 주면 해당 출생 시각의 DST를 반영해 오프셋을 산출한다.
출력 (둘 다 반환):
구조화 텍스트 — 행성별 별자리·도수·하우스(역행 R 표시), ASC·MC
네이탈 차트 PNG (1080×1080)
예제 출력: examples/astrology_example.png
(1990-05-15 12:00 · 서울 · Asia/Seoul).
git clone https://github.com/molpass/mcp-astrology.git
cd mcp-astrology
npm install && npm run build예제 차트를 직접 생성해 보려면:
npm run example # examples/astrology_example.png 재생성astrology){
"mcpServers": {
"astrology": {
"command": "node",
"args": ["/abs/path/mcp-astrology/dist/index.js"]
}
}
}
/abs/path는 클론한 실제 절대경로로 바꾼다. Windows 예:"args": ["C:/Users/<you>/mcp-astrology/dist/index.js"]
페어링 스킬: skill/astrology.skill.md —
위·경도·시간대가 빠지면 사용자에게 질의하도록 안내한다.
Hermes Agent용 MCP — molpass의 바이브 코딩(vibe coding) 프로젝트.
아이디어·방향: molpass (이정훈) · https://zeolinex.com
기획: Claude (Chat)
개발: Claude Code
자가 호스팅 Hermes Agent에 도구로 붙여 쓰는 MCP 서버입니다.
같은 모음:
mcp-saju — 사주명리 만세력
mcp-qr — QR 코드 생성
mcp-biorhythm — 바이오리듬
mcp-astrology — 서양 점성술 네이탈 차트
mcp-ziwei — 자미두수 명반
mcp-numerology — 수비학
mcp-liuren — 대육임
mcp-qimen — 기문둔갑
mcp-taiyi — 태을신수
mcp-weather — 한국 날씨·미세먼지
mcp-newsfeed — 한국 주요뉴스
MIT
출생 정보(날짜·시각·위경도·시간대)를 받아 서양 점성술 네이탈 차트를 계산한다. 행성별 별자리·하우스와 ASC·MC 텍스트, 그리고 네이탈 차트 PNG를 반환한다.
| Name | Required | Description | Default |
|---|---|---|---|
| birthDate | Yes | 생년월일 (YYYY-MM-DD) | |
| birthTime | Yes | 출생시각 (HH:MM, 24시간) | |
| latitude | Yes | 위도 (북위 +, 남위 −) | |
| longitude | Yes | 경도 (동경 +, 서경 −) | |
| timezone | Yes | 시간대: 숫자 오프셋(예: 9, -4) 또는 IANA 존(예: "Asia/Seoul") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It states what the tool calculates and returns but omits details like ephemeris used, precision, or whether network access is required. It is adequate but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence that front-loads the core purpose. It is efficient but could benefit from slightly more structure, such as separating input and output details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of output schema and siblings, the description adequately covers inputs, computation, and outputs (text and PNG). It is complete enough for an agent to understand and use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, meaning the schema already documents all parameters. The description adds no additional meaning beyond the schema descriptions, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates a Western astrology natal chart from birth information, specifying inputs and outputs. It uses a specific verb ('calculate') and resource ('natal chart'), and distinguishes the tool's purpose without needing sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for natal chart calculation but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. No siblings are provided, so the need is reduced, but the dimension expects some guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0get_natal_chartOnly one tool exists, so no ambiguity. The description clearly defines its purpose.
With a single tool, naming is inherently consistent.
One tool for an astrology server feels thin; users typically expect multiple tools for different astrology functions.
Only natal chart calculation is available; missing common astrology features like transits, synastry, or progressions.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Western, Vedic, and Chinese astrology calculations, charts, forecasts, and geocoding.
Western natal charts, horoscopes, transits and synastry for AI agents, verified vs NASA JPL.
Official Divine API MCP for Western Astrology: Natal, Synastry, Transit, Composite, Progressions.
Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/molpass/mcp-astrology'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
