-
Notifications
You must be signed in to change notification settings - Fork 0
MCP Driver part 2: Streamable HTTP transport #54
Copy link
Copy link
Open
Labels
complexity:complexHigh effort, significant design neededHigh effort, significant design neededphase:executionRouter, driversRouter, driverspriority:mediumImportant but not blockingImportant but not blockingsize:MMedium change, 50 to 200 linesMedium change, 50 to 200 linestype:featureNew functionalityNew functionality
Milestone
Metadata
Metadata
Assignees
Labels
complexity:complexHigh effort, significant design neededHigh effort, significant design neededphase:executionRouter, driversRouter, driverspriority:mediumImportant but not blockingImportant but not blockingsize:MMedium change, 50 to 200 linesMedium change, 50 to 200 linestype:featureNew functionalityNew functionality
Parent: #41 | Split: Streamable HTTP transport
Problem
This is part 2 of #41 (MCP Driver). It covers the Streamable HTTP transport — connecting to remote MCP servers over HTTP — and reconnection handling for long-lived connections.
Depends on the core MCPDriver + stdio transport (part 1).
Proposed Change
1. Streamable HTTP transport
mcp.client.streamable_http.streamable_http_client.MCPDriver.from_http(url).async withprotocol.2. Extended response handling
structuredContent) when available.Acceptance Criteria
MCPDriver.from_http()connects to a Streamable HTTP MCP serverstructuredContent) is properly handleddocs/integrations.mdupdated with real usage examples for both transportsAffected Files
src/agent_kernel/drivers/mcp.py(extend with HTTP transport)tests/test_drivers.py(HTTP transport tests)docs/integrations.md(usage examples)Dependencies