Google Antigravity Plugin Marketplace Launches

• Google launched the Plugin Marketplace on 29 October 2026 as a central directory for third-party and Google-built plugins in both the Antigravity App and CLI; before it, connecting an agent to outside systems meant hand-configuring MCP endpoints, environment variables, skills and subagents per repository^[1]
• A plugin is a versioned bundle defined by a plugin.json manifest that can package up to five primitives (skills, MCP servers, rules, lifecycle hooks and custom agents) that install, update and toggle as one unit^[1]
• Hooks run outside the model's reasoning loop at points such as SessionStart, PreToolUse, PostToolUse, PreInvocation, PostInvocation and Stop, so teams can block sensitive tool calls or require tests to pass; MCP servers can declare required user variables or OAuth 2.0 flows, prompted once at setup^[1]
• Launch partners span delivery, operations, data, design, commerce and security, with Google's post spotlighting Atlassian, Canva, CrowdStrike, Databricks, Datadog, Dropbox, Figma, monday.com, Ping Identity, SentinelOne, Stripe and Unity, and a long category list from Firebase and Google Workspace to Vercel, Sentry and Supabase^[1]

Notable features

• Install from the app's Customizations panel (Plugins tab) or the terminal with agy plugin install <plugin-name>; builders can check a bundle with agy plugin validate, install it locally and confirm with agy plugin list, and partners apply through an interest form^[1]
• Google's docs add that plugins installed in the app sync automatically into the CLI's Installed tab, and plugins that need an API token open a setup dialog when toggled on, while OAuth plugins open the browser for sign-in^[1]
• Google's own first-party entry followed within days: NeoTeo reports the google-cloud-developer plugin (five skills plus a Developer Knowledge MCP connection) appeared under 'Build with Google' from 3 November 2026^[2]
• A Google Developer Expert write-up notes why packaging matters: loose files in .agents/ drift across repositories, whereas a plugin is versioned, validated with agy plugin validate --strict, automatically namespaces tools as <plugin-name>_<server-name> and can be shared via GitHub or the Marketplace^[3]