This is it. You’d need Copilot to use the MCP server with VSCode. Alternatively you can install the Claude client and use that to access the MCP server to connect your account.
You don’t have to install GitHub Copilot separately. Rather, you would have to install the GitHub Copilot extension inside VS Code.
If you wish to use VS Code, then you’d need to use Copilot to get MCP access. If you don’t wish to use VS Code, you can install any other AI assistants like Claude and use that to get MCP access.
Is your VSCode connection to Kite MCP stable? In my case, it keeps getting terminated with error “Error reading SSE stream: TypeError: terminated”. Then I have to manually restart. Connection keeps dropping every minute.
2025-05-28 21:23:57.443 [info] Starting server kite
2025-05-28 21:23:57.444 [info] Connection state: Starting
2025-05-28 21:23:57.464 [info] Starting server from LocalProcess extension host
2025-05-28 21:23:57.481 [info] Connection state: Running
2025-05-28 21:23:57.637 [info] 405 status sending message to https://mcp.kite.trade/sse, will attempt to fall back to legacy SSE
2025-05-28 21:23:58.153 [info] Discovered 18 tools
2025-05-28 21:25:12.779 [info] Connection state: Error Error reading SSE stream: TypeError: terminated
2025-05-28 21:25:16.738 [info] Starting server kite
2025-05-28 21:25:16.738 [info] Connection state: Starting
2025-05-28 21:25:16.754 [info] Starting server from LocalProcess extension host
2025-05-28 21:25:16.765 [info] Connection state: Running
2025-05-28 21:25:16.902 [info] 405 status sending message to https://mcp.kite.trade/sse, will attempt to fall back to legacy SSE
Claude said there is a protocol version mismatch between my Claude AI client and the Kite MCP server. I tried deleting and reinstalling Claude, but that did not help either.
@Matti If you are an engineer then read below.
Try hosting your mcp server on a ec2 or gcp instance once and let Claude connect directly to it.
We faced the same error from Claude update. Ours was hosted on Google Cloud Run which started experiencing issues from Saturday 31st May. Ours also connect using mcp remote library.
We noticed that the setup works well on a local server. We then switched to a gcp instance and let Claude connect directly to it.
We also tried few other options like ECS Fargate which failed.
My hunch is that Gateway is the culprit along with the latest Claude update.