RFC: MCPRemoteEndpoint CRD — Unified Remote MCP Server Connectivity#67
Draft
RFC: MCPRemoteEndpoint CRD — Unified Remote MCP Server Connectivity#67
Conversation
Introduces MCPRemoteEndpoint, a single CRD that unifies remote MCP server connectivity with two explicit modes: type: proxy (deploys a proxy pod with full auth/authz/audit) and type: direct (pod-less, config-only). Deprecates both MCPRemoteProxy and MCPServerEntry (THV-0055) once GA. MCPServerEntry (THV-0055) ships first as a near-term solution; this RFC defines the long-term replacement. Co-authored-by: Chris Burns <chris@chrisjburns.com> Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Introduces
MCPRemoteEndpoint, a single CRD that unifies remote MCP server connectivity with two explicit modes:type: proxy— deploys a proxy pod with full auth middleware, authz policy, and audit logging (replacesMCPRemoteProxy)type: direct— no pod deployed; VirtualMCPServer connects directly to the remote URL (replacesMCPServerEntry)Relationship to THV-0055 (MCPServerEntry)
MCPServerEntry(PR #55) ships first as a near-term solution for direct remote backends behind vMCP. This RFC defines the long-term replacement that unifies both direct and proxy modes under a single resource. OnceMCPRemoteEndpointreaches GA, bothMCPRemoteProxyandMCPServerEntryenter a deprecation window.Test plan
🤖 Generated with Claude Code