feat: add RooCode User-Agent header to MCP server requests #9813
+26
−4
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.
This PR attempts to address Issue #9810.
Summary
Adds the "User-Agent: RooCode/{version}" header to MCP server HTTP requests to match the header format used in API requests.
Changes
Context
Previously, MCP server requests were sending a default "User-Agent: node" header. This change ensures that MCP requests are properly identified as coming from RooCode, improving observability for MCP hosts tracking source agents.
Fixes #9810
Feedback and guidance are welcome!