🔑 refactor: MCP Settings Rendering Logic for OAuth Servers

[dustinhealy]

Summary

This pull request enhances the MCP Settings panel rendering logic to show when servers need user interaction for configuration, authentication, or initialization. The panel will now render if a server is detected that:

• has CustomUserVars
• was detected as an OAuth server during startup
• has startup: false configured in librechat.yaml

This replaces the previous filtering logic which only checked for customUserVars.

Server-side changes:

• api/server/routes/config.js: Added dependency on getMCPManager and updated the route handler to include three new properties in the payload:
  • isOAuth: Determines if server requires OAuth by checking getMCPManager().getOAuthServers()
  • startup: Includes the startup configuration flag from server config

Client-side changes:

• client/src/hooks/Nav/useSideNavLinks.ts: Updated navigation logic to render MCPPanel when servers meet any of the previously mentioned criteria.

• client/src/locales/en/translation.json: Added new localization string for empty state handling: com_sidepanel_mcp_no_custom_vars

Configuration updates:

• packages/data-provider/src/config.ts: Added new optional properties to TStartupConfig type:
  • isOAuth: Boolean indicating OAuth requirement detection
  • startup: Boolean reflecting server startup configuration

UX/UI Improvements:

• Enhanced empty state handling: CustomUserVarsSection now displays "No custom user variables set for {serverName}" instead of rendering nothing when no variables are configured.

• Improved section organization: Reordered MCP panel sections to show Custom User Variables first, followed by Server Initialization, creating a more logical user flow.

• Better visual design: Updated ServerInitializationSection styling:

  • Changed from red-themed alert styling to amber background (better semantic meaning)
  • Updated action buttons from blue to green (follows app design patterns)
  • Improved contrast and accessibility in light / dark modes

• Smarter initialization controls: The subtle reinitialize button now only appears for connected servers that actually need it (servers with OAuth requirements or custom user variables), preventing unnecessary UI clutter.

Bug Fixes:

• Fixed reinitialize endpoint: Corrected improper handling of failure states in the MCP server reinitialize endpoint to prevent misleading success toasts.

• Enhanced component props: Added hasCustomUserVars prop to ServerInitializationSection to enable conditional rendering of initialization controls.

Change Type

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• This change requires a documentation update

Testing

Manual verification of MCP Settings Panel presence/absence in SideNav with various MCP server configurations:

• Servers with customUserVars
• OAuth-required servers
• Servers with startup: false
• Servers without any configuration needs
• Mixed combinations of the above
• Empty state handling for servers without custom variables
• Visual styling across light and dark modes

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• A pull request for updating the documentation has been submitted.