Vedika Astrology and Vastu

@vedika-io/mcp-server

MCP server for the Vedika Intelligence API — astrology, divination and Vastu capabilities across Vedic, Western, KP, Chinese, Tarot, I Ching, Human Design, Numerology, and Ayurvedic domains, exposed as semantic tools for AI agents.

The server calls the documented Vedika API operations. Calculation and interpretation coverage varies by tool and account plan.

Discovery metadata

The server.json descriptor identifies this package as io.github.vedika-io/vedika-mcp-server and uses standard input/output transport. It declares VEDIKA_API_KEY as a required secret environment variable. Supply your key in your MCP client's private environment settings; the descriptor contains no key value.

Quick Start

npm install -g @vedika-io/mcp-server

Get your API key at vedika.io/pricing (starts at $12/mo). No free tier — every query costs money.

Configuration

Where the key goes matters more than which client you use.

- Put it in the gitignored local settings file for your client, never the

shared one. A key in a committed config is a key you have published.

- Pin the version. The examples below pin @2.0.9. npx -y @vedika-io/mcp-server

with no version resolves whatever npm currently tags latest on *every start*, so

a bad or hijacked release runs the moment it is published, with nothing recording

which version you were on.

- Versions before 2.0.4 send your key to whatever VEDIKA_BASE_URL names and

follow a redirect while carrying it. Do not pin below 2.0.4.

- The key is a payment credential: every query costs money. Treat it like a card

number, not like a setting.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{

"mcpServers": { "vedika": { "command": "npx", "args": ["-y", "@vedika-io/mcp-server@2.0.9"], "env": { "VEDIKA_API_KEY": "vk_live_your_key_here" } } } }

Claude Code

Add to .claude/settings.local.json:

Not `.claude/settings.json`. That file is the shared, checked-in one — a key

put there is committed, pushed, and in your history for good. settings.local.json

is gitignored and stays on your machine. This README said settings.json until

2026-09-07, and the published 2.0.3 package still does.

{

"mcpServers": { "vedika": { "command": "npx", "args": ["-y", "@vedika-io/mcp-server@2.0.9"], "env": { "VEDIKA_API_KEY": "vk_live_your_key_here" } } } }

Cursor

Add to Cursor Settings > MCP Servers:

{

"vedika": { "command": "npx", "args": ["-y", "@vedika-io/mcp-server@2.0.9"], "env": { "VEDIKA_API_KEY": "vk_live_your_key_here" } } }

Windsurf

Add to ~/.windsurf/mcp_config.json:

{

"mcpServers": { "vedika": { "command": "npx", "args": ["-y", "@vedika-io/mcp-server@2.0.9"], "env": { "VEDIKA_API_KEY": "vk_live_your_key_here" } } } }

Environment Variables

---

Tools

Core

Vedic Computation

Western Astrology

Cross-System (3 tools)

Supplementary

Tarot & Divination

Chinese Astrology

Alternative Systems

Vedic Extended

Spiritual & Wellness

Bundles

Utility

Vastu

---

Input Patterns

Birth Details (required by most Vedic/Western tools)

{

"datetime": "1990-06-15T14:30:00", "latitude": 28.6139, "longitude": 77.2090, "timezone": "+05:30", "ayanamsa": "lahiri" }

Vedic Compatibility (male/female)

{

"type": "guna-milan", "male": { "datetime": "1992-03-15T10:30:00", "latitude": 28.61, "longitude": 77.20, "timezone": "+05:30" }, "female": { "datetime": "1994-07-22T08:15:00", "latitude": 19.07, "longitude": 72.87, "timezone": "+05:30" } }

Western Relationship (person1/person2 -- gender-neutral)

{

"type": "synastry", "person1": { "datetime": "1990-01-15T14:30:00", "latitude": 40.71, "longitude": -74.00, "timezone": "-05:00" }, "person2": { "datetime": "1992-08-22T09:45:00", "latitude": 34.05, "longitude": -118.24, "timezone": "-08:00" } }

Location-Only (panchang, muhurta)

{

"type": "choghadiya", "latitude": 28.6