-
Notifications
You must be signed in to change notification settings - Fork 236
Open
Description
Problem
The MCP connectors UI currently allows users to add the same custom MCP server multiple times, but these duplicate entries do not appear in the connectors list (component: @/components/connectors-provider). Additionally, there is no way to edit custom MCP servers after they are added. This leads to user confusion and makes it hard to manage MCP server configurations.
Technical Solution (tested in fork)
The solution I found is to:
- Refactor the MCP server management logic and connectors-provider UI so that all MCP servers (custom and preset) are tracked in a unified list and rendered immediately after creation.
- Add validation in the UI (and optionally in the backend) to block duplicate MCP server entries by checking for servers with the same configuration before allowing creation.
- Make sure the connectors-provider UI displays all custom MCP servers and provides an option to delete them, so users can remove unwanted servers.
- Apply the same logic for rendering and managing both preset and custom MCP servers to avoid inconsistencies.
This approach ensures all MCP servers are visible and manageable, prevents accidental duplicates, and improves the user experience for server configuration.
Component to review: @/components/connectors-provider
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels