🗃️ docs: Update MCP docs for new settings panel behavior and to clarify configuration/initialization steps for non OAuth MCP servers like github-mcp (#373)

pages/docs/configuration/librechat_yaml/object_structure/mcp_servers.mdx

@@ -352,8 +352,11 @@ my-mcp-server:
     API_KEY: # This key will be used as {{API_KEY}} in headers/url
       title: "API Key" # This is the label shown above the input field
       description: "Get your API key <a href='https://example.com/api-keys' target='_blank'>here</a>." # This description appears below the input
+  startup: false # This server will not be connected at application startup since it requires the information provided by the user in customUserVars.
 ```
 
+ **NOTE** See [MCP Server Initialization](/docs/features/mcp#server-initialization) for more information about UI based server initialization.
+
 ### MCP Server with Custom Icon
 
 ```yaml filename="MCP Server with Icon"

pages/docs/features/mcp.mdx

@@ -180,6 +180,17 @@ You can initialize or re-initialize MCP servers directly from the interface:
      >
        <source src="/videos/mcp_settings_init.mp4" />
      </video>
+
+
+### MCP Settings Panel Visibility
+
+The MCP Settings Panel appears in the right sidebar when LibreChat detects MCP servers that might require user intervention during their initialization. The panel will be visible when any configured server meets one of these criteria:
+
+- **Custom User Variables**: Server has `customUserVars` defined which may contain user-provided credentials
+- **OAuth Authentication**: Server is detected as requiring OAuth authentication during startup
+- **Manual Initialization**: Server has `startup: false` configured, requiring manual initialization
+
+
 ## LibreChat-Specific Features
 
 LibreChat's MCP implementation is designed for highly configurable, real-world, multi-user environments.