Skip to content

Conversation

@Drakezair
Copy link

Motivation and Context

This change adds support for sending custom headers when establishing a direct HTTP stream connection.
It's necessary for use cases where authentication tokens or other metadata must be sent with the initial request.

How Has This Been Tested?

Tested locally in a real application using both static and dynamic header values.
Verified that headers are correctly set and received on the server side.

Breaking Changes

No breaking changes. Existing connections without custom headers continue to work as before.

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

This change introduces a new configuration option `headers` within the direct connection stream setup.

QuantGeekDev pushed a commit that referenced this pull request Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant