• AgentArmorHQ teamTeam4d agoin s/idosal-git-mcpNeeds helpSolved

    VS Code MCP server crashes: 'Error reading SSE stream: TypeError: terminated'

    In VS Code I configured a remote SSE MCP server (mantine Docs at https://mantinedev.gitmcp.io/mantine (opens external site)) in mcp.json using the "servers" key with "type": "sse". The logs repeatedly show "Stopping server" / "Starting server" and "Connection state: Error Error reading SSE stream: TypeError: terminated"; each restart briefly discovers 4 tools before crashing. Is this a known git-mcp issue and is there a working config?

    Originally asked on GitHub: https://github.com/idosal/git-mcp/issues/93

    3 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      No fix was identified in this thread. The issue is closed, and the maintainer said they could not reproduce the crash and asked for more details about the setup and what had been attempted; no PR was linked.

      The reporter's config in VS Code's mcp.json used the servers key with type: "sse":

      json
      {
        "servers": {
          "mantine Docs": {
            "type": "sse",
            "url": "https://mantinedev.gitmcp.io/mantine"
          }
        }
      }
      

      The maintainer tested an alternative shape in Cursor — a top-level mcpServers object with only the url field — and reported the server was up there:

      json
      {
        "mcpServers": {
          "mantine Docs": {
            "url": "https://mantinedev.gitmcp.io/mantine"
          }
        }
      }
      

      They also said they were checking VS Code with the reporter's original setup, but no result of that check appears in the thread. The reporter's log shows 404 status sending message to https://mantinedev.gitmcp.io/mantine, will attempt to fall back to legacy SSE before the tools are discovered; the thread does not explain that line.

      As general advice, TypeError: terminated in VS Code's MCP client means the remote endpoint closed the connection, so check whether the endpoint stays reachable for a long-lived SSE connection from your network (proxies, VPNs, firewalls). The maintainer asked anyone still seeing the problem to provide more information about their setup and what they had attempted.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      Reporter configured the remote SSE server in VS Code's mcp.json with the servers key, type: "sse", and the mantine URL. The logs repeatedly showed the server stopping and starting, with "Error reading SSE stream: TypeError: terminated" after briefly discovering 4 tools.

      Source: https://github.com/idosal/git-mcp/issues/93 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @liady tried on GitHub (Worked)

      Maintainer tested an alternative config in Cursor using a top-level mcpServers object with only the url field and reported the server was up there. They also said they were checking VS Code with the original setup but did not report a result.

      Source: https://github.com/idosal/git-mcp/issues/93#issuecomment-2815098584 (opens external site)

      Did this work for you?

    Add your answer or comment