Plugin Marketplace in Antigravity

Today, we are launching the Plugin Marketplace in Antigravity, a centralized directory for discovering and installing third-party and Google-built plugins across the Antigravity App and the Antigravity CLI. Until now, connecting an agent to external systems meant manually configuring Model Context Protocol (MCP) endpoints, environment variables, domain skills, and custom subagents across individual repositories or local configuration files. The Plugin Marketplace packages these primitives into verified, shareable bundles that you can browse by category and install in a click. Instead of switching between browser tabs to look up a ticket, inspect a design spec, query production logs, or check a security alert, you can give your agent direct, scoped access to the systems where your team already works.

As Antigravity continues to optimize for builders, we are launching the marketplace with integrations from partners across software delivery, enterprise operations, data analytics, design, commerce, and security. Here is a look at what each launch partner brings to your workflow in Antigravity.

What are the components of a plugin?

An Antigravity plugin is a versioned, self-contained bundle defined by a plugin.json manifest. Rather than configuring tools and instructions piece by piece across individual repositories, a plugin packages up to five extensibility primitives that install, update, and toggle on or off together as a single unit.

Skills

Skills are modular packages of domain knowledge, multi-step procedures, and optional helper scripts defined in a SKILL.md file. While tools give an agent raw access to an external system, skills teach the agent how to sequence those tools reliably for complex workflows such as incident triage, schema migration, or design-to-code translation. To keep the agent’s context window focused, Antigravity uses progressive disclosure: only each skill’s name and short description are loaded at startup, and the full instructions, reference docs, and scripts are pulled into context on demand when relevant to your prompt or invoked via a /skill-name slash command.

MCP Servers

Model Context Protocol (MCP) server configurations (mcp.json) connect the agent to external APIs, databases, and developer tools over remote Streamable HTTP endpoints or local standard input/output (stdio) processes. Plugins can declare required user variables (such as API tokens or workspace URLs) or OAuth 2.0 authentication flows, prompting you once during setup in the Antigravity UI or CLI and automatically scoping tool availability to the plugin’s lifecycle.

Rules

Rules are Markdown instructions (rules/AGENTS.md or rules/*.md) that establish persistent guardrails, coding conventions, API usage constraints, and domain standards. Rules bundled inside a plugin can remain active whenever the plugin is enabled or load dynamically when the agent determines they are relevant to the task at hand, ensuring the agent follows organizational policies and partner best practices such as query cost limits, SDK conventions, or read-only operational modes.

Hooks

Lifecycle hooks (hooks.json) execute deterministic shell commands or scripts at specific points in the agent’s execution loop, including SessionStart, PreToolUse, PostToolUse, PreInvocation, PostInvocation, and Stop. Because hooks run outside the model’s reasoning loop and exchange structured JSON over standard input and output, teams can use them to gate or block sensitive tool calls, redact secrets from tool outputs, inject workspace context at startup, or require linters and test suites to pass before the agent finishes a turn.

Custom Agents

Custom agents (agents/<agent-name>.md) define specialized personas and subagents with tailored system prompts, curated tool allowlists, model selections, and command execution policies. A custom agent bundled in a plugin can be selected as the primary session agent for a dedicated workflow or spawned in the background by the main agent to handle focused tasks, such as a security posture audit, log investigation, or code review, in an isolated context window.

Plugins to explore

Getting started

The Plugin Marketplace in Antigravity is rolling out today across the Antigravity App and the Antigravity CLI. To explore the catalog and install your first plugin, open the Customizations panel in the Antigravity App and browse the Plugins tab, or install plugins directly from your terminal using agy plugin install <plugin-name>:

agy plugin install <plugin-name>

To learn how to build and package your own plugins for your team or the community, check out the Plugins documentation and the Marketplace guide. Before publishing or sharing a plugin, you can validate its plugin.json manifest and MCP server configurations and test it locally from your terminal:

# Validate plugin.json and MCP server configurations
agy plugin validate ./<plugin-name>

# Install and test the plugin locally from your working directory
agy plugin install ./<plugin-name>

# Verify the plugin is installed and enabled
agy plugin list

If you are a technology partner interested in publishing an official integration in the Plugin Marketplace in Antigravity, validate your plugin bundle and submit your details through the partner interest form.