Skip to content

vMCP: Use proxy-mode instead of transport #2413

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 31, 2025
Merged

vMCP: Use proxy-mode instead of transport #2413

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion pkg/vmcp/aggregator/cli_discoverer.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,11 +74,20 @@ func (d *cliBackendDiscoverer) Discover(ctx context.Context, groupRef string) ([
healthStatus := mapWorkloadStatusToHealth(workload.Status)

// Convert core.Workload to vmcp.Backend
// Use ProxyMode instead of TransportType to reflect how ToolHive is exposing the workload.
// For stdio MCP servers, ToolHive proxies them via SSE or streamable-http.
// ProxyMode tells us which transport the vmcp client should use.
transportType := workload.ProxyMode
if transportType == "" {
// Fallback to TransportType if ProxyMode is not set (for direct transports)
transportType = workload.TransportType.String()
}

backend := vmcp.Backend{
ID: name,
Name: name,
BaseURL: workload.URL,
TransportType: workload.TransportType.String(),
TransportType: transportType,
HealthStatus: healthStatus,
Metadata: make(map[string]string),
}
Expand Down
Loading