I’m experiencing persistent MCP server errors in Antigravity on Linux. Multiple MCP servers fail to maintain stable connections, with repeated authentication and session errors

Google Antigravity
,
1

Environment

  • OS: Pop!_OS 24.04
  • Antigravity version: [check Help → About and fill in]
  • Model in use: Gemini 3 Flash
  • Node.js version: v24.13.0 (via nvm, symlinked to /usr/local/bin/)

Errors observed

1. StitchMCP

2. atlassian-mcp-server

  • Receives HTTP error status 404: Streamable HTTP error: Error POSTing to endpoint: Missing sessionId parameter
  • Falls back to SSE-only transport, then also gets cancelled with context canceled

3. github-mcp-server

  • Error: invalid or expired token during GitHub MCP server connection
  • Followed by: method invalid during initialization method=notifications/cancelled
  • Server session disconnected and ended

Steps to reproduce

  1. Open Antigravity on Pop!_OS 24.04
  2. Open the Agent panel with default MCP servers enabled (Stitch, Atlassian, GitHub)
  3. Errors appear immediately on startup, before any user interaction

What I’ve already tried

  • Symlinked node, npm, npx from nvm to /usr/local/bin/ (this fixed earlier MCP PATH issues)
  • Restarted Antigravity multiple times
  • Checked that the GitHub token is valid in my GitHub account settings

Expected behavior

MCP servers should establish stable connections and remain available throughout the session, not cancel themselves immediately after connecting.

Additional context

I’ve been hitting multiple Linux-specific issues with Antigravity (icon rendering, marketplace fetch, sign-in). Happy to provide additional logs or run diagnostic commands if that helps. Screenshot of the errors attached.