Skip to content
MCP Apps2-0Antigravity AppFeaturesMCP Apps Antigravity App FeaturesAntigravity App
Available on:
Antigravity App

MCP Apps let a Model Context Protocol (MCP) tool ship an interactive HTML interface alongside plain-text model output. Antigravity implements the open MCP Apps specification (io.modelcontextprotocol/ui) and adds Antigravity-specific entrypoints (com.google.antigravity/ui) for side panel, full-page, and custom file viewer surfaces.

For the full protocol specification, iframe bridge lifecycle, theming tokens, and SDK reference, see the MCP Apps overview and the @modelcontextprotocol/ext-apps API reference.

MCP Apps in the Antigravity App: inspect an inline deployment card in chat, open the side panel release board to promote a canary rollout, switch to the full-page view from Plugins in the sidebar, and edit a custom file type in a file viewer tab.

Every MCP App comes from a plugin or MCP server that you install or build. Each tool controls where its view renders through _meta:

SurfaceDeclared withHow it opens and behaves
Inline in chat_meta.ui.resourceUriReplaces the collapsed MCP tool step card directly in the conversation stream. Auto-resizes up to 800 px (150 px fallback). Tools with aux_pane or global entrypoints do not render inline.
Side panel
aux_pane
aux_pane entrypointOpens beside the conversation when the agent finishes calling the tool, from Open in side pane, or from Overview > Plugins, the side panel + menu, or More actions (⋯) > Plugins. One tab per (server, tool). Manual launches pass {}; repeat agent calls update the open tab in place.
Full page
global
global entrypointOpens full-width outside any conversation from Plugins in the left sidebar. Manual launch passes {}. Conversation-only capabilities (message, updateModelContext) are omitted.
File viewer
file
file entrypointReplaces the built-in viewer for files matching a claimed extension. Uses the plugin’s logo as the tab icon, stays hidden from the model regardless of visibility, and receives {"file": {"name", "resourceUri"}}.
Antigravity CLI
agy
mcp_config.jsonConnects to <plugin>_<server> through /mcp with no iframe rendering. Ignores _meta.ui.visibility (exposing all listed tools to the model, including visibility: ["app"] helpers and file entrypoint tools) and reads plain-text content directly.

Use MCP Apps for reusable tool or plugin UIs backed by a live MCP server, side panel views, or custom file viewers. Use /generative_ui for one-off diagrams, charts, or prototypes generated on the spot for a single conversation.

The Antigravity App includes the built-in /mcp-app-development command. Ask the agent to scaffold a starter MCP App plugin directly in your workspace:

/mcp-app-development Build an MCP App plugin for Antigravity that tracks release checklist items inline in chat and in a side panel board using @modelcontextprotocol/ext-apps.

To build an MCP App by hand, do the following:

  1. Follow the MCP Apps specification and @modelcontextprotocol/ext-apps API reference to bundle a single-file ui:// HTML resource (text/html;profile=mcp-app) and link it from _meta.ui.resourceUri.
  2. Package your server inside a plugin with mcp_config.json at the plugin root (using ${PLUGIN_ROOT} and ${PLUGIN_DATA} for local stdio servers, or serverUrl for remote Streamable HTTP servers).
  3. Validate and install locally with agy plugin validate <path> --strict and agy plugin install <path>.

During MCP initialize, the Antigravity App advertises com.google.antigravity/ui ({"entrypoints": ["aux_pane", "global", "file"]}) alongside io.modelcontextprotocol/ui.

Add _meta["com.google.antigravity/ui"].entrypoints on a tool that also declares a valid ui:// resourceUri to open views outside the inline conversation stream. Keep file entrypoints on their own separate tool: any tool with a file entrypoint is unconditionally hidden from the model and receives {"file": {"name", "resourceUri"}} rather than {}:

// Tool 1: model-callable side panel + full-page view
{
  "_meta": {
    "ui": { "resourceUri": "ui://acme-cloud/deployments.html" },
    "com.google.antigravity/ui": {
      "entrypoints": [
        { "type": "aux_pane", "title": "Acme Deployments" },
        { "type": "global", "title": "Acme Deployments" }
      ]
    }
  }
}

// Tool 2: separate host-invoked custom file viewer
{
  "_meta": {
    "ui": { "resourceUri": "ui://acme-cloud/topology-viewer.html" },
    "com.google.antigravity/ui": {
      "entrypoints": [
        { "type": "file", "title": "Acme Topology Viewer", "extensions": [".acmetopo", ".jsonc"] }
      ]
    }
  }
}
TypeExtra fieldsHost behavior
aux_panetitle (optional string)Auto-opens beside the active conversation when called by the agent; manual menu launches pass {}. Does not render inline. One tab per (server, tool).
globaltitle (optional string)Opens full-width from Plugins in the left sidebar with {}. Does not render inline.
filetitle (optional string)
extensions (required string[])
Always hidden from the model regardless of visibility. Extensions are normalized to lowercase with a leading dot. First enabled server claiming an extension wins.

When a user opens a file matching a file entrypoint extension, Antigravity invokes the tool with a per-view opaque URI ({"file": {"name": "bracket.stl", "resourceUri": "antigravity-file://<uuid>/bracket.stl"}}) without exposing the raw filesystem path:

  • Read: Send resources/read for that exact resourceUri from the iframe. Antigravity answers directly (without calling your MCP server) with a base64 blob (application/octet-stream, max 10 MiB).
  • Write (local files only): Check hostContext["com.google.antigravity/resources"]?.write before enabling save controls. When present, send com.google.antigravity/resources/write with { uri, text } (UTF-8) or { uri, blob } (base64), capped at 10 MiB.
  • Open a file in the side panel: Call app.request() with method com.google.antigravity/toggle-aux-pane and params { "tabType": "fileView", "uri": "file:///path/to/file" }. Handle JSON-RPC -32601 on hosts without this extension.
  • Start a background conversation: Pass _meta: { "com.google.antigravity/message": { "target": "new" } } in ui/message (app.sendMessage()) to start a new conversation in the same project instead of posting to the current thread.
LimitValueNotes
HTML and file size10 MiBApplies to ui:// HTML documents and antigravity-file:// reads and writes.
Persisted tool result1 MiBCallToolResult payloads stored on trajectory steps; load larger datasets through an app-only tool.
Concurrent tools/call4 per viewScoped strictly to the view’s owning MCP server; in-flight calls abort on close.
Hidden background frames5 (LRU)Hidden aux_pane and global frames stay mounted in memory up to the 5-frame cap.
Inline card height150 px fallback
800 px max
Falls back to 150 px if no size-changed arrives within 100 ms; taller views scroll internally.
TeardownNo notificationAntigravity does not send ui/resource-teardown on close; persist edits eagerly.
Isolation and CSPDefault-denyIsolated iframe with no persistent browser storage. Allowlist bare origins only in resource _meta.ui.csp, and prefer tools/call over connectDomains.

Antigravity namespaces plugin servers as <plugin-name>_<server-key> and falls back to its bundled Node.js runtime only when "command": "node". Because ui:// resources fetch fresh on every mount, HTML edits apply when you close and reopen a view. After editing local stdio server code, restart the server from Customizations > Installed > select plugin > MCP > More actions (⋮) > Restart.