feat(mcp): add Context.dev marketplace connector - #1297
Closed
luoye520ww wants to merge 1 commit into
Closed
Conversation
Collaborator
|
不想加外部源,也没理由给他们到流量 |
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.
Summary
https://mcp.context.dev/mcpwith OAuth 2.1 dynamic client registration and PKCE (no client secret or API key in persisted config).Changes
context-devmarketplace entry with permission/setup preview, HTTPS docs allowlist, and encrypted runtime OAuth configuration.Behavior before
Context.dev had to be added manually as an opaque remote MCP server, with no discoverable preset or OAuth configuration guidance.
Behavior after
Users can open the MCP marketplace, review the Context.dev permission preview, and add a user-scoped streamable HTTP server. Kun's existing MCP OAuth runtime performs interactive authorization and stores tokens in its encrypted OAuth store;
mcp.jsoncontains no credential material.Safety
clientIdandclientSecretremain unset so dynamic registration/PKCE is used; no token is persisted in config or logged.Typecheck
Both passed with exit code 0.
Tests
Actual validation
A local mock-independent OAuth provider/transport test suite passed. Live Context.dev authorization requires a user account and remains the only external validation.
Issue
Fixes #1294