Add upstream MCP proxy backend for guarded passthrough tools #24
No reviewers
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/mcp-beaver!24
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-18"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This adds a guarded upstream MCP proxy backend for streamable-HTTP servers. The proxy snapshots an allowlisted upstream tool surface, preserves the upstream tool schema where possible, and fails closed on unknown tools or schema drift.
serve-upstreamfor the proxy backendgo build ./...,go vet ./..., andgo test ./...closes #18
ward.workflow: pull-request-and-merge