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-ziwei Calculate ziwei chart for 1992-03-22 18:45 male"
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.
생년월일·출생시각·성별을 받아 자미두수(紫微斗数) 명반을 계산해 반환하는 MCP 서버. 12궁 + 주성/보좌성 + 사화(四化) 텍스트와 12궁 명반 PNG를 돌려준다.
구조·네이밍·PNG·설치 규약은
STANDARD.md를 따른다.mcp-qrskeleton 복제본.
계산: iztro — 경량 자미두수 성반 생성 라이브러리(JS). 한국어 로케일 ko-KR 지원.
렌더: @napi-rs/canvas(prebuilt) — 12궁 4×4 그리드 직접 렌더.
결정론적: 같은 입력 → 같은 명반.
Related MCP server: ziwei-mcp
get_ziwei파라미터 | 타입 | 필수 | 기본 | 설명 |
| string | ✅ | — | 생년월일 |
| string | ✅ | — | 출생시각 → 時辰 인덱스로 변환 |
|
| ✅ | — | 성별 |
|
|
| 양/음력 | |
| string |
| 로케일 |
時辰 변환 (HH:MM → timeIndex 012): iztro util.timeToIndex 사용.
子시는 早子(00:0000:59 → 0)·晚子(23:00~23:59 → 12)로 분리한다.
출력 (둘 다 반환):
구조화 텍스트 — 12궁(천간지지·주성·보좌성·명궁★/신궁☆) + 명주/신주/오행국 + 사화(록/권/과/기)
명반 PNG (1080×1080, 12궁 4×4 그리드, 중앙 출생정보)
예제 출력: examples/ziwei_example.png
(양력 2000-08-16 03:00 寅시 · 여성).
git clone https://github.com/molpass/mcp-ziwei.git
cd mcp-ziwei
npm install && npm run build예제 명반을 직접 생성해 보려면:
npm run example # examples/ziwei_example.png 재생성폰트: 한글·한자 라벨을 위해 한글 가능 폰트가 필요하다. Windows는 Malgun Gothic 기본 탑재라 추가 설치 불필요. Linux는 Nanum/Noto CJK 권장.
ziwei){
"mcpServers": {
"ziwei": {
"command": "node",
"args": ["/abs/path/mcp-ziwei/dist/index.js"]
}
}
}
/abs/path는 클론한 실제 절대경로로 바꾼다. Windows 예:"args": ["C:/Users/<you>/mcp-ziwei/dist/index.js"]
페어링 스킬: skill/ziwei.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
생년월일·출생시각·성별을 받아 자미두수(紫微斗数) 명반을 계산한다. 12궁 + 주성/보좌성 + 사화(四化) 텍스트와 12궁 명반 PNG를 반환한다. iztro 기반, 결정론적.
| Name | Required | Description | Default |
|---|---|---|---|
| birthDate | Yes | 생년월일 (YYYY-MM-DD) | |
| birthTime | Yes | 출생시각 (HH:MM, 24시간) → 時辰 인덱스로 변환 | |
| gender | Yes | 성별 | |
| calendarType | No | 양력(solar) / 음력(lunar) | solar |
| lang | No | 로케일 (기본 ko-KR) | ko-KR |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It states the tool is deterministic and based on iztro, but does not disclose safety (e.g., read-only or destructive), authentication needs, or potential side effects. The output format is mentioned but not detailed.
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 extremely concise with three sentences. The first sentence states the purpose, the second describes outputs, and the third adds technical context. No unnecessary words.
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 moderate complexity (5 parameters, 3 required, no output schema), the description covers the main purpose and outputs. It could mention return structure or usage limitations, but the schema handles parameters well. The lack of output schema is mitigated by describing outputs (text and PNG).
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%, so the baseline is 3. The description does not add significant meaning beyond the schema, only noting that birthTime is converted to a time index. It does not explain derivation details or constraints beyond what is in the JSON schema.
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 that it calculates a Zi Wei Dou Shu chart based on birth date, time, and gender. It specifies the output (12 palaces, main stars, auxiliary stars, four transformations text, and PNG). The verb '계산한다' and resource '명반' are specific, and there are no sibling tools to differentiate.
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 mentions it is based on iztro and deterministic, but does not provide guidance on when to use this tool versus alternatives. No sibling tools exist, so differentiation is not needed, but the lack of contextual usage advice keeps this at a mid score.
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_ziweiOnly one tool exists, so there is no potential for confusion between tools. It is perfectly distinct.
With a single tool, there is no naming inconsistency. The name 'get_ziwei' follows a clear verb_noun pattern in snake_case.
One tool is slightly low but still reasonable for a highly focused server that performs a single computation. It does not feel overly thin.
The tool fully covers the domain of computing a Ziwei Doushu natal chart, returning both text and image. No obvious gaps for the stated purpose.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
BaZi (Chinese Four Pillars) chart calculator. Structured chart data only, no predictions.
Generate BaZi charts from birth details. Explore Four Pillars, solar terms, and Luck Pillars for d…
Zi Wei Dou Shu for AI agents: free natal charts, six transit levels, and optional readings.
BaZi four pillars, Chinese zodiac, lunisolar calendar and almanac days for AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/molpass/mcp-ziwei'
If you have feedback or need assistance with the MCP directory API, please join our Discord server