-
Notifications
You must be signed in to change notification settings - Fork 2
document vMCP remote server support #406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR documents the new vMCP feature that enables MCPRemoteProxy resources to be aggregated alongside MCPServer resources by VirtualMCPServer, providing a unified endpoint for both local container-based and remote MCP servers.
Key changes include:
- Updated vMCP documentation to describe support for both MCPServer and MCPRemoteProxy backend types
- Added configuration examples showing how to add remote proxies to MCPGroups
- Extended the remote MCP proxy guide with a dedicated section on vMCP integration
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/toolhive/guides-vmcp/intro.mdx | Updated overview and architecture diagram to show MCPRemoteProxy as a supported backend type alongside MCPServer |
| docs/toolhive/guides-vmcp/configuration.mdx | Added "Add backends to a group" section with YAML examples for both MCPServer and MCPRemoteProxy configurations |
| docs/toolhive/guides-k8s/remote-mcp-proxy.mdx | Added "Use with Virtual MCP Server" section explaining how to add remote proxies to MCPGroups and the benefits of vMCP aggregation |
| docs/toolhive/concepts/vmcp.mdx | Updated multi-server aggregation section to mention MCPRemoteProxy support and mixed backend scenarios |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.
| remoteURL: https://mcp.analytics.example.com | ||
| transport: streamable-http | ||
| port: 8080 | ||
| oidcConfig: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does the oidcConfig here mean? Is it a token that vMCP sends?
| - **Unified endpoint**: Clients connect to one vMCP URL instead of multiple | ||
| proxy endpoints | ||
| - **Centralized authentication**: vMCP handles client authentication; remote | ||
| proxies validate the forwarded tokens |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume we can't auth to remote servers as of yet?
| namespace: toolhive-system | ||
| spec: | ||
| groupRef: dev-tools | ||
| remoteURL: https://mcp.analytics.example.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we use a real MCP server in the example?
Description
Documents the new vMCP feature that enables MCPRemoteProxy resources to be grouped with MCPServer resources and aggregated by VirtualMCPServer into a single unified endpoint.
Changes include:
groupRefusage and benefits of vMCP aggregationType of change
Related issues/PRs
Screenshots
N/A - content updates only, no structural changes
Submitter checklist
Content and formatting
Navigation
N/A - No pages were added, deleted, renamed, or reordered. Only content updates to existing pages.
Reviewer checklist
Content