🔧 fix: Fix rampant pings and rate limiting

- Skips idle connection checks in `getMCPManager` to avoid unnecessary pings.
- Introduces a skipOAuthTimeout flag during initial connection to prevent timeouts during server discovery.
- Uses a lightweight connection state check instead of ping to avoid rate limits.
- Prevents refetch spam and rate limit errors when checking connection status.
- Fixes an issue where the server connection was not being disconnected.

api/server/controllers/PluginController.js

@@ -97,7 +97,6 @@ function createServerToolsCallback() {
         return;
       }
       await mcpToolsCache.set(serverName, serverTools);
-      logger.warn(`MCP tools for ${serverName} added to cache.`);
     } catch (error) {
       logger.error('Error retrieving MCP tools from cache:', error);
     }
@@ -240,7 +239,6 @@ const getAvailableTools = async (req, res) => {
         // Check if the app-level connection is active
         try {
           const mcpManager = getMCPManager();
-          const allConnections = mcpManager.getAllConnections();
 
           const appConnection = mcpManager.getConnection(serverName);
 

api/server/controllers/UserController.js

@@ -182,7 +182,7 @@ const updateUserPluginsController = async (req, res) => {
               `[updateUserPluginsController] Disconnecting MCP connection for user ${user.id} and server ${serverName} after plugin auth update for ${pluginKey}.`,
             );
             // Don't kill the server connection on revoke anymore, user can just reinitialize the server if thats what they want
-            // await mcpManager.disconnectUserConnection(user.id, serverName);
+            await mcpManager.disconnectUserConnection(user.id, serverName);
           }
         } catch (disconnectError) {
           logger.error(