MCP Servers fail to initialize automatically in Antigravity IDE 2.1.1

Google Antigravity
1

Bug Report ā€“ MCP Servers fail to initialize automatically in Antigravity IDE 2.1.1

Title

MCP servers (notebooks and visualization) fail to initialize automatically after IDE startup with context deadline exceeded, but manual Refresh immediately resolves the issue.

Environment

  • Antigravity IDE: 2.1.1

  • VSCode OSS: 1.107.0

  • Commit: e0b7a2bcf575cfba10528c4e7c10bd3ce2d7769a

  • Electron: 39.2.3

  • Chromium: 142.0.7444.175

  • Node.js (IDE): 22.21.1

  • OS: Windows 11 x64 (10.0.26200)

Installed extensions:

  • Google Cloud Data Agent Kit

  • Python

  • Jupyter

  • Jupyter Renderers

  • Debugpy

Original problem

Initially the IDE reported:

MODULE_NOT_FOUND

Cannot find module

googlecloudtools.datacloud-0.5.2-universal\mcp_servers\cli\mcp_proxy_bundle.js

Installing Google Cloud Data Agent Kit resolved this issue completely.

Current issue

After installing the extension, every IDE startup shows:

chrome-devtools-mcp:
context deadline exceeded

notebooks:
[MCP Proxy] Socket connection error:
connect ENOENT
\\?\pipe\datacloud-mcp-notebooks-antigravityide

visualization:
[MCP Proxy] Socket connection error:
connect ENOENT
\\?\pipe\datacloud-mcp-visualization-antigravityide

context deadline exceeded

Important observation

Opening:

Antigravity IDE
ā†’ Manage MCP Servers

shows the servers in an error state.

Pressing Refresh once immediately removes every error.

After Refresh:

  • notebooks work correctly

  • Jupyter works correctly

  • matplotlib renders correctly

  • visualization works correctly

  • no MCP errors remain

The problem only returns after restarting the IDE.

Reproducibility

100% reproducible.

Steps:

  1. Launch Antigravity IDE.

  2. Wait until startup completes.

  3. Observe MCP errors.

  4. Open Manage MCP Servers.

  5. Press Refresh.

  6. Errors disappear immediately.

  7. Restart the IDE.

  8. Errors return.

Diagnostics performed

Verified:

  • mcp_proxy_bundle.js exists.

  • File path is correct.

  • Node can execute the proxy manually.

  • Proxy displays its usage correctly.

  • chrome-devtools-mcp runs correctly through npx.

  • Python works.

  • Jupyter works.

  • Notebook execution works.

  • Graph rendering works.

  • Named pipes are created only after manual Refresh.

Manual execution:

node mcp_proxy_bundle.js

returns

Usage: node mcp_proxy.js <serverId_or_socketPath>

indicating the proxy itself is valid.

Suspected root cause

This appears to be a startup race condition.

The IDE attempts to connect to the MCP servers before they finish initializing.

The automatic startup sequence times out (context deadline exceeded) and never retries.

A manual Refresh restarts or reconnects successfully, suggesting the servers themselves are healthy.

Suggested improvement

Possible solutions:

  • Delay MCP client connection until the server reports ready.

  • Automatically retry connection after timeout.

  • Restart failed MCP servers automatically during startup.

  • Add configurable startup timeout for MCP initialization.

Temporary workaround

Open:

Manage MCP Servers

Press:

Refresh

The issue disappears until the next IDE restart.

1 Like