Skip to content

Prioritize HTTP transport protocol for MCP server - SSE is being deprecated #44

@jayscambler

Description

@jayscambler

Context

MCP currently supports 3 transport protocols: stdio, SSE, and HTTP. According to recent discussions, HTTP is replacing SSE as the preferred transport protocol because "SSE was a stupid idea".

Current State

Based on the codebase structure, we have:

  • Phase 3.1: Transport abstraction already implemented
  • Phase 3.5: HTTP transport implementation exists in contextframe/mcp/transports/http/

Task

We need to ensure that:

  1. HTTP transport is fully implemented and tested
  2. Documentation is updated to reflect HTTP as the preferred transport over SSE
  3. SSE is marked as deprecated with migration guides
  4. Examples and tests prioritize HTTP transport

Implementation Details

The HTTP transport implementation should:

  • Follow the MCP specification for HTTP transport
  • Support all MCP operations (tools, resources, prompts)
  • Include proper error handling and retries
  • Support both sync and async operations
  • Include comprehensive tests

References

  • MCP Transport Protocols: stdio, sse, http
  • Current branch: jay/cfos-27-mcp-server-components
  • Existing HTTP transport code: contextframe/mcp/transports/http/

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions