Turbo Notify in Antigravity

In the Antigravity CLI (agy), the turbo-notify plugin brings the MCP server and the virtual attendant skill. The attendant works in assisted mode, in a session you keep open, with a person approving every answer. Nothing is answered with the session closed.

What you need

A Turbo Notify account with a connected number (quickstart).
The Antigravity CLI installed.
Python 3.9 or newer.

Connect

agy plugin install https://github.com/turbo-notify/agent-skills

After the install, agy plugin list shows the MCP server as a component of the plugin. Installing from GitHub uses no version tag: it follows the latest stable version.

With your account: in the sidebar open Customizations, tab Installed, MCP Servers. The server is listed with its 36 tools. Click Authenticate next to it, sign in to Turbo Notify, approve access and paste the code back within a minute (the code expires after 60 seconds). The dot turns green and Sign out replaces the button. On the first call of a tool, Antigravity asks permission to use it. If you edited mcp_config.json while a conversation was open, open a new conversation: the open one does not see the server.
With an API key: create the key in API Keys (opens in a new tab) and add the server with the header:
```
agy mcp add turbo-notify https://mcp.turbonotify.com -H "Authorization: Bearer YOUR_KEY"
```
Treat the key like a password.

Scopes and keys are in MCP server.

Test

Run agy plugin list: the turbo-notify plugin should appear. Then ask the agent: “List my WhatsApp numbers on Turbo Notify.” It calls list_numbers, which only reads. Nothing is sent.

For the skill, ask: “Set up the Turbo Notify virtual attendant.”

Update

Run the install command again. It replaces the installed copy.

agy plugin install https://github.com/turbo-notify/agent-skills

The skill checks its own version and messages the administrators when a newer one exists.

Limits

Assisted mode only, with the session open. Every answer needs approval, and the context is not kept apart per customer.
The Gemini CLI is not supported. Google’s target is Antigravity.
To serve customers at any hour, use Claude Code or Codex.
The tools follow the API limits: 600 requests per minute per key or sign-in, plus the plan’s quota and sending pace. See MCP server limits.

What is not verified

The plugin and CLI (agy) path. The Authenticate button, the code pasted back and a list_numbers call were walked on 3 November 2026 in the Antigravity desktop app, with the server declared in mcp_config.json (key url); the full flow with a customer’s account was not repeated.
The attendant talking to real customers in Antigravity. Install and update were tried on a clean profile; serving real customers was not.