An error please help

Google Antigravity
,
1

Hello I was getting an error while connecting antigravity to roblox studio
how can I fix this anyone help please
Roblox_Studio: Error: expect initialized request, but received: Some(Request(JsonRpcRequest { jsonrpc: JsonRpcVersion2_0, id: Number(1), request: CustomRequest(CustomRequest { method: “server/discover”, params: Some(Object {}), extensions: Extensions }) })) : connection closed: calling “initialize”: client is closing: EOF

2

did you find a fix? I have the same issue

3

Google Antigravity mcp & the updated MCP specification…
:link: reference: modelcontextprotocol.io - Version 2026-07-28 - Major changes.

I am not familiar with the “Roblox studio” you are mentioning, but this is a problem multiple people seem to have across Antigravity, while using MCP Servers now. Even if their setup worked fine before… I have the answer and will put it here for anyone facing the same issues, and to explain for those whom are curious.

To start with: what can you do to fix it?

  • :bell: Notify the developer of the MCP tool of these changes.
  • :palms_up_together: Try to help with the development if capable and it’s open-source.
  • :hammer_and_wrench: Temporarily work-around at the end of the post, but that is NOT recommended unless you have no other options, requires tinkering.

:information_source: The technical answer and sources for details

The client [Antigravity] uses and adopts the updated stateless MCP specification, more info & sources:

:police_car_light: The big change being pushed is this:

‘‘Make MCP stateless: remove the initialize/notifications/initialized handshake. Every request now carries its protocol version and client capabilities […] Clients SHOULD identify themselves on each request […] and servers SHOULD identify themselves in each result’s _meta […]’’
:link: Sources:
Modelcontextprotocol SEP-2575 Stateless MCP Proposal
Modelcontextprotocol 2026-07-28 changelog

:nerd_face: The technical answer is above, but, what goes wrong here ?

What the Antigravity attempts to do:

  • :incoming_envelope: Antigravity, upon first interaction with the MCP server, wishes to know about the MCP server to find out what the capabilities of the MCP server are.

What most likely goes wrong/happens if you encounter this:

  1. :green_circle: Your MCP configuration is used by Antigravity…
  2. :right_arrow: The MCP server [most likely] is not yet updated. The client and server “don’t speak the same language” and don’t know what to do with the responses, so it panics or exits instead of returning a standard response…
    (or standardized error handling for this, etc.)
  3. :red_circle: For Antigravity this is likely seen as the MCP server closing the connection abruptly, and it doesn’t receive the answer it expects which is “up to the specification”. Or the MCP server receives a response it doesn’t understand, so, the same but the other way around…

:sleeping_face: So, TL;DR:

  • :puzzle_piece: The recent changes to the MCP specification -standardization how MCP tools and AI communicate and work- has been pushed to Antigravity (same for some other providers). Meaning that Antigravity already accounts for this big change, while not every MCP tool had already been updated for this prior.

  • :speech_balloon: Basically the communication between Antigravity and MCP servers has changed, but if only one of them speaks the new language, it gets confused.

:hammer_and_wrench: The temporarily, not recommended work-around..

  • We can, if there is no option to notify the MCP tool developer, collaborate on the (open source) project, or if we need it NOW, make a temporarily wrapper script instead of directly using the incompatible MCP as we normally would.

  • In this example “Orbit local” is used and Python:
    https://docs.gitlab.com/orbit/local/access/mcp/

  • Details can be found here: