Antigravity MCP for WhatsApp: Connect WaBot to Google’s IDE

What Google Antigravity is

Google Antigravity is Google’s agent-first development platform. It comes as a desktop app that runs several local agents in parallel, a full agentic IDE, a terminal CLI (agy) and an SDK, on macOS, Windows and Linux. Google lists it as free for individual developers, with an enterprise option.

Since 18 June 2026 it is also where free and Google AI Pro/Ultra users of Gemini CLI were moved. If you’re still on Gemini CLI through a Code Assist licence or paid API key, use our Gemini CLI WhatsApp MCP guide instead.

What WaBot’s MCP server can do

WaBot’s hosted MCP server lives at https://api.wabot.shop/mcp and speaks Streamable HTTP, the transport Antigravity requires for remote servers. Its 36 tools cover:

Authentication is two HTTP headers only: clientid and clientsecret. No OAuth and no account ID. Limits: 60 requests a minute per Client ID, and every tool call is recorded in an audit log.

Set up WaBot in Antigravity, step by step

1. Copy your WaBot credentials

In the WaBot app go to Developer → Developer Credentials and copy the Client ID and Client Secret. The page’s Copy MCP config button copies them in one go.

2. Open Antigravity’s MCP config

Per Antigravity’s MCP documentation:

• IDE: in the agent side panel, open the … menu → MCP Servers → Manage MCP Servers → View raw config.
• Or edit the file directly: ~/.gemini/config/mcp_config.json applies to every project; <workspace>/.agents/mcp_config.json applies to one workspace.

3. Add the WaBot server

Remote servers use serverUrl (Antigravity no longer accepts the old httpUrl key), and headers is sent with each connection:

{
  "mcpServers": {
    "wabot": {
      "serverUrl": "https://api.wabot.shop/mcp",
      "headers": {
        "clientid": "<Client ID>",
        "clientsecret": "<Client Secret>"
      }
    }
  }
}

Replace the placeholders with your real values. Antigravity’s documentation doesn’t describe environment-variable substitution in headers, so the values sit in the file. That’s why the global file in your home folder is the safer choice. If you use the workspace file, keep it out of git:

# .gitignore
.agents/mcp_config.json

4. Reload and check

Back in Manage MCP Servers (or Settings → Customizations in the desktop app), confirm wabot is listed and enabled; refresh it if needed. In Antigravity CLI, type /mcp to open the MCP Manager overlay, reload configs and see connection logs.

5. Smoke test

Ask the agent: “Using WaBot, call get_account and list my connected WhatsApp numbers.” This only reads.

Use case 1: send a test order update while you build

You’re writing the “order shipped” step of a store backend and want to see the real WhatsApp message before wiring it into code.

Type:

Using WaBot, list my approved templates and pick the one for order shipping. Send it to my own number +91 98xxx xx000 with order number SR-1042 and name Asha. Show me the template, variables and number first. Then wait for my reply and tell me what I said.

Antigravity calls: list_templates, get_account (for the phone ID), send_template_message, then wait_for_reply, which waits up to 30 seconds per call.

You see: the order update on your phone exactly as a customer would, and your reply in the agent panel. You can then ask the agent to write your app’s sending code to match the variables it just used.

Antigravity’s documentation doesn’t mention server-pushed MCP notifications, so use wait_for_reply rather than counting on subscribe_replies.

Use case 2: build an appointment form as a WhatsApp Flow

A clinic, salon or café wants bookings inside WhatsApp, without a website form.

Type:

Create a WhatsApp Flow in WaBot called table_booking for Spice Route Café: a heading, name, phone, party size (dropdown 1-8), preferred date and a Submit button. Keep it as a draft and show me the fields. Publish only after I say yes.

Antigravity calls: list_whatsapp_flow_categories and list_whatsapp_flow_field_types to see what’s allowed, create_whatsapp_flow (saved as a draft), and after your go-ahead publish_whatsapp_flow.

You see: a field list to review, then a published Flow you can attach to a template. Once published, a Flow’s JSON can’t be edited, which is why the draft review matters; deprecate_whatsapp_flow retires one you no longer want.

Use case 3: a “price” auto-reply in one prompt

Customers keep typing “price”. You want an instant answer without writing a webhook handler.

Type:

In WaBot, create an automation: when an incoming message includes the word price, send the approved template price_list. Create it inactive, show me the diagram, and activate it when I confirm.

Antigravity calls: create_simple_autoflow (matchText “price”, operator includes), preview_workflow_schematic for a Mermaid diagram, then set_workflow_status to switch it on.

You see: a diagram of trigger → template, then a live automation. Test it by sending “price” from your own phone.

Safety: real messages, real customers

• Keep Antigravity’s default Ask mode for WaBot tools. Antigravity runs unconfigured MCP tools in Ask mode, so you approve each call. Don’t pre-approve mcp(wabot/*) while testing.
• Ask for the message and recipient before anything is sent, and test on your own number first.
• Message only people who opted in. An agent doesn’t change WhatsApp’s rules: see WhatsApp opt-in and consent.
• Don’t commit the Client Secret. If you think it has leaked, contact WaBot at hello@wabot.shop. WaBot records every tool call in an audit log.

To let agents read chats but never send, Antigravity’s disabledTools list in the wabot entry can block send_template_message and send_session_message.

Limits

• Not available through MCP: campaigns and broadcast scheduling, campaign analytics, segmentation, deleting workflows, and advanced workflow steps (branching, webhooks, agent handoff, code).
• Automations are created inactive until activate: true or set_workflow_status.
• 24-hour rule: outside it, only approved templates can be sent. New templates go to Meta review, from minutes to hours; poll get_template_status with sync: true.
• 60 requests a minute per Client ID.
• Full tool list: WaBot MCP documentation. Also coding in Cursor? See WhatsApp MCP for Cursor.

Frequently asked questions

Does Google Antigravity support remote MCP servers?

Yes. Antigravity’s MCP documentation supports local stdio servers (command) and remote Streamable HTTP servers (serverUrl), with a headers object for remote connections. The legacy HTTP+SSE transport and the httpUrl key aren’t supported.

Where is Antigravity’s mcp_config.json?

~/.gemini/config/mcp_config.json for all projects, or .agents/mcp_config.json inside a workspace. In the IDE: agent panel … menu → MCP Servers → Manage MCP Servers → View raw config.

Do I need OAuth to connect WaBot to Antigravity?

No. WaBot uses two headers, clientid and clientsecret, from Developer → Developer Credentials. Put them under headers in the wabot entry.

Can Antigravity agents send WhatsApp campaigns?

No. Campaigns, scheduling and segmentation aren’t exposed over MCP. Agents can send individual template and session messages, build keyword automations and create WhatsApp Flows.

Will Antigravity send messages without asking me?

By default Antigravity runs MCP tools in Ask mode, so you approve each call. Keep it that way for the WaBot send tools, and test on your own number first.