Conversation
Product plugins had no stable way to install a declared remote MCP connector. They either had to reach into MCP internals or make an authenticated HTTP call back into their own machine, and neither preserved the MCP plugin as the owner of OAuth and credentials. Add the tokenless McpConnectorPort to the public Harness contract. The MCP plugin provides install, DCR authorization and sanitized status through that port; installed headers are strict vault-key/template bindings resolved only while dialing. A changed remote endpoint clears pending and persisted OAuth state, while the owner-facing OAuth route now delegates to the same DCR implementation. Proven with focused MCP connector and OAuth tests, TypeScript typecheck, package build, dist health smoke, and boundary check. The full suite was also run but has a pre-existing Node 26 timing failure in src/shutdown.test.ts, whose shutdown socket assertion observed 0ms instead of its required >=49ms. This does not add product pack manifests, platform UI, or brokered OAuth; those remain product-plugin responsibilities.
mikield
added this pull request to stack #5
September 11, 2026 02:55
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.
Product plugins had no stable way to install a declared remote MCP connector. They either had to reach into MCP internals or make an authenticated HTTP call back into their own machine, and neither preserved the MCP plugin as the owner of OAuth and credentials.
Add the tokenless McpConnectorPort to the public Harness contract. The MCP plugin provides install, DCR authorization and sanitized status through that port; installed headers are strict vault-key/template bindings resolved only while dialing. A changed remote endpoint clears pending and persisted OAuth state, while the owner-facing OAuth route now delegates to the same DCR implementation.
Proven with focused MCP connector and OAuth tests, TypeScript typecheck, package build, dist health smoke, and boundary check. The full suite was also run but has a pre-existing Node 26 timing failure in src/shutdown.test.ts, whose shutdown socket assertion observed 0ms instead of its required >=49ms.
This does not add product pack manifests, platform UI, or brokered OAuth; those remain product-plugin responsibilities.