Vedaksha vs Bazi MCP
A side-by-side look at the Vedaksha and Bazi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vedaksha for spirituality & esoterica work as a local process; choose Bazi MCP for spirituality & esoterica as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vedaksha when
- You need dedicated capabilities in the Spirituality & Esoterica domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VEDAKSHA_MCP_TOKEN.
Choose Bazi MCP when
- You need dedicated capabilities in the Spirituality & Esoterica domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
getBaziDetail, getSolarTimes, getChineseCalendar.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Spirituality & Esoterica | Spirituality & Esoterica |
| Quality signal | 41/100 · Fair | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | VEDAKSHA_MCP_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 436 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Vedaksha | View Bazi MCP |
Tools & capabilities
Vedaksha tools
No tool names declared yet. Check the project README from the listing page.
Bazi MCP tools 3
getBaziDetail根据时间（公历或农历）、性别来获取八字信息。solarDatetime和lunarDatetime必须传且只传其中一个。getSolarTimes根据八字获取公历时间列表。返回的时间格式为：YYYY-MM-DD hh:mm:ss。例如时间1998年7月31日下午2点整表示为：1998-07-31 14:00:00getChineseCalendar获取指定公历时间（默认今天）的黄历信息。
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Vedaksha
{
"mcpServers": {
"vedaksha": {
"command": "uvx",
"args": [
"vedaksha"
],
"env": {
"VEDAKSHA_MCP_TOKEN": "YOUR_VEDAKSHA_MCP_TOKEN_HERE"
}
}
}
}
Bazi MCP
{
"mcpServers": {
"cantian-ai-bazi-mcp": {
"command": "npx",
"args": [
"bazi-mcp"
]
}
}
}
Frequently asked questions
Vedaksha is categorized under Spirituality & Esoterica and uses a local stdio subprocess. Bazi MCP belongs to Spirituality & Esoterica and uses a local stdio subprocess. Pick Vedaksha for spirituality & esoterica work and Bazi MCP for spirituality & esoterica.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Vedaksha has no declared pricing — check the project's own site. Bazi MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add vedaksha and cantian-ai-bazi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vedaksha has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 4 GitHub stars. Bazi MCP has 64/100 (Good) with 4 views, 0 installs and 436 GitHub stars.