Problem (one or two sentences)

Issue: VS Code extensions (Cline, Roo Code, Kilo Code) use divergent type field naming for MCP server configs, preventing configuration portability:

Different tools use inconsistent naming conventions for the MCP type field:

Examples:

// Cline: camelCase
{
  "mcpServers": {
    "Context7": {
      "disabled": false,
      "timeout": 60,
      "type": "streamableHttp", 
      "url": "https://mcp.context7.com/mcp"
    },
    "DeepWiki": {
      "disabled": false,
      "timeout": 60,
      "type": "streamableHttp", 
      "url": "https://mcp.deepwiki.com/mcp"
    }
  }
}

// Roo/Kilo Code: kebab-case
{
  "mcpServers": {
    "Context7": {
      "disabled": false,
      "timeout": 60,
      "type": "streamable-http", 
      "url": "https://mcp.context7.com/mcp"
    },
    "DeepWiki": {
      "disabled": false,
      "timeout": 60,
      "type": "streamable-http", 
      "url": "https://mcp.deepwiki.com/mcp"
    }
  }
}

// mcp-use/LangChain: snake_case
{
  "mcpServers": {
    "Context7": {
      "disabled": false,
      "timeout": 60,
      "type": "streamable_http", 
      "url": "https://mcp.context7.com/mcp"
    },
    "DeepWiki": {
      "disabled": false,
      "timeout": 60,
      "type": "streamable_http", 
      "url": "https://mcp.deepwiki.com/mcp"
    }
  }
}

// VS Code/NuxtUI
{
  "servers": {
    "github-mcp": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp"
    }
  }
}

Users must maintain separate configs or modify code—impractical for packaged apps.

Plugin-Host Relationship: As extensions running within VS Code's environment, these tools should follow their host platform's established standards. VS Code documentation explicitly defines supported transport types: stdio, http (Streamable HTTP), and sse (legacy).

Recommendation: Standardize on http to match VS Code's official specification.

References:

• Cline: Does cline support http type MCPSERVER request connections? cline/cline#5108
• Roo Code: feat: add OAuth authentication support for streamable-http MCP servers #7297
• mcp-use: https://github.com/mcp-use/mcp-use
• langchain: Solved 322: Confusion with streamable_http vs streamable-http transport naming langchain-ai/langchain-mcp-adapters#323
• NuxtUI: https://ui.nuxt.com/docs/getting-started/ai/mcp
• VS Code: https://code.visualstudio.com/docs/copilot/customization/mcp-servers
• screenshot: https://code.visualstudio.com/docs/copilot/customization/mcp-servers

Context (who is affected and when)

VS Code extension developers and users configuring MCP servers.

Desired behavior (conceptual, not technical)

All VS Code MCP extensions should use "type": "http" (not "streamableHttp",
"streamable-http", or "streamable_http") to match VS Code's official standard.

Configurations should work across extensions without modification.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response