Gemini CLI astrology MCP setup

One command hands Gemini CLI the whole RoxyAPI reference as a searchable tool. Add your key and it runs live calculations while it writes the code. Five minutes, no local process.

Gemini CLI is the Google open-source terminal agent, and it reads MCP servers from settings.json. RoxyAPI runs as a Remote MCP server over Streamable HTTP, so the keyless docs server answers every question about endpoints, fields and SDK methods, and a per-domain server pulls a real natal chart, horoscope or tarot spread mid-build.

Step 1, the docs server (keyless)

gemini mcp add writes the entry for you. Register the docs server at user scope so it works in every project:

gemini mcp add --transport http --scope user roxy-docs https://roxyapi.com/mcp/docs

That is one tool, search_docs, over the entire reference: endpoints, request and response fields, SDK methods, auth, integration steps. No API key, documentation only, never a live calculation.

Start Gemini, run /mcp to confirm the server is connected, then ask in plain language:

Using roxy-docs, find the natal chart endpoint and show me how to call it with the TypeScript SDK.

Step 2, a domain server for live calls

Live calculations take your key in the X-API-Key header, one server per domain. Gemini CLI resolves $VAR and ${VAR} inside settings.json string values when it loads the file, so keep the key in your environment and write only the placeholder.

export ROXY_API_KEY="your-key-from-roxyapi.com/account?tab=keys"

gemini mcp add --transport http --scope user roxy-astrology \
  https://roxyapi.com/mcp/astrology --header 'X-API-Key: $ROXY_API_KEY'

{
  "mcpServers": {
    "roxy-docs": {
      "httpUrl": "https://roxyapi.com/mcp/docs"
    },
    "roxy-astrology": {
      "httpUrl": "https://roxyapi.com/mcp/astrology",
      "headers": { "X-API-Key": "$ROXY_API_KEY" }
    }
  }
}

export ROXY_API_KEY="your-key-from-roxyapi.com/account?tab=keys"

for p in astrology vedic-astrology forecast human-design chinese-astrology feng-shui mesoamerican-astrology vastu numerology kabbalah tarot biorhythm ayurveda iching crystals dreams angel-numbers location; do
  gemini mcp add --transport http --scope user "roxy-$p" \
    "https://roxyapi.com/mcp/$p" --header 'X-API-Key: $ROXY_API_KEY'
done

Get your API key, or mint another there.

Step 3, point Gemini at the truth sources

Gemini reads GEMINI.md from your project, and ~/.gemini/GEMINI.md globally, as standing instructions on every prompt. Drop this in:

## RoxyAPI
- Search https://roxyapi.com/mcp/docs (tool: search_docs) before writing any RoxyAPI call. No MCP in this context? Fetch https://roxyapi.com/llms.txt instead.
- Read https://roxyapi.com/AGENTS.md in full before the first call: auth, the location rule, request body shapes, the error contract, the SDK for this language.
- Print request and response fields with jq from https://roxyapi.com/api/v2/openapi.json before using an endpoint, with the jq recipe in https://roxyapi.com/AGENTS.md. Generate types from that spec, never by hand.
- Base URL https://roxyapi.com/api/v2. Auth is the X-API-Key header read from ROXY_API_KEY, server side only.
- Every chart, horoscope, panchang, dasha and compatibility call needs latitude, longitude and timezone from GET /location/search?q={city}. Never ask a person for coordinates.
- A 200 is clean JSON with no wrapper. Errors are { error, code, doc_url }, and a 400 carries issues[]. Retry only 429 and 5xx.
- Add ?lang= for en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant.

On a repo shared with other agents, keep the block in AGENTS.md instead and add that filename to the context list so Gemini loads it too. Every SDK ships the same playbook inside the installed package:

{
  "context": { "fileName": ["AGENTS.md", "GEMINI.md"] }
}

Step 4, copy the prompt for what you are building

Every app prompt lives on one page: AI prompts. Adding a feature to a repo you already have is the Add RoxyAPI to an existing app prompt; a whole app from a blank repository is Astrology Birth Chart App or the domain prompt beside it.

Frequently asked questions