The RoxyAPI Astrology MCP server gives any AI agent natal charts, horoscopes, synastry, transits, Vedic kundli, panchang, tarot, numerology and 18+ insight domains on one key, as hosted Remote MCP with nothing to install. RoxyAPI is the data layer for insight apps.
https://roxyapi.com/mcp/astrology
Point an MCP client at that URL, send your key in the X-API-Key header, and the agent can call 258+ tools across every RoxyAPI domain. Calculations read the NASA JPL DE440 ephemeris directly and are verified against NASA JPL Horizons. Get a key at roxyapi.com/pricing.
Use the hosted Remote MCP URL over Streamable HTTP. Every domain has its own server at https://roxyapi.com/mcp/{domain}, so an agent loads only the tools it needs. Add location beside any chart domain so the agent can turn a city name into coordinates and a timezone by itself.
export ROXY_API_KEY="your-key-from-roxyapi.com/account?tab=keys"claude mcp add --transport http --scope user roxy-astrology \
https://roxyapi.com/mcp/astrology --header "X-API-Key: $ROXY_API_KEY"Writing integration code rather than calling tools at run time? Point Claude Code at the documentation server instead: claude mcp add --transport http roxy-docs https://roxyapi.com/mcp/docs.
Claude Desktop starts local servers from claude_desktop_config.json, so use the stdio package below, or download astrology-mcp-server.mcpb, double-click it to install, and paste your key when asked.
{
"mcpServers": {
"roxy-astrology": {
"command": "npx",
"args": ["-y", "@roxyapi/mcp"],
"env": { "ROXY_API_KEY": "your-key" }
}
}
}import OpenAI from 'openai';
const openai = new OpenAI();
const response = await openai.responses.create({
model: 'gpt-4o',
tools: [
{
type: 'mcp',
server_label: 'roxy_astrology',
server_url: 'https://roxyapi.com/mcp/astrology',
authorization: process.env.ROXY_API_KEY,
require_approval: 'never',
},
],
input: 'What is the Sun sign for someone born 1990-05-12 at 14:30 in New York?',
});~/.cursor/mcp.json:
{
"mcpServers": {
"roxy-astrology": {
"url": "https://roxyapi.com/mcp/astrology",
"headers": { "X-API-Key": "${env:ROXY_API_KEY}" }
}
}
}~/.codex/config.toml:
[mcp_servers.roxy-astrology]
url = "https://roxyapi.com/mcp/astrology"
env_http_headers = { "X-API-Key" = "ROXY_API_KEY" }- Add an AI Agent node and connect an MCP Client Tool node to its Tools input.
- Endpoint
https://roxyapi.com/mcp/astrology, Server Transport HTTP Streamable. - Authentication Header Auth, name
X-API-Key, value your key.
Add one MCP Client Tool node per domain. Use a secret key: publishable pk_ keys are refused on the MCP servers.
For clients that only start local servers over stdio. The package relays to the same hosted servers, so the tools, the answers and the billing are identical to Remote MCP.
ROXY_API_KEY=your-key npx -y @roxyapi/mcp| Variable | Default | Meaning |
|---|---|---|
ROXY_API_KEY |
none | Your RoxyAPI key |
ROXY_MCP_DOMAINS |
astrology |
Comma separated domains to load, for example astrology,vedic-astrology,location |
A container image builds from the Dockerfile in this repository: docker build -t astrology-mcp-server . then docker run -i --rm -e ROXY_API_KEY astrology-mcp-server.
One key reaches every domain. Each slug is a Remote MCP server at https://roxyapi.com/mcp/{slug} and a valid ROXY_MCP_DOMAINS value.
| Domain | Slug | Tools |
|---|---|---|
| Western Astrology | astrology |
39 |
| Vedic Astrology | vedic-astrology |
58 |
| Forecast | forecast |
5 |
| Human Design | human-design |
12 |
| Chinese Astrology | chinese-astrology |
16 |
| Feng Shui | feng-shui |
11 |
| Mesoamerican Astrology | mesoamerican-astrology |
18 |
| Vastu | vastu |
10 |
| Numerology | numerology |
20 |
| Kabbalah | kabbalah |
12 |
| Tarot | tarot |
10 |
| Biorhythm | biorhythm |
6 |
| Ayurveda | ayurveda |
8 |
| I-Ching | iching |
9 |
| Crystals and Healing Stones | crystals |
12 |
| Dreams | dreams |
5 |
| Angel Numbers | angel-numbers |
4 |
| Location and Timezone | location |
3 |
The Western astrology server covers natal charts, daily, weekly, monthly and yearly horoscopes, synastry, composite charts and compatibility scores, transits, progressions, solar arc, profections, solar, lunar and planetary returns, astrocartography, aspects, houses, fixed stars, asteroids and moon phases. The Vedic server adds the kundli birth chart, divisional charts, panchang, Vimshottari dasha from mahadasha down to sookshma, doshas, yogas, shadbala, ashtakavarga, KP astrology and kundli matching. Every tool carries a typed input schema, so the agent fills arguments correctly on the first call.
Planetary positions read the NASA JPL DE440 ephemeris directly and are verified against NASA JPL Horizons. The method and the test suite are published at roxyapi.com/methodology.
No. Remote MCP is the default: paste the URL and your key into any client that speaks Streamable HTTP. The npm package exists only for clients that start local stdio servers.
One subscription covers every domain, every endpoint and every MCP server, with flat monthly pricing and no per-domain add-ons. Plans are at roxyapi.com/pricing.
Responses are available in 10+ languages, including English, Hindi, Spanish, German, French, Portuguese, Russian, Turkish and Chinese.
- sdk-typescript, sdk-python, sdk-php, sdk-go, sdk-dotnet: typed SDKs for the same API
- ui: drop-in chart and reading components
- agent-plugin: RoxyAPI skill and docs server for Claude Code and Cursor
- astrology-ai-chatbot: an open source astrology chatbot built on these MCP servers
- astrology-api-openapi: the OpenAPI specification
- astrology-api-benchmark: the published accuracy benchmark
Full MCP guide: roxyapi.com/docs/mcp.
MIT