Skip to content

feat(http): support multiple URL toolsets - #3362

Open
yaohuangguan wants to merge 1 commit into
github:mainfrom
yaohuangguan:feat/multi-toolset-url
Open

yaohuangguan wants to merge 1 commit into
github:mainfrom
yaohuangguan:feat/multi-toolset-url

Conversation

@yaohuangguan

Copy link
Copy Markdown

Closes #3233.

Summary

Allow the URL-addressable remote toolset route to accept the same comma-separated toolset list as the X-MCP-Toolsets header.

For example:

/mcp/x/default,actions,projects
/mcp/x/repos,issues/readonly

The URL path reuses headers.ParseCommaSeparated, so normalization matches the existing header path. URL-selected toolsets continue to take precedence over X-MCP-Toolsets.

Tests

  • Added route coverage for multiple URL toolsets
  • Added coverage for /readonly composition
  • Added coverage for URL-over-header precedence
  • Ran go test ./...
  • Ran the documentation generator and git diff --check

@yaohuangguan
yaohuangguan requested a review from a team as a code owner October 2, 2026 01:17
Copilot AI balanced review requested due to automatic review settings October 2, 2026 01:17

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

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.

Support multiple remote toolsets via URL for managed MCP clients without custom headers

2 participants