Add oauth.authServerMetadataUrl hint to bundled .mcp.json#42
Closed
potluck wants to merge 1 commit into
Closed
Conversation
Users installing the Val Town plugin from the directory get no auth prompt and no working tools, with no error surfaced (repro + network trace in val-town/plugins#<issue>). The plugin-install client path never attempts a connection to the MCP server at all, so this alone won't fix that — the actual gap is in the install/first-use trigger logic on the claude.ai side (see anthropics/claude-code#36307 and anthropics/claude-ai-mcp#359, which reports the marketplace sync pipeline silently drops the oauth block from bundled .mcp.json files). Adding this now so we're ready once that's fixed upstream.
|
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.
Summary
oauth.authServerMetadataUrlhint pointing athttps://api.val.town/.well-known/oauth-authorization-serverto bothplugin/.mcp.jsonandplugin/mcp.json.Why
While debugging #41 (installing the plugin never triggers auth, tools silently unavailable), we found the plugin manifest schema supports an optional
oauthblock on an MCP server entry, which our config wasn't using.This alone does not fix #41 — the network trace in that issue shows the plugin-install flow never attempts a connection to the MCP server at all, so no client-side hint here changes that. It's also likely to be silently stripped during marketplace sync per anthropics/claude-ai-mcp#359. Adding it anyway since it's low-risk/correct, and puts us in a better position once #359 and the underlying install-flow gap are fixed upstream.
Test plan