Skip to content
RoxyAPI
Set up your AI agentGet startedAPI ReferenceSDKRemote MCPFree Templates
  1. Docs
  3. Build With RoxyAPI
  5. Antigravity

Antigravity astrology MCP setup

One config block hands every Antigravity agent the whole RoxyAPI reference as a searchable tool. Add your key and they run live calculations while they write the code. Five minutes, no local process.

Antigravity is the Google agentic IDE, with a VS Code-style editor, an Agent Manager for long-running tasks, browser connectivity so agents can test what they build, and MCP support in the editor, the CLI and the SDK. 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)

Antigravity keeps MCP servers in ~/.gemini/config/mcp_config.json globally, or .agents/mcp_config.json inside a workspace. Open the global file from the ... menu at the top of the agent side panel, then MCP Servers, Manage MCP Servers, View raw config, and add:

{
  "mcpServers": {
    "roxy-docs": {
      "serverUrl": "https://roxyapi.com/mcp/docs"
    }
  }
}

Remote servers must use serverUrl. 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. Save, 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:

{
  "mcpServers": {
    "roxy-docs":                   { "serverUrl": "https://roxyapi.com/mcp/docs" },
    "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-forecast":               { "serverUrl": "https://roxyapi.com/mcp/forecast",               "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-human-design":           { "serverUrl": "https://roxyapi.com/mcp/human-design",           "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-chinese-astrology":      { "serverUrl": "https://roxyapi.com/mcp/chinese-astrology",      "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-feng-shui":              { "serverUrl": "https://roxyapi.com/mcp/feng-shui",              "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-mesoamerican-astrology": { "serverUrl": "https://roxyapi.com/mcp/mesoamerican-astrology", "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-vastu":                  { "serverUrl": "https://roxyapi.com/mcp/vastu",                  "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-numerology":             { "serverUrl": "https://roxyapi.com/mcp/numerology",             "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-kabbalah":               { "serverUrl": "https://roxyapi.com/mcp/kabbalah",               "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-tarot":                  { "serverUrl": "https://roxyapi.com/mcp/tarot",                  "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-biorhythm":              { "serverUrl": "https://roxyapi.com/mcp/biorhythm",              "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-ayurveda":               { "serverUrl": "https://roxyapi.com/mcp/ayurveda",               "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-iching":                 { "serverUrl": "https://roxyapi.com/mcp/iching",                 "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-crystals":               { "serverUrl": "https://roxyapi.com/mcp/crystals",               "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-dreams":                 { "serverUrl": "https://roxyapi.com/mcp/dreams",                 "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-angel-numbers":          { "serverUrl": "https://roxyapi.com/mcp/angel-numbers",          "headers": { "X-API-Key": "YOUR_KEY" } },
    "roxy-location":               { "serverUrl": "https://roxyapi.com/mcp/location",               "headers": { "X-API-Key": "YOUR_KEY" } }
  }
}

258+ tools in total. Start with the two or three domains you are actually building on: every connected tool is a definition in front of the model on every turn. Get your API key, or mint another there.

Antigravity does not interpolate environment variables in headers, so the key is written into the file in plain text. Treat mcp_config.json as a secret file and never commit a workspace .agents/mcp_config.json that carries one.

Step 3, point the agents at the truth sources

Workspace rules live in .agents/rules/, one file per rule, and global rules in ~/.gemini/GEMINI.md. Create .agents/rules/roxyapi.md:

## 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. Prefer the MCP tools over a raw fetch.
- 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.

Rule files cap at 12,000 characters each, so keep it to the block above.

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 chat app whose model calls live calculations as tools is AI Astrology Chatbot.

Frequently asked questions

serverUrl or url for the RoxyAPI server in Antigravity?

serverUrl, always. Antigravity does not support the legacy url or httpUrl fields for remote MCP connections, so a config copied from Cursor or Gemini CLI leaves the server listed and never connected. Everything else about the entry is the same.

Where does Antigravity keep mcp_config.json?

Globally at ~/.gemini/config/mcp_config.json, and per project at .agents/mcp_config.json in the workspace. The older ~/.gemini/antigravity/ folder is where MCP OAuth tokens are cached, not where servers are declared, so editing a file there changes nothing.

How do I keep the RoxyAPI key safe in Antigravity?

There is no environment variable interpolation in headers, so the key sits in the config file in plain text. Keep the keyed servers in the global ~/.gemini/config/mcp_config.json rather than a workspace file, and never commit a .agents/mcp_config.json containing one.

The agent is not seeing my RoxyAPI tools. What now?

Open the MCP list from the ... menu at the top of the agent panel, or /mcp in the CLI, and read the server status and the connection log there. Confirm the key has no surrounding quotes or trailing whitespace. If the list is simply crowded, set disabledTools on a server to withhold the tools you do not need, or disabled to switch a whole server off without deleting it.

Is RoxyAPI free to try with Antigravity?

The docs server at https://roxyapi.com/mcp/docs needs no key and returns documentation, so the agent writes correct code from the first prompt. Live calculations across the domains need your API key, billed flat, 1 request to 1 quota unit, every domain included.