Tracking: MCP proxy support roadmap

[davidruzicka]

Summary

Add first-class MCP proxy support to mcp4openapi so it can expose tools discovered from upstream MCP servers instead of only generating tools from OpenAPI.

Goals

• Support an upstream remote MCP server over streamable HTTP as the first implementation target.
• Keep mcp4openapi transport-compatible for downstream clients while delegating tool discovery and invocation upstream.
• Preserve security-by-default boundaries for upstream auth, tool exposure, and outbound network access.
• Leave room for optional stdio support without forcing the first delivery to solve process isolation immediately.

Scope

This tracking issue groups the implementation plan for MCP proxy support.

Planned child issues

• Define upstream MCP provider model and configuration schema #212 Define upstream MCP provider model and configuration schema
• Implement remote upstream MCP transport and session lifecycle #213 Implement remote upstream MCP transport and session lifecycle
• Forward upstream notifications to downstream SSE clients #214 Forward upstream notifications to downstream SSE clients
• Introduce provider-backed tool discovery and invocation for proxied MCP tools #215 Introduce provider-backed tool discovery and invocation for proxied MCP tools
• Harden upstream auth, tool policy, and proxy security boundaries #216 Harden upstream auth, tool policy, and proxy security boundaries
• Add experimental stdio upstream MCP support behind a feature gate #217 Add experimental stdio upstream MCP support behind a feature gate
• Document and test MCP proxy support end to end #218 Document and test MCP proxy support end to end

Notes

• Start with remote HTTP only.
• Keep stdio explicitly opt-in and gated.
• Treat inbound client auth and upstream auth as separate trust boundaries.
• Prefer explicit allow/deny tool policy and namespacing for upstream tools.

Agent-authored issue.

[github-actions]

🤖 Agent note (issuer)

Autonomy gate decision: unsafe
Reasons:

• issue includes explicit acceptance or validation structure
• issue matches high-risk keywords that should stay in a human lane