Best MCP Servers for Google Antigravity in 2026

Google Antigravity is growing fast enough that Firecrawl and Bright Data have each shipped their own setup guide for it — but neither has published the head-to-head comparison a buyer actually wants. This one runs that comparison, sourced from Antigravity's own docs and each vendor's own guide, not paraphrased from a listicle.

Antigravity's MCP config

Antigravity reads MCP server definitions from a JSON file at ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json at your project root (workspace-scoped, takes precedence over global). The root key is mcpServers, and the same file format applies whether you're configuring Antigravity 2.0, the Antigravity IDE, or the Antigravity CLI.

Antigravity supports two server shapes:

• Command-based (local): { "command": "...", "args": [...], "env": {...}, "cwd": "..." } — runs a local process.
• Remote: { "serverUrl": "...", "headers": {...} } — points at a hosted endpoint. Both shapes also accept disabled (boolean) and disabledTools (array) toggles, and the remote shape additionally supports authProviderType: "google_credentials" for ADC or an oauth block (clientId/clientSecret).

The gotcha worth flagging up front: Antigravity's config directory is named ~/.gemini/, the same prefix Gemini CLI uses, but the two schemas aren't identical. Gemini CLI splits remote servers into url (SSE) vs httpUrl (HTTP-streaming) — Antigravity's own docs state plainly that "legacy fields like url or httpUrl are not supported," using serverUrl for every remote server instead. Copy a Gemini CLI remote-server block into Antigravity as-is and it won't connect.

You don't have to hand-edit the file, either: an MCP Store handles installs through a UI — Antigravity 2.0: Settings → Customizations → Installed MCP Servers; Antigravity IDE: the Agent side panel's … menu → MCP Servers; Antigravity CLI: the /mcp command opens an interactive MCP manager.

What to evaluate

• Generic crawl (any URL → markdown) vs. structured platform data (named sites → JSON).
• Local command-based server vs. a remote HTTP server you don't have to run yourself.
• Tool count and what it actually covers, not just the headline number.
• Pricing model and whether a failed request still gets billed.

The contenders

Firecrawl MCP: zero-setup, but keyless mode is limited

Firecrawl's own Antigravity quickstart points readers at its hosted endpoint — serverUrl: "https://mcp.firecrawl.dev/v2/mcp", nothing else required. That gets you firecrawl_search, firecrawl_scrape, and firecrawl_parse with no API key, but keyless access shares its rate limit with everyone else on your public IP, and it's a narrower slice of Firecrawl's tools than the full local npx -y firecrawl-mcp server used elsewhere in this series. Choose it when the job is quick, occasional crawling of arbitrary sites and you don't want to manage a key.

Bright Data: anti-bot scale across 40+ named platforms

Bright Data publishes its own Antigravity guide with a command-based entry: npx @brightdata/mcp, API_TOKEN under env, and "PRO_MODE": "true" to unlock the full 70+-tool set (the default is a smaller Rapid-mode tier). Coverage spans named e-commerce, social, business, and finance platforms. Choose it when anti-bot reliability on hard, named targets is the actual constraint.

Zyte: not currently available for Antigravity

Worth stating plainly rather than skipping: Zyte's two Claude-adjacent products (the Claude Code plugin and the GitHub-Copilot-specific Web Scraping Copilot VS Code extension) are each locked to one client, and neither connects to Antigravity. If your stack is Antigravity-first, Zyte isn't currently in the running here.

Crawlora: structured JSON across 155 platform groups, full tool set, no local process

Crawlora's MCP server connects to Antigravity the same way Firecrawl's default does — a serverUrl-based remote entry — but at the full tool count rather than a keyless-limited subset. Point serverUrl at https://mcp.crawlora.net/mcp with the API key under headers.Authorization (Bearer <key>):

{
  "mcpServers": {
    "crawlora": {
      "serverUrl": "https://mcp.crawlora.net/mcp",
      "headers": { "Authorization": "Bearer <CRAWLORA_API_KEY>" }
    }
  }
}

1,398 tools across search, maps, e-commerce, social, finance, travel, jobs, media, app stores, and reviews, normalized JSON, pay-on-success billing, 2,000 free credits/month with no card. Choose it for structured records from named platforms without maintaining a parser or a local process.

How to choose, by job

• You need occasional, zero-setup crawling of arbitrary websites → Firecrawl MCP's keyless default.
• You need reliable extraction from specific hard, named platforms at scale → Bright Data.
• You need structured JSON from named platforms without running a local process, billed only on success → Crawlora MCP.
• You specifically want Zyte's Scrapy-generation workflow → you'll need Claude Code or GitHub Copilot for now, not Antigravity.

Add structured web data to Antigravity

1,398 tools across 155 platform groups, one API key, billed only on success. 2,000 free credits a month, no card.

Set up Crawlora MCPBrowse the API catalog

Sources

Related reading

• Best MCP Servers for Gemini CLI in 2026: the closely-related client with a different remote-server field — read this if you're deciding between the two.
• Best MCP Servers for Warp in 2026 · Best MCP Servers for JetBrains IDEs in 2026.
• Best MCP Servers for GitHub Copilot in 2026 · Best MCP Servers for Windsurf in 2026.
• Best Web Scraping MCP Servers & Skills for Claude Code in 2026.
• Crawlora vs Firecrawl · Crawlora vs Bright Data.
• Give your AI agent live web data with MCP.