Antigravity CLI or Gemini CLI: Connect MCP, Publish, and Run Forms

Last updated: October 15, 2026

Use FORMLOVA from Gemini CLI / Antigravity CLI by checking client access and permissions, registering the official MCP endpoint, authorizing your FORMLOVA account, then inspecting a saved draft. A list of proposed fields in chat is not evidence that a form was created. Begin with one private study-session registration draft and verify the saved target.

FORMLOVA registration, drafts and preview are available on Free. The AI client's eligibility, subscription and usage conditions are separate.

Before connecting

• Have a FORMLOVA account with verified email.
• Check the client's MCP support, account eligibility and organization policy.
• Decide whether the setup is personal or shared, and identify the intended form.
• Use the official endpoint below; do not paste credentials into chat or shared configuration.

https://formlova.com/api/mcp

Connect Gemini CLI

Current Gemini CLI authentication documentation supports signing in with a personal Google account. This guide does not retain the old blanket claim that personal access ended and migration to Antigravity is mandatory. Check your account, organization policy and usage allowance.

gemini mcp add --transport http formlova https://formlova.com/api/mcp
gemini mcp list

Inside Gemini CLI, use /mcp auth formlova and complete FORMLOVA OAuth. Manual configuration uses httpUrl under mcpServers in project .gemini/settings.json or user ~/.gemini/settings.json.

{
  "mcpServers": {
    "formlova": {
      "httpUrl": "https://formlova.com/api/mcp"
    }
  }
}

Keep Antigravity CLI configuration separate

Antigravity has its own official MCP flow. Current documentation describes the /mcp manager, global ~/.gemini/config/mcp_config.json, workspace .agents/mcp_config.json, and serverUrl for remote connections.

{
  "mcpServers": {
    "formlova": {
      "serverUrl": "https://formlova.com/api/mcp"
    }
  }
}

Do not substitute Gemini CLI's httpUrl. Follow the client's authentication UI, verify FORMLOVA sign-in/authorization, and do not paste codes or tokens into chat. Logging in to the Google CLI and authorizing FORMLOVA are separate. Do not assume configuration and credentials always transfer automatically.

After connecting, test a study-session registration draft

This is a proposed trial, not an operation or result measured for this rewrite. Use a private test draft first.

Create a private study-session registration draft with name, email, attendance format (in person / online) and optional questions. Ask for date and capacity; do not guess. Show fields, logic and preview. Do not publish or send email.

Before proceeding, check:

• Is there an actual saved form with the intended name, fields and private state?
• Do required rules, logic and completion copy match the purpose?
• Can you check input on mobile and desktop? Preview submission does not test production storage or email delivery.

Move from draft review to publishing

Inspect the saved fields, required rules and choices, then open form and completion previews. Review instructions, consent, intended audience, duplicate prevention and privacy requirements. Request publishing explicitly after the checks; initial review and final publication are separate stages.

Eligible new forms with supported free-text inputs default to sales detection enabled. Review the setting and external-AI processing; disable it when unsuitable. Classification is after storage and excludes paid/selection-only forms.

After publishing, submit authorized test data to verify actual storage, workflow execution and send results separately. Opening preview does not prove live collection or delivery.

Separate operations from plan eligibility

Response statuses are new, in_progress, resolved and spam. Keep business stages such as confirmed or awaiting a reply in retained tags/notes or an external ledger. Preserve existing notes/tags and do not mark unfinished work complete.

MCP email/phone displays are masked. Do not use them as raw recipients or manual joins; use authorized exports, supported response-recipient tools or server-side integration. Free response notifications are a six-hour owner digest and do not consume outgoing-mail quota. They are separate from per-form immediate notification or paid email workflow actions.

Workflow Place prompts do not automatically start continuous monitoring. Distinguish a single run from triggers, schedules and destinations actually saved.

Troubleshoot in order

Check URL, configuration syntax/scope, account, OAuth, enabled tools, form permissions, then feature eligibility. Refresh tool discovery using the client's current official procedure where necessary. After uncertain writes, retrieve the saved object before retrying to avoid duplicate forms or sends.

Questions and next step

Does connecting unlock paid features? No. Connection and feature eligibility are separate; start with the free draft.

Is every client interface identical? The server URL is shared, but permissions, available tools, UI and confirmation behaviour depend on the client/account.

What should I try first? Create the proposed intake, inspect the saved draft and preview, then add only the operations you need.

Current official references

• Gemini CLI / Antigravity CLI official MCP guide
• Antigravity MCP
• Gemini CLI authentication
• FORMLOVA setup

Related Guides and References

• Most form tools stop at creation
• How to create forms with ChatGPT and Claude
• How to run the pre-publish review and publish with FORMLOVA
• How to view, filter, and manage form responses with FORMLOVA
• How to find a recipe in FORMLOVA's Workflow Place and set it up from chat
• Slack Notification + Sheets Log
• Response to HubSpot Contact
• Response to Notion Database
• the complete guide to using FORMLOVA with Claude Desktop
• the complete guide to using FORMLOVA with Claude Code
• the complete guide to using FORMLOVA with Cursor
• the complete guide to using FORMLOVA with ChatGPT
• The MCP Form Service Guide for FORMLOVA -- Not Just Building With AI, but Running Forms After Publication
• Google Gemini CLI: historical discussion #28017 (use the current authentication guide for present account eligibility)
• Antigravity CLI official site
• Google: Gemini CLI -- MCP servers with the Gemini CLI
• Model Context Protocol: Introduction

Disclosure and Verification

This guide is written by FORMLOVA's developer. Client connection steps were checked on October 15, 2026 against current official documentation and local setup code; product features were checked against SPEC and plan definitions. Where older local instructions differ, this article follows the current official flow. This rewrite did not execute a new connection, publication or send; the trial request is a proposal.