refactor: restrict mcp_catalog to oauth and none auth only#2988
Merged
Conversation
rumpl
previously approved these changes
Jun 3, 2026
231eca6 to
0fb497e
Compare
0fb497e to
e285904
Compare
rumpl
approved these changes
Jun 3, 2026
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.
The MCP catalog feature currently requires manual API key management for 12 of its 51 servers. Most users don't need these, and their configuration overhead adds unnecessary complexity. This change simplifies the catalog by supporting only OAuth and anonymous-access servers, which can be fully managed by the framework.
The refactor removes all API key machinery from the MCP catalog code, drops 12 rarely-used servers from the built-in registry, and updates callers and tests accordingly. The catalog shrinks from 51 to 39 servers but becomes much simpler to use and maintain. Users who need the removed servers can still set them up manually as custom MCP servers.
The change is backwards-incompatible for anyone explicitly using the removed servers in their config, but as an internal feature not yet documented in release notes, this is acceptable.