How do I verify Montage workspace access with Google Antigravity?
Google Antigravity distinguishes lazy-loaded MCP schemas from eagerly registered tools. That distinction matters when inspecting Montage: a cached schema file can explain a tool to the model without proving a fresh authorized call. Start with the installed Antigravity surface and its current MCP configuration, then verify the workspace through an actual read-only operation rather than judging readiness from tool-name visibility.
Using Google Antigravity, call only Montage signals_status as the first live operation. Report the actual workspace identity and coverage from the tool response. If authentication, transport, or the tool is unavailable, stop and explain the blocker. Do not start collection, recurring tracking, writes, publishing, messaging, or social actions.Find the active MCP configuration
Inspect the mcp_config.json used by the Antigravity installation you actually run. App, IDE, and CLI data locations differ, so avoid changing a neighboring profile and expecting this session to reload it. Preserve existing mcpServers entries. Choose a unique Montage name and keep personal authorization material out of shared project files and model instructions that may be copied elsewhere.
Connect to the hosted endpoint
Use the remote server configuration documented for that release, with https://app.montages.co/mcp as the service address. Do not supply a local command to launch Montage, and do not infer Streamable HTTP configuration keys from a different Google client. Verify the effective entry in Antigravity's MCP controls before investigating model behavior; an ignored definition cannot be repaired by prompting harder.
Resolve authorization before tool use
Follow the installed client's supported remote authentication controls and approve only the intended Montage account. If OAuth is unavailable or incompatible, stop or use another documented OAuth-capable client. Do not place cookies in configuration or invent a token. Product sign-in and remote Montage authorization are separate decisions, even when both accounts happen to use the same email address.
Understand lazy schema inspection
Antigravity normally caches tool schemas and lets the agent inspect them before invoking a lazy tool. Eager loading instead sends the full declaration up front. Neither mode is an authorization boundary. Keep the default loading policy unless you have a measured reason to change it, and do not enable every Montage tool merely to make the status tool easier to discover.
Request status without changing timeouts
Ask for signals_status as the first Montage operation and inspect its actual workspace response. If a connection or call times out, review the server-specific error before changing timeoutSeconds; disabling limits is not a sign-in remedy. Preserve a failed or unauthorized state honestly. Do not let an agent convert this diagnostic into collection, publishing, follows, or a background research task.
Keep the boundaries clear.
- Installed App, IDE, and CLI configuration and schema-cache locations differ; loading a cached schema is not execution proof.
- Documented setup, not live interoperability certification. A visible tool catalog is not workspace authorization.
- First live operation: read-only signals_status. No automatic collection, recurring tracking, or social actions; broader actions need separate explicit authorization.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.