[UX] Plugin list displays all MCP connections as mcp-client instead of server names #3768
tang-zhilei
started this conversation in
Ideas
Replies: 1 comment
|
你这个 UX 请求成立,官方那边该修的是显示名。补两条今天就能缓解的: 1. 装一个 MCP 管理界面插件。 npm 上现在有好几个,它们的面板都是按 server 名分组、带状态指示的,正好是你 Expected Behavior 里画的那个形状:
这不改插件列表本身,是在旁边给你一个真正能认出谁是谁的面。 2. 换一种承载形状:一个适配器托管全部 server。 你现在是 N 个 server = N 个 边界说清楚:第 2 条是换掉官方的 MCP 客户端,不是修好它的显示名——你原帖的诉求(官方用 另外:#3766 和这条是同一篇(同标题同正文),要跟进的话合并到一处就行。 利益相关:pi2dsh 是我的;上面那几个 mcp-manager 都不是。 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem Description
When 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.Current Behavior
Users cannot quickly identify which connection corresponds to which MCP server (e.g., mimo-mcp, fetch, context7).
Expected Behavior
The plugin list should display meaningful names that help users identify each connection:
Suggested Improvements
server_info.nameas the display nameEnvironment
Additional Context
This is a UX improvement request. The current functionality works correctly, but the display names are not user-friendly for managing multiple MCP connections.
All reactions