Allow add extra headers for remote server connection #149
+18
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow add extra headers for remote server connection like
bearer tokenMotivation and Context
Many MCP servers require authentication via a bearer token. By allowing clients to specify custom header values, this approach supports bearer token authentication and provides flexibility for servers that require additional or specialized headers.
How Has This Been Tested?
Yes. I can use this to connect to GitHub MCP server by adding bearer token.
Breaking Changes
No. The newly added header parameter has default empty value.
Types of changes
Checklist
Additional context