Introducing Kite MCP: Connect your Kite account to AI assistants

for VS Code try this add the server to settings.json

   "mcp": {
        "inputs": [],
        "servers": {
            "kite": {
                "url": "https://mcp.kite.trade/sse"
            }
        }
    }

Ref below link
Connect your Zerodha account to AI assistants with Kite MCP – Z-Connect by Zerodha

once added start the MCP server of kite

go to VSCODE command palette and list the server

then you can able to do the same as on Claude Desktop

# on copilot chat show the options available on kite MCP server

have a nice day prompting guys

I am confused,
I don’t want to install unnecessary stuff on my trading PC.

Do you mean

GitHub Copilot Chat (Free for students and open-source devs)
Requires GitHub Education Pack or open-source contributor status

You do not need GitHub Copilot unless:

  • You specifically want to use Copilot Chat inside VS Code
  • You want AI-assisted code suggestions with MCP access

Pls clarify.

@zerodha Team

@Rajesh_K1

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.

1 Like

this is not applicable to me as i want un restricted prompt access.

So essentially, that means I need this.

If I want this

Man this should have been in the info at the first place, not everyone here is a developer.
:expressionless:

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.

1 Like

Pls make a video of this.

You may refer to this YouTube video to understand the steps to install Copilot in VS Code.

1 Like

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

2025-05-28 21:25:17.576 [info] Discovered 18 tools

Can you help? I am getting this
CleanShot 2025-05-30 at 18.25.42

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.

1 Like

Hi Matti, I don’t see any option to DM in this platform. Can I drop a mail or reach out to you elsewhere?

We’ll check this.

Can you check if there is a newer version of VSCode than what you are using?

Same problem…

We are checking this and will provide an update shortly.

@Matti - I am getting exactly the same error as @Renjith_Pillai

Can you pls help. Attaching the error logs.

Looks like Claude has changed something on their end breaking the integration. We’re working on fixing this.

2 Likes


I have been trying to integrate i don’t know wat to do its showing this i don’t know how to fix this

i am facing the same issue

@Khushboo_Jain

We’re still working on fixing this. Meanwhile, you can use Kite MCP via VS Code alternatively.

@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.

Got this forum from this tweet .