RoxyAPI
Quick StartAGENTS.mdSDKMCP SetupFree StartersAPI Playground
  1. Docs
  3. Build With Roxy
  5. Antigravity

Antigravity, connect Roxy as an MCP server

Register Roxy once, then ask Gemini 3 Pro to build spiritual-data features in natural language. Time to ship: 5 minutes.

Antigravity is the Google agentic IDE built around Gemini 3 Pro. It has a VS Code-style editor, an Agent Manager dashboard for long-running coding tasks, deep browser connectivity so agents can test the apps they build, and native Model Context Protocol (MCP) support.

Once Roxy is registered as an MCP server, every Gemini-powered agent in Antigravity can call all 130+ Roxy endpoints across astrology, Vedic astrology, tarot, numerology, dreams, angel numbers, I Ching, crystals, biorhythm, and location as auto-discovered tools. No manual function definitions, no glue code.

What you can build with this

  • Natal chart features generated directly inside your project code
  • Tarot readers, kundli generators, daily horoscope pages with working data
  • Multi-agent workflows that geocode a city, fetch a chart, and write the UI
  • Vedic features (KP, Gun Milan, panchang) with sub-lord precision
  • AI-driven prototypes you can run and test without leaving the editor

What you need, 30 seconds

  1. A Roxy API key. Get one on the pricing page.
  2. Antigravity installed from antigravity.google.

Step 1, add Roxy as an MCP server

Antigravity stores MCP servers in ~/.gemini/antigravity/mcp_config.json. Edit via the MCP store UI or directly.

{
  "mcpServers": {
    "roxy-astrology": {
      "serverUrl": "https://roxyapi.com/mcp/astrology",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

That is the minimum config for Western astrology. To add all ten Roxy domains, add one entry per product (astrology, vedic-astrology, tarot, numerology, iching, dreams, crystals, angel-numbers, biorhythm, location). Save. Antigravity reloads the servers automatically.

Or do it via the store UI.

  1. Open the "..." dropdown at the top of the agent panel.
  2. Click Manage MCP Servers.
  3. Click View raw config. Antigravity opens mcp_config.json.
  4. Paste the JSON above, adjust the key, save.

The field name is serverUrl in Antigravity (not url like in some other MCP clients). This is for Streamable HTTP, which is what Roxy uses. No local process, no Docker, no stdio.

For all 10 Roxy products at once:

{
  "mcpServers": {
    "roxy-astrology":       { "serverUrl": "https://roxyapi.com/mcp/astrology",       "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-vedic-astrology": { "serverUrl": "https://roxyapi.com/mcp/vedic-astrology", "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-tarot":           { "serverUrl": "https://roxyapi.com/mcp/tarot",           "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-numerology":      { "serverUrl": "https://roxyapi.com/mcp/numerology",      "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-iching":          { "serverUrl": "https://roxyapi.com/mcp/iching",          "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-dreams":          { "serverUrl": "https://roxyapi.com/mcp/dreams",          "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-crystals":        { "serverUrl": "https://roxyapi.com/mcp/crystals",        "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-angel-numbers":   { "serverUrl": "https://roxyapi.com/mcp/angel-numbers",   "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-biorhythm":       { "serverUrl": "https://roxyapi.com/mcp/biorhythm",       "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-location":        { "serverUrl": "https://roxyapi.com/mcp/location",        "headers": { "X-API-Key": "YOUR_KEY" } }
  }
}

Antigravity stores this file in plain text on disk under your home directory. Treat it as a secret file. Antigravity does not currently support ${env:VAR} interpolation in headers, so the key is inlined directly.

Step 2, verify the connection

Open any chat with the Antigravity agent and ask:

What MCP tools are available?

The agent should list every Roxy tool it discovered, grouped by product (roxy-astrology, roxy-tarot, etc.).

If nothing appears:

  • Open Agent Settings with Cmd+, (Mac) or Ctrl+, (Windows/Linux).
  • Navigate to the Customizations tab.
  • Find your roxy-* server entries and check for error messages.
  • Confirm the API key has no leading or trailing whitespace and no surrounding quotes.

As an out-of-band smoke test, curl the underlying endpoint:

curl "https://roxyapi.com/api/v2/astrology/horoscope/aries/daily" \
  -H "X-API-Key: YOUR_KEY"

If that prints JSON, the key is good and any error is a config issue. If it returns 401, check your key at your account page.

Step 3, first prompt to try

Once Roxy is connected, the agent picks the right tool for each question. Try one of these in the agent panel:

  • Build a daily horoscope page in Next.js. Use the Roxy MCP tools to fetch the actual horoscope.
  • Create a tarot reader using the three-card spread tool from roxy-tarot.
  • Build a Vedic kundli generator. Use roxy-vedic-astrology to compute the chart with nakshatra and Vimshottari Dasha.
  • Look up the Life Path number for someone born 1990-05-12 using the numerology MCP.
  • Generate the kundli for someone born July 15 1990 at 2:30 PM in Mumbai. Geocode the city first.

The agent inspects the tool schemas, calls the right endpoint, and integrates the result into the code it writes.

Add project context for better output

Agentic IDEs write better code when you give them short project context. Drop this into your initial prompt or save as a project rule.

We use Roxy API for spiritual data (astrology, tarot, numerology, etc.).
- Base URL: https://roxyapi.com/api/v2
- Auth: X-API-Key header (already configured via the MCP server)
- Prefer the MCP tools over raw fetch. They auto-discover endpoints.
- If you need raw fetch, read the key from process.env.ROXY_API_KEY (server-side only)
- Always call /location/search first when any endpoint needs coordinates
- IANA timezone strings are DST-correct. Prefer them over decimal offsets.
- Reference: https://roxyapi.com/llms.txt for the full endpoint list
- Tighter playbook (Rule 0, common tasks, body shapes, gotchas): https://roxyapi.com/AGENTS.md

For a tighter execution context, point Antigravity at the site-level AGENTS.md directly. It is the 120-line blind-agent execution playbook with all common task body shapes inline.

Gotchas

  • serverUrl, not url. Antigravity uses serverUrl. Cursor uses url. Claude Code uses url inside .mcp.json. They are different.
  • No env interpolation yet. Antigravity does not read ${env:VAR} in headers. The key lives in the config file. Do not commit it.
  • Geocode first for chart endpoints. Natal chart, kundli, panchang, compatibility, synastry, transits all require latitude, longitude, and timezone. Tell the agent to call roxy-location first.
  • X-API-Key not Authorization: Bearer. Some no-code platforms default to Bearer. Roxy uses a custom header.

What to build next