Skip to content

Conversation

@daixijun
Copy link

@daixijun daixijun commented Nov 14, 2025

What this enables:

  • Clients can accept either Server-Sent Events (SSE) or JSON responses
  • Flexible content negotiation based on server preferences
  • Improved interoperability with different MCP server implementations

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

What this enables:

- Clients can accept either Server-Sent Events (SSE) or JSON responses
- Flexible content negotiation based on server preferences
- Improved interoperability with different MCP server implementations
@github-actions github-actions bot added T-core Core library changes T-transport Transport layer changes labels Nov 14, 2025
@jokemanfire
Copy link
Collaborator

test fail check pls.

@daixijun
Copy link
Author

image

It works correctly on my local machine, can you try again?

test fail check pls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-core Core library changes T-transport Transport layer changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants