Simplify MCP gateway after Bifrost migration #8

Open
opened 2026-05-26 04:21:01 +00:00 by fkrebs · 1 comment
Owner

With Bifrost routing MCP natively + OWUI speaking MCP directly, custom mcp-gateway on CT 104 loses its routing role.

Keep only if it does:

  • (a) STDIO lifecycle for spawn MCP servers (Bifrost needs running servers — check whether it lifecycle-manages STDIO)
  • (b) Central secret injection beyond Bifrost VKs
  • (c) Path for non-LLM MCP clients bypassing Bifrost

Action:

  1. Test whether Bifrost can spawn catalog/spawn MCP servers in DinD style
  2. If yes: retire mcp-gateway entirely
  3. If no: keep as STDIO supervisor, put Bifrost in front for governance

Depends-on: LiteLLM→Bifrost issue.

With Bifrost routing MCP natively + OWUI speaking MCP directly, custom `mcp-gateway` on CT 104 loses its routing role. **Keep only if** it does: - (a) STDIO lifecycle for spawn MCP servers (Bifrost needs running servers — check whether it lifecycle-manages STDIO) - (b) Central secret injection beyond Bifrost VKs - (c) Path for non-LLM MCP clients bypassing Bifrost **Action:** 1. Test whether Bifrost can spawn catalog/spawn MCP servers in DinD style 2. If yes: retire `mcp-gateway` entirely 3. If no: keep as STDIO supervisor, put Bifrost in front for governance Depends-on: LiteLLM→Bifrost issue.
Author
Owner

Partially done 2026-05-26: _litellm_sync_loop and _lobechat_sync_loop disabled in mcp-gateway/server.py. LiteLLM decommissioned. Full MCP gateway sunset (Phase 3) deferred.

Partially done 2026-05-26: _litellm_sync_loop and _lobechat_sync_loop disabled in mcp-gateway/server.py. LiteLLM decommissioned. Full MCP gateway sunset (Phase 3) deferred.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fkrebs/docs#8