modelcontextprotocol / modelcontextprotocol/servers

MCP Server Communication Failure on Windows with Antigravity/Gemini Code Assist

Open
#3,278 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
90.5k
Forks
11.7k
Avg merge
2d 2h
Merged PRs (30d)
5

Description

Bug Report: MCP Server Communication Failure

Summary

The MCP server @modelcontextprotocol/server-memory starts correctly but Antigravity fails to communicate with it, causing indefinite loading states when calling MCP tools like mcp_conversations_read_graph.

Environment

  • OS: Windows
  • Extension: Antigravity (Gemini Code Assist)
  • MCP Config Location: C:\Users\julio\.gemini\antigravity\mcp_config.json

Configuration

{
    "mcpServers": {
        "conversations": {
            "command": "npx",
            "args": ["-y", "@modelcontextprotocol/server-memory"],
            "env": {
                "MEMORY_FILE_PATH": "C:\\Users\\julio\\.gemini\\antigravity\\mcp_memory.json"
            }
        }
    }
}

Steps to Reproduce

  1. Configure MCP server as shown above
  2. Start/reload VSCode with Antigravity
  3. Attempt to use any MCP tool (e.g., mcp_conversations_read_graph)
  4. Result: Tool hangs indefinitely with "Loading..." state, never returns

Diagnosis Performed

1. Server Runs Correctly Manually
MEMORY_FILE_PATH="C:/Users/julio/.gemini/antigravity/mcp_memory.json" npx -y @modelcontextprotocol/server-memory
# Output: "Knowledge Graph MCP Server running on stdio"
2. Node Processes Are Running
node.exe  PID 11404
node.exe  PID 3260
3. Memory File Never Created

The mcp_memory.json file is never created, indicating the server is never successfully invoked by Antigravity.

Expected Behavior

MCP tools should return results within seconds, not hang indefinitely.

Actual Behavior

MCP tools hang indefinitely. User must manually cancel the operation.

Suspected Cause

The stdio communication channel between Antigravity and the MCP server is not being established correctly on Windows.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or failing test is named. Start by reproducing the Windows setup from the Antigravity mcp_config.json and the manual npx command, then trace whether the stdio connection is established; done means MCP tools return results within seconds and mcp_memory.json is created.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript, vscode
Domain
api, devtools, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.