Use DNSai in Gemini

Google's current path is Antigravity (the Gemini CLI was retired 2026-06-18). Both read a JSON config with a Bearer header.

✓ Free key works — header in the config

Antigravity (current) · one domain per request

↓ Download this guide (.md) drop it into your repo or paste it into your assistant

Set it up

Antigravity CLI / IDE (current path)

Edit ~/.gemini/antigravity/mcp_config.json (or Agent panel → MCP Servers → View raw config). The remote URL key is serverUrl.

{
  "mcpServers": {
    "dnsai": {
      "serverUrl": "https://mcp.dnsai.com/mcp",
      "headers": { "Authorization": "Bearer dk_free_xxxxxxxx" }
    }
  }
}

Gemini CLI (legacy — retired 2026-06-18)

For grandfathered setups only: ~/.gemini/settings.json, key httpUrl for Streamable HTTP (url is SSE). Prefer Antigravity above.

{
  "mcpServers": {
    "dnsai": {
      "httpUrl": "https://mcp.dnsai.com/mcp",
      "headers": { "Authorization": "Bearer dk_free_xxxxxxxx" }
    }
  }
}

Your key. Both configs take a Bearer header, so the free key works. Get a free key for 100/day, or drop headers for anonymous.

Verify it works

Ask the agent:

Use dnsai to look up WHOIS for openai.com

Every result ends with a plain-English summary, a source link on dnsai.com, and your remaining quota.

Troubleshooting

Three different URL keys across tools: Antigravity serverUrl, Gemini CLI httpUrl (Streamable HTTP), and url = SSE. Using the wrong one is the #1 failure.
Gemini Code Assist's MCP can get stuck "Connecting" — steer to Antigravity.

Sources: Antigravity MCP install · Gemini CLI MCP docs

Need bulk, multi-domain, or the full API?

Pro unlocks bulk / multi-domain lookups; Enterprise adds large-scale scanning and the full programmatic API.

See plans & pricing →