Mark slack-mcp verified and name the toggle it needs - #65
Merged
Conversation
An authorization has now been taken through Gemini Enterprise end to end: consent, code exchange, and a search tool answering through the MCP server. Everything setup listed as read off the server's metadata rather than seen to work is settled, so it says what happened instead of what might. Only refreshing stays unconfirmed - no token issued here has expired yet. The run also turned up a condition setup did not have. Unless the Slack app has Model Context Protocol on under Features -> Agents & AI Apps, the server answers initialize with 400, having already read the token: a correct token looks broken, and the 401 a bad one gets never appears. Setup now says so, and that the toggle costs nothing already granted. 🤖 Generated with Claude Code
Merged
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
1 participant
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.
slack-mcphas now been taken through Gemini Enterprise from end to end:consent screen, code exchange, and the MCP server answering a search call
with results. The entry records that, and one condition it did not have.
setup says what was seen, not what the metadata suggests
The paragraph that opened "No authorization has been taken through Gemini
Enterprise yet" and its five unconfirmed items are replaced by what the run
settled:
secret (post or Basic was not observed, and a connection has no field to
say which)
scope;user_scopewas not neededaccess_typeandprompton the authorization URL are ignoredresource(RFC 8707) is not requiredRefreshing stays unconfirmed: no token issued here has lived long enough to
expire. The
oauth:comments ontoken_url,scope_parameterandauthorization_queryare rewritten the same way.the Model Context Protocol toggle
Setup did not mention it, and it is the one thing that makes a correct token
look broken. With Model Context Protocol off under Features -> Agents & AI
Apps, the server answers
initializewith 400 and "App is not enabled",after it has read the token - a token it does not accept answers 401
invalid_tokeninstead. Turning it on needs neither a reinstall nor a freshauthorization, so a token taken before the toggle keeps working.
tests
tests/conformance/test_catalog.py: the entry is now expected to carry theverification date, setup to name the toggle, the 400, and the reinstall it
does not need, and to leave exactly one line unconfirmed - the refresh one.
Written first, red, then the entry.
Scopes, the optional menu, hosts and token shapes are untouched.