[UX] Plugin list displays all MCP connections as mcp-client instead of server names

[tang-zhilei]

Problem Description\n\nWhen multiple MCP servers are configured in DSH Web, the plugin list displays all connections with the same name mcp-client, making it difficult to identify and manage individual MCP server connections.\n\n## Current Behavior\n\n\nPlugin List:\n├── mcp-client\n├── mcp-client\n└── mcp-client\n\n\nUsers cannot quickly identify which connection corresponds to which MCP server (e.g., mimo-mcp, fetch, context7).\n\n## Expected Behavior\n\nThe plugin list should display meaningful names that help users identify each connection:\n\n\nPlugin List:\n├── MiMo MCP (mimo-mcp)\n├── Web Fetch (fetch)\n└── Context7 Docs (context7)\n\n\n## Suggested Improvements\n\n1. Display Server Name: Use the MCP server's server_info.name as the display name\n2. Support Custom Aliases: Allow users to set custom names for each connection in configuration\n3. Show Connection Status: Include visual indicators (✅ connected / ❌ disconnected / ⚠️ error)\n\n## Environment\n\n- DSH Version: latest\n- OS: Windows\n- MCP Servers configured: mimo-mcp, fetch, context7, sequential-thinking, knowledge-graph\n\n## Additional Context\n\nThis is a UX improvement request. The current functionality works correctly, but the display names are not user-friendly for managing multiple MCP connections.