Antigravity and Cloud MCP

Distinguish Antigravity configuration, Cloud authorization and a successful saved-file read.

Cloud MCP uses the remote HTTP endpoint https://mcp.altifigence.com/cloud-mcp. A configured server, an authorized account and a successful tool read are separate checks. Availability depends on the client and your Cloud organization’s tool policy.

Configure Antigravity

When the installed Antigravity version reads remote MCP servers from mcp_config.json, the Cloud MCP entry has this form. Confirm the installed version’s documentation and the intended configuration file before using it.

{
  "mcpServers": {
    "altifigence": {
      "serverUrl": "https://mcp.altifigence.com/cloud-mcp"
    }
  }
}

Antigravity’s documentation lists a global file, ~/.gemini/config/mcp_config.json, and a workspace file, <workspace>/.agents/mcp_config.json. In that file, a remote server uses the Streamable HTTP transport and takes its endpoint in serverUrl. The Cloud MCP entry does not use headers or client credentials; access comes from the account authorization below.

Authenticate

When your Antigravity version offers Authenticate for the configured server, Antigravity starts the account authorization. Its documentation places Authenticate next to the server in the Customizations tab of Agent settings. Cloud returns to Antigravity’s registered callback; finish any remaining step in Antigravity as its documentation describes. The account, organization and requested scopes belong to that authorization. The DDS settings page does not prove that Antigravity completed it. A callback alone does not establish successful Cloud tool access.

Check connection availability in DDS

Use QUOTA to open DDS settings and choose Developer access.
Read the project selected in Overview and the requirement for account sign-in, organization consent and permission.
Choose Open setup to open Developer tools. Read the offered setup information and Documentation link.
Expand Details. Read MCP endpoint, Transport, Authentication and the permission labels. The displayed transport is Streamable HTTP.

In Developer access, read the selected project and the sign-in and consent requirement.

Choose Open setup to open Developer tools.

The Details table is a reference to tool names and permission categories. The connection’s actual discovered tools and current grant determine access; the reference alone does not enable a tool.

Expand Details to read the Cloud MCP endpoint, the permissions and the tool reference.

Context, search & connections is a separate settings page for context, Web search and AI connections. These controls are not the Cloud MCP consent screen. Developer tools may show setup information without offering an external authorization session in this host.

When the connection exposes read tools

A connected Cloud account can expose identity, accessible projects and saved-file reads under cloud.read. A successful small read of a non-sensitive file from a project returned by that connection establishes more than server configuration alone. Project/file identity, pagination, chunk completion and versions define what was read. A denied tool remains unavailable without the required current organization policy and consent.

Keep staff DX separate

The staff DX endpoint ends in /dx-mcp. Its organization plugin and employee device-login flow do not configure customer Cloud access. The DX device-code flow must not be substituted for Cloud authorization, and staff scopes must not be mixed with cloud.* scopes.

If connection fails

If Antigravity rejects the configuration entry, use the documentation for its installed version. A rejected callback, missing tool or denied read has a different cause from an unavailable DDS workspace. Keep the sanitized error and use MCP troubleshooting. Tokens, browser cookies and authorization codes do not belong in shared project configuration.