RoxyAPI
Quick StartSDKMCP SetupFree StartersAPI PlaygroundPricing
  1. Docs
  3. Build With Roxy
  5. Antigravity

Antigravity

Antigravity is Google's agentic IDE built around Gemini 3 Pro. It has a VS Code-style editor, an Agent Manager dashboard for orchestrating long-running coding tasks, deep browser connectivity for letting agents test the web apps they build, and native Model Context Protocol (MCP) support for connecting to external tools, databases, and APIs.

This guide walks you through connecting RoxyAPI to Antigravity as an MCP server. Once connected, every Gemini-powered agent in Antigravity can call all 130+ RoxyAPI endpoints across astrology, Vedic astrology, tarot, numerology, dream interpretation, angel numbers, I-Ching, crystals, biorhythm, and location as auto-discovered tools — no manual function definitions, no glue code.

Add RoxyAPI as an MCP server

Roxy provides a remote MCP server per product domain. Pick your product and get the exact config block on the MCP Setup page — select the Antigravity tab. Or follow the walkthrough below.

Antigravity stores MCP server configuration in a single JSON file at ~/.gemini/antigravity/mcp_config.json. You can either edit it directly through the MCP store UI inside Antigravity, or open the file in any editor.

  1. Open the "..." dropdown at the top of the editor's agent panel
  2. Click Manage MCP Servers
  3. Click View raw config — Antigravity opens ~/.gemini/antigravity/mcp_config.json in the editor
  4. Add the RoxyAPI server entry from the example below
  5. Save the file
  6. Antigravity reloads the MCP servers automatically

Option B: edit the file directly

Open ~/.gemini/antigravity/mcp_config.json in any editor and add the entry below. Antigravity picks up the change on the next reload.

Configuration

For a single product domain (Western Astrology):

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

The field name is serverUrl in Antigravity (not url like in some other MCP clients). This is for Streamable HTTP transport, which is what RoxyAPI's remote MCP servers use. No local process, no Docker, no stdio.

For all 10 RoxyAPI product domains at once, add an entry per product:

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

Antigravity stores this file in plain text on disk under your home directory. The API key is stored as a literal string in the config. If you share your machine or back up your home directory to a remote location, treat the config file like any other secret. Antigravity does not currently support ${env:VAR} interpolation in headers the way Cursor does, so you cannot reference an environment variable inline.

Verify the connection

After saving the config:

  1. Open any chat with the Antigravity agent
  2. Ask: "What MCP tools are available?"
  3. The agent should list every RoxyAPI tool it discovered, grouped by product (roxy-astrology-api, roxy-tarot-api, etc.)

If the tools do not appear:

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

Use RoxyAPI in an Antigravity agent task

Once connected, the agent picks the right tool automatically based on your request. Examples:

  • "Build a daily horoscope page in Next.js. Use the RoxyAPI MCP tools to fetch the actual horoscope."
  • "Create a tarot card reader using the three-card spread tool from roxy-tarot-api."
  • "I need a Vedic kundli generator. Use roxy-vedic-astrology-api 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 server."

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

Add project context for better generation

Antigravity (like Cursor and Claude Code) generates better code when you give it project context. For RoxyAPI projects, paste this short context block into your initial prompt or save it as a project rule:

We use RoxyAPI 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)
- Use the MCP tools rather than raw fetch when possible — they auto-discover endpoints
- For raw fetch fallback, the API key must be read from process.env.ROXY_API_KEY (server-side only, never expose to browser)
- Reference: https://roxyapi.com/llms.txt for the full endpoint list

Test your API key outside Antigravity first

Before troubleshooting an Antigravity MCP issue, confirm your key works on its own. Open a terminal and run:

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 you see in Antigravity is a config issue, not a RoxyAPI issue. If it returns 401, the key is wrong. Check at your account page.

Where to go next

  • MCP Setup — full reference for every MCP-compatible client (VS Code, Claude Code, Claude Desktop, OpenAI Agents, Gemini Agents, and now Antigravity)
  • Interactive API reference — Scalar-powered live docs for every endpoint, with a pre-filled test key. Useful when you want to inspect tool parameters before asking the agent to use them
  • AI prompt recipes — ready-to-paste prompts for tarot, numerology, Vedic astrology, dreams, and more. Each one tested to produce a working app on the first try in agentic IDEs
  • Function calling guide — for non-MCP agents that need manual tool definitions
  • Starter apps — clone a working Next.js or React Native template and let Antigravity extend it with new features
  • Pricing — RoxyAPI plans start at 5,000 requests per month