1. Get a free API key
Same astrology API free tier — 10,000 calls/month. Sign up, then pass X-API-Key to the MCP client.
Navamsha hosts a free astrology MCP server at https://agent.navamsha.in/mcp so Claude, ChatGPT, Cursor, and coding agents call real Jyotish tools — Kundali, Panchang, Dasha, Gun Milan, Western natal, and numerology — instead of inventing chart data.
Same free vedic astrology API key as REST — 10,000 calls/month, no credit card. Lahiri ayanamsa · Navamsha Astrology Engine · 20 curated MCP tools.
How Navamsha's hosted Vedic astrology MCP compares to other astrology MCP servers. Last verified August 10, 2026 — confirm free limits on each vendor site.
Swipe the table to see all columns →
| Provider | Hosted URL | Free tier | Auth | Tools | Ayanamsa | REST + MCP |
|---|---|---|---|---|---|---|
| Navamsha | agent.navamsha.in/mcp | 10,000 calls/month (same key as REST) | X-API-Key header | 20 curated tools | Lahiri (Navamsha Astrology Engine) | One hub — REST + MCP on same key |
| VedAstro | Public Vedic MCP (vedastro.org) | Rate-limited free MCP (~5 req/min cited) | API key / vendor auth | Broad prediction catalog | Verify current default (often Raman cited) | Library + REST + MCP tiers |
| AstrologyAPI.com | Dedicated MCP page | ~150 signup credits (sandbox) | API key | 300+ REST endpoints; MCP scope varies | Vendor defaults — confirm per suite | Credit wallet shared across suites |
| FreeAstroAPI | Hosted MCP included | 80 requests/day REST + MCP | API key | Developer-focused subset | Vendor defaults | REST + MCP on same tiers |
| DivineAPI | developers.divineapi.com/mcp | Plan-dependent — verify pricing page | API key | Vedic + Western + report modules | Vendor defaults | REST + MCP connectors |
1. Get a free API key
Same astrology API free tier — 10,000 calls/month. Sign up, then pass X-API-Key to the MCP client.
2. Connect your client
Pick a client, copy its config, and replace YOUR_NAVAMSHA_API_KEY. Cursor, Claude Desktop, and Windsurf share the same mcpServers JSON shape.
~/.cursor/mcp.json (or .cursor/mcp.json in your project)
{
"mcpServers": {
"navamsha": {
"url": "https://agent.navamsha.in/mcp",
"headers": {
"X-API-Key": "YOUR_NAVAMSHA_API_KEY"
}
}
}
}ChatGPT custom connector
Where your plan exposes custom connectors, go to Settings → Connectors → Create connector, paste https://agent.navamsha.in/mcp, and set X-API-Keyas the connector's auth header. Availability depends on OpenAI's current rollout.
Call list_navamsha_capabilities from any connected agent for live discovery. Tools proxy to api.navamsha.in — same chart JSON as REST.
| Family | Tools |
|---|---|
| Kundali | get_kundali_basic, get_kundali_complete, get_planets, get_houses, get_divisional_chart |
| Panchang | get_panchang, get_muhurta_choghadiya |
| Dasha & timing | get_vimshottari_dasha, get_current_dasha, get_transits |
| Dosha | get_mangal_dosha, get_doshas_summary |
| Matchmaking | get_ashtakoot_match, get_manglik_compatibility |
| Western | get_western_natal, get_western_synastry |
| Numerology | get_life_path, get_name_numerology |
| Meta | list_navamsha_capabilities, get_api_health |
Building outside a chat client? Both frameworks speak Streamable HTTP MCP directly — no custom REST wrapper.
LangChain — langchain-mcp-adapters
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient({
"navamsha": {
"transport": "streamable_http",
"url": "https://agent.navamsha.in/mcp",
"headers": {"X-API-Key": "YOUR_NAVAMSHA_API_KEY"}
}
})
tools = await client.get_tools()CrewAI — crewai-tools
from crewai_tools import MCPServerAdapter
server_params = {
"url": "https://agent.navamsha.in/mcp",
"transport": "streamable-http",
"headers": {"X-API-Key": "YOUR_NAVAMSHA_API_KEY"}
}
with MCPServerAdapter(server_params) as tools:
# pass tools straight into a CrewAI Agent
...Updates & OAuth roadmap
BYO API key works today on this Vedic astrology MCP. Join the list for OAuth connector UX and new tool announcements.