support `streamable-http` transport for mcps

[MatLBS]

[getnao-bot]

🔍 AI Analysis

Summary: Add support for streamable-http transport for MCP servers. Currently only stdio and basic http transport are supported.

Labels: enhancement, mcp, backend

Analysis

The MCP (Model Context Protocol) supports multiple transport types. Currently, the nao MCP integration only supports:

• stdio - local command execution
• http - basic HTTP transport

The streamable-http is a newer transport protocol that provides better streaming support for MCP servers.

Relevant Code Locations

1. MCP config types (apps/backend/src/types/mcp.ts):

   • McpServerConfig interface defines available config options
   • Currently only supports type: 'http' with URL
   • Missing streamable-http support

2. MCP service (apps/backend/src/services/mcp.service.ts):

   • _convertToServerDefinition() converts config to MCPorter definition
   • Handles http type but not streamable-http

3. Example config (example/agent/mcps/mcp.json):

   • Shows current configuration format

Proposed Fix

Step 1: Update config type

// In apps/backend/src/types/mcp.ts
export interface McpServerConfig {
  type?: 'http' | 'streamable-http';
  url?: URL;
  
  // For stdio transport
  command?: string;
  args?: string[];
  env?: Record<string, string>;
  
  // For streamable-http (optional headers, etc.)
  headers?: Record<string, string>;
}

Step 2: Update JSON schema

// In mcpJsonSchema
z.object({
  type: z.enum(['http', 'streamable-http']).optional(),
  // ...
})

Step 3: Update service

// In _convertToServerDefinition()
if (config.type === 'streamable-http') {
  return {
    name,
    command: {
      kind: 'streamable-http',
      url: config.url!,
      headers: config.headers,
    },
  };
}

Alternative Solutions

1. Use headers for existing http: Some MCP servers accept auth headers in the URL
2. Proxy through backend: Have nao backend proxy requests (more complex)
3. Wait for MCPorter: Check if future MCPorter versions add native support

Suggested Next Steps

1. Add streamable-http to the config type and schema
2. Update _convertToServerDefinition() to handle the new transport
3. Test with an MCP server that requires streamable-http
4. Document the new config option

---

AI-assisted analysis