Antigravity + Occult API

The MCP server exposes 309 astrology endpoints to the Antigravity agent as callable tools. Rather than describing an API and hoping the model writes a correct request, it searches the catalogue, reads the real request schema, and makes the call — so the numbers in its answer came from the ephemeris rather than from its training data.

Searching and reading schemas costs nothing. Only a successful call_endpoint spends a credit, and failed calls are free.

Create one in the dashboard. It looks like yt_live_… and carries your credit balance, so treat it as a password: never in client-side code, never committed.

Create an API key

Open ~/.gemini/antigravity/mcp_config.json (Windows: %USERPROFILE%\.gemini\antigravity\mcp_config.json), creating it if it does not exist, and add:

{
  "mcpServers": {
    "occult-api": {
      "command": "npx",
      "args": ["-y", "occult-api-mcp"],
      "env": { "OCCULT_API_KEY": "yt_live_your_key_here" }
    }
  }
}

If you would rather not edit the file by hand, the same thing lives at Agent side panel → MCP Servers → Manage MCP Servers → View raw config.

Replace yt_live_your_key_here with your real key. You do not need to install anything else — npx fetches the server on first run.

Ask the Antigravity agent:

List the tools you have from the occult-api server.

You should get back five tools:

• search_endpoints
• describe_endpoint
• call_endpoint
• get_panchanga
• check_account

If the list is empty the server has not started. The usual cause is the config file being in the right place with the wrong shape, so check the key name above before anything else.

Using the occult-api MCP server, compare the D1 and D9 charts for this birth data and tell me which planets are vargottama.

It should call the API rather than answer from memory. If the reply arrives instantly and contains no tool call, the agent has answered from training data — say “use the occult-api tools” and it will.

• Antigravity keeps its config under `~/.gemini/`, not under a folder named for the editor — worth knowing if you go looking for it by name.
• For REMOTE servers Antigravity expects `serverUrl` where Cursor and VS Code use `url`. It does not affect the setup below, which runs the server locally over stdio, but it is the thing that breaks a snippet copied from elsewhere.
• A workspace-local config at `.agents/mcp_config.json` takes precedence over the global one.

The endpoints are ordinary HTTP. Nothing on this page is required to use them:

curl -X POST https://api.occultapi.com/api/astro/panchanga/ \
  -H 'X-API-Key: yt_live_your_key_here' \
  -H 'Content-Type: application/json' \
  -d '{
    "date_time": "2026-09-17T06:00:00+05:30",
    "latitude": 26.9124,
    "longitude": 75.7873,
    "timezone_as_float": 5.5,
    "keys": ["tithi", "nakshatra", "yogam", "karana"]
  }'

Note the keys array: four calculations in one request, charged as one credit. Calling four times costs four.