docs: document reset_remote_mcp_server_auth meta-tool#2874
Merged
Conversation
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
This is a documentation-only change adding a description of the new reset_remote_mcp_server_auth meta-tool to examples/mcp_catalog.yaml. The diff is accurate and consistent with the described behavior.
Reviewed: examples/mcp_catalog.yaml (+15 lines, documentation comment update)
No bugs, security issues, or correctness problems were found in the changed lines.
melmennaoui
approved these changes
May 22, 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_catalogtoolset now exposes a fifth meta-tool,reset_remote_mcp_server_auth, that allows users to clear persisted OAuth credentials for a remote MCP server. This is useful when an access token was revoked, authorization scopes changed, or the user needs to sign in with a different account.This change updates the example configuration to document the new meta-tool and clarify when it becomes available. The implementation already supports the feature; this is purely a documentation update to keep the example in sync with the actual toolset behavior.
The meta-tool is only exposed once at least one server is enabled and is a no-op for servers using
api_keyornoneauthentication.