Running multiple instances of same MCP server with different configs? #9633

Activity

1. github-actions

   assigned

   thdxr

   on Jan 20, 2026
2. cvrt-jh commented on Jan 20, 2026

   

   cvrt-jh

   on Jan 20, 2026

   Author

   More actions

   Closing to repost with anonymized data - accidentally included personal email addresses.
3. cvrt-jh

   closed this as not plannedon Jan 20, 2026
4. github-actions commented on Jan 20, 2026

   

   github-actionsBot

   on Jan 20, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [Bug] Web UI spawns duplicate MCP server waves during active session #9230: Web UI spawns duplicate MCP server waves during active session
   • [FEATURE]: MCP auth configuration for multi-tenant serve deployments #5784: MCP auth configuration for multi-tenant serve deployments
   • feat: add per-session MCP server support for REST API (parity with ACP) #7004: Add per-session MCP server support for REST API (parity with ACP)
   • Feature: Pass session identifier to MCP servers #6279: Feature - Pass session identifier to MCP servers
   • WSL2/devcontainer: MCP OAuth callback unreachable from host browser (Sentry) #9081: WSL2/devcontainer - MCP OAuth callback unreachable from host browser
   • All MCP oauth flow return potential CSRF attack #9510: All MCP oauth flow return potential CSRF attack
   • Memory leak: MCP OAuth transports not closed on retry or cancellation #9153: Memory leak - MCP OAuth transports not closed on retry or cancellation
   • [FEATURE]: support config.d/ directory for modular configuration #9062: Support config.d/ directory for modular configuration
   • [FEATURE]: Expose session context to child processes via environment variables #9292: Expose session context to child processes via environment variables
   • add ability to load secrets from external command or environment variables in the config file #231: Add ability to load secrets from external command or environment variables in the config file

   Feel free to ignore if none of these address your specific case.