MCP Astrology Server: 9 Spiritual Domains, 123+ AI Tools [2026]

About the author: Torsten Brinkmann is an Astrologer and Developer Advocate with 16 years of experience in Western astrology and software engineering. He holds an M.Sc. in Computer Science from TU Munich and has contributed to open-source ephemeris and chart rendering libraries. His writing addresses both the astronomical mathematics behind natal charts and the developer integration patterns for astrology APIs.

AI agents are getting smarter, but most are still blind to spiritual and metaphysical data. An agent that can search the web and write code still cannot cast a birth chart, draw tarot cards, interpret dream symbols, or look up crystal healing properties. The Model Context Protocol changes that. MCP gives agents a standardized way to discover and call external tools. The question is: which tools do you give your agent?

Most MCP servers in the spiritual data space cover a single domain. You get astrology tools, or nothing. If you want your agent to combine a birth chart reading with a tarot spread and a dream symbol lookup in one conversation, you need multiple providers, multiple credentials, and multiple configuration blocks. That is credential sprawl, and it kills agent development velocity.

Roxy solves this with 9 dedicated MCP servers, 123 tools, and one API key.

Why multi-domain MCP matters for AI agents

Single-domain MCP servers handle one vertical well. An astrology-only server might expose 100+ tools for birth charts, horoscopes, transits, and compatibility. That is useful for a pure astrology chatbot.

But the most compelling AI agent experiences cross domain boundaries. A user asks about their week ahead. The agent could pull their daily horoscope based on sun sign, then draw a tarot card for additional guidance, check their personal year number from numerology, and surface a relevant dream symbol if the user mentions a recurring dream. That multi-domain conversation is impossible with a single-domain MCP server.

With Roxy, your agent discovers 123 tools across 9 domains through the same authentication mechanism. No credential juggling. No separate billing accounts. No inconsistent response formats.

Ready to build this? Roxy MCP gives your AI agent access to 9 spiritual intelligence domains under one key. See pricing.

How many tools per domain: the full breakdown

Each Roxy domain has its own MCP server at a dedicated URL. Every endpoint in that domain becomes a callable tool. Here is the current count from the live MCP servers:

Compare this to what exists elsewhere. The largest single-domain MCP server in the astrology space offers 109 tools, but covers astrology alone. Another provider ships 21 tools via a local npm package, limited to astrology. Nobody else covers tarot, I-Ching, dreams, crystals, or angel numbers through MCP. Those 5 domains are exclusive to Roxy.

How to set up Roxy MCP servers

Every Roxy MCP server is a remote Streamable HTTP endpoint. No local processes, no Docker containers, no npm packages to install. You point your agent at a URL, pass your API key, and the agent auto-discovers all available tools.

The base URL pattern is https://roxyapi.com/mcp/{product-slug}. You need an API key from the checkout page.

VS Code (GitHub Copilot, Cline, Continue)

Create or edit .vscode/mcp.json in your workspace:

{
  "servers": {
    "roxy-astrology-api": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/astrology-api",
      "headers": {
        "X-API-Key": "your_api_key_here"
      }
    },
    "roxy-tarot-api": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/tarot-api",
      "headers": {
        "X-API-Key": "your_api_key_here"
      }
    },
    "roxy-numerology-api": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/numerology-api",
      "headers": {
        "X-API-Key": "your_api_key_here"
      }
    }
  }
}

Reload VS Code after saving. Add more domains by repeating the block with a different slug (vedic-astrology-api, iching-api, dreams-api, crystals-api, angel-numbers-api, location-api).

Claude Desktop

Edit your claude_desktop_config.json:

{
  "mcpServers": {
    "roxy-astrology-api": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/astrology-api",
      "headers": {
        "X-API-Key": "your_api_key_here"
      }
    },
    "roxy-tarot-api": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/tarot-api",
      "headers": {
        "X-API-Key": "your_api_key_here"
      }
    },
    "roxy-dreams-api": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/dreams-api",
      "headers": {
        "X-API-Key": "your_api_key_here"
      }
    }
  }
}

Config location: macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json. Restart Claude Desktop after saving.

Claude Code

Add servers via CLI:

claude mcp add-json roxy-astrology-api '{"type":"http","url":"https://roxyapi.com/mcp/astrology-api","headers":{"X-API-Key":"your_api_key_here"}}'

claude mcp add-json roxy-tarot-api '{"type":"http","url":"https://roxyapi.com/mcp/tarot-api","headers":{"X-API-Key":"your_api_key_here"}}'

claude mcp add-json roxy-iching-api '{"type":"http","url":"https://roxyapi.com/mcp/iching-api","headers":{"X-API-Key":"your_api_key_here"}}'

Add --scope user to make servers available across all projects. Run claude mcp list to verify.

Cursor

Cursor uses the same .vscode/mcp.json format shown above. Create the file in your workspace root and reload the editor.

A real multi-domain agent conversation

Here is what a multi-domain spiritual AI agent looks like in practice. The user starts a single conversation and the agent pulls from three different domains without any manual switching.

User: I was born March 15, 1990 at 2:30 PM in Berlin. Can you do a quick birth chart, draw three tarot cards for my week, and tell me what it means that I keep dreaming about water?

Agent workflow:

1. Calls post_natal_chart from the astrology MCP server with date, time, and coordinates for Berlin
2. Reads the natal chart response: Sun in Pisces, Moon in Scorpio, Ascendant in Leo. Notes the heavy water element presence.
3. Calls post_spreads_three_card from the tarot MCP server for a past/present/future reading
4. Gets The Moon (past), Ace of Cups (present), The Star (future). Notes the water symbolism in all three cards.
5. Calls get_symbols_id from the dreams MCP server with id "water" for dream interpretation data
6. Synthesizes everything: "Your birth chart is heavily water-influenced with Sun in Pisces and Moon in Scorpio. Your tarot draw reinforces this with The Moon, Ace of Cups, and The Star, all cards connected to water energy and intuition. Your recurring water dreams align with your natal water dominance. Water in dreams typically signifies emotions surfacing from the subconscious, which makes sense given your Pisces/Scorpio emphasis on emotional depth."

That cross-domain synthesis is the value. No single-domain tool can connect a natal chart to tarot symbolism to dream analysis. The agent needs access to all three domains, and MCP makes that access automatic.

Remote HTTP MCP vs local stdio servers

MCP servers run in two modes: local stdio and remote HTTP. The difference matters for production deployments.

Local stdio means you install a package (usually via npm or pip), and the MCP client spawns it as a child process on your machine. The client and server communicate through standard input/output streams. This works for development but creates operational overhead: you need Node.js or Python installed, the process consumes local resources, and every machine that runs your agent needs the same setup.

Remote HTTP (what Roxy uses) means the server runs at a URL. Your agent sends HTTP POST requests to the server endpoint. No local installation. No child processes. No dependency management. The server handles computation, caching, and scaling.

For AI agent deployments, remote HTTP is simpler. You configure a URL and an API key. That configuration works identically on a laptop, a CI server, a cloud function, or a multi-agent orchestration framework. The 123 tools behind those URLs run on infrastructure verified against NASA JPL Horizons, backed by 1,950 tests including 828 gold standard tests cross-referenced against authoritative sources.

Roxy implements MCP Specification 2025-11-25 (latest stable) using Streamable HTTP transport. Tool discovery (tools/list) is free. Tool calls (tools/call) count as billable API requests against your monthly quota.

Building a spiritual AI agent with the API

Beyond MCP, every Roxy endpoint is also available as a standard REST API. Here is a curl example calling the Western astrology natal chart endpoint:

curl -X POST https://roxyapi.com/api/v2/astrology/natal-chart \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "date": "1990-03-15",
    "time": "14:30:00",
    "latitude": 52.52,
    "longitude": 13.405,
    "timezone": 1
  }'

The response includes planets with signs, degrees, houses, aspects, element distribution, and interpretations. That same data is what your agent receives when it calls the post_natal_chart MCP tool. MCP wraps the REST API, so every endpoint documented in the API reference is also an MCP tool.

The TypeScript SDK provides full type safety:

import Roxy from "@roxyapi/sdk";

const roxy = new Roxy({ apiKey: "your_api_key_here" });

const chart = await roxy.astrology.getNatalChart({
  date: "1990-03-15",
  time: "14:30:00",
  latitude: 52.52,
  longitude: 13.405,
  timezone: 1,
});

Whether you use MCP, REST, or the SDK depends on your architecture. MCP is ideal for AI agents that need to auto-discover tools. REST and SDK are better for deterministic application logic where you know exactly which endpoints to call.

Frequently Asked Questions

Q: Can one MCP server cover multiple spiritual domains? A: Each Roxy domain has its own MCP server with a dedicated URL. You configure multiple servers (one per domain) in your MCP client, but they all use the same API key and the same subscription. Your agent discovers tools from all configured servers simultaneously.

Q: How many MCP tools can an AI agent realistically use in one conversation? A: Most MCP clients can handle hundreds of tools without issues. Claude Desktop, VS Code, and Cursor all support multiple MCP servers with combined tool counts well above 100. The agent selects relevant tools based on the user query, so having 123 tools available does not create confusion. It creates capability.

Q: What is the difference between remote HTTP MCP and local stdio MCP servers? A: Local stdio requires installing a package and spawning a process on your machine. Remote HTTP (what Roxy uses) runs at a URL with no local dependencies. Remote is simpler for production: same config works everywhere, no version mismatches, no child process management. Tool calls are HTTPS requests with sub-50ms latency.

Q: Is there an MCP server for tarot, I-Ching, or dream interpretation? A: Roxy is the only provider offering MCP servers for tarot (10 tools), I-Ching (9 tools), dreams (5 tools), crystals (12 tools), and angel numbers (4 tools). These domains are not available through any other MCP server.

Q: How much does multi-domain MCP access cost? A: Every Roxy subscription includes all 9 domains. The Starter plan at $39/month covers 5,000 requests across all domains. That works out to $4.33 per domain per month. Getting equivalent coverage from separate single-domain providers would cost $84 to $200+ per month.

One key, nine domains, 123 tools

The MCP ecosystem is growing fast, but spiritual and metaphysical data remains underserved. Most providers cover astrology and stop there. Roxy covers 9 domains with 123 tools under a single API key: Western astrology, Vedic astrology, tarot, numerology, I-Ching, dreams, crystals, angel numbers, and location data.

If you are building an AI agent, chatbot, or multi-agent system that needs spiritual intelligence, start with Roxy MCP. One key. Nine servers. 123 tools. Get your API key and connect your first MCP server in under 5 minutes.