MCP Server OAuth support

[deepaknlwl]

MCP servers requiring OAuth authentication fail with 401 errors

Problem

When connecting to remote MCP (Model Context Protocol) servers that require OAuth 2.1 authentication, KiloCode fails with 401 (Unauthorized) errors. The extension does not support OAuth authentication flows, making it impossible to use MCP servers that require bearer token authentication.

Description

Remote MCP servers using SSE (Server-Sent Events) or Streamable HTTP transports often require OAuth 2.1 bearer token authentication. When KiloCode attempts to connect to these servers:

1. The MCP SDK detects that authentication is required
2. The server returns a 401 Unauthorized error
3. KiloCode has no mechanism to handle OAuth flows
4. The connection fails permanently
5. Users cannot use these MCP servers

This affects any MCP server that:

• Uses OAuth 2.1 for authentication
• Requires bearer tokens in HTTP headers