[UI Bug] MCP Registry search does not filter server descriptions
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by locating the MCP Registry UI search entry point and tracing which server fields it searches; the issue does not name files or tests. Review the search discussion in Issue #13 for relevant context, then add description matching alongside name matching with partial keyword support. Done when a query found only in a server description returns that server.
由索引模型根据 Issue 内容生成。
描述
Description
The search functionality in the MCP Registry UI does not appear to search or filter MCP servers based on their descriptions.
Currently, users have difficulty discovering relevant MCP servers unless they already know the server name or an exact keyword associated with it.
Searching by functionality or use case should also return MCP servers whose descriptions contain the relevant terms.
Steps to Reproduce
- Open the MCP Registry UI.
- Enter a keyword or phrase related to an MCP server's functionality.
- Check whether servers with matching terms in their descriptions appear.
- Observe that relevant servers may not be returned when the search term exists only in the description.
Expected Behaviour
- Search should include MCP server names and descriptions.
- Matching keywords in descriptions should return relevant MCP servers.
- Search should support partial keyword matching.
- Users should be able to discover servers based on functionality and use cases, not just server names.
Actual Behaviour
The search does not appear to consider the description field, making it difficult to discover relevant MCP servers based on their capabilities.
Suggested Improvement
Extend the existing search functionality to include the description field alongside server names.
Consider supporting keyword-based matching across metadata fields to improve search relevance and discoverability as the registry grows.
Related Discussion
This issue is related to the earlier discussion in Issue #13, which also touches on registry search behaviour.
It would be useful to revisit this discussion when implementing the improvement.
Impact
Improving description-based search will:
- Make MCP discovery easier for developers and users.
- Improve visibility of MCP servers based on their actual capabilities.
- Reduce dependency on knowing exact server names.
- Improve the overall usability and discoverability of the MCP ecosystem.
Priority: Medium – Search usability and discoverability.
- 主要语言
- Go
- 星标
- 7.4k
- 派生
- 1k
- 平均合并
- 17 小时 57 分钟
- 30 天内合并 PR
- 68
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/registry 的其他 Issue
-
3 registry records that cannot resolve for any client, and a caution about single-pass dead counts未关闭
难度 2/5 1-3 小时 新手友好度 68/100
modelcontextprotocol/registry#1692 ·
维护者通常 1 天内回复
-
IsValidRemoteURL only blocks literal localhost/127.0.0.1 — misses [::1], 127.0.0.0/8, 0.0.0.0, and private/link-local addresses可能已有人在做 @amitvijapur 于 108 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/registry#1465 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
modelcontextprotocol/registry#1805 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 49/100
modelcontextprotocol/registry#1792 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 28/100
modelcontextprotocol/registry#1789 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/registry 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 67/100
adrianbrad/queue#92 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
-
agent-ready area:skills
难度 2/5 1-3 小时 新手友好度 75/100
jmbarzee/temporal-architect#444 ·
维护者通常 1 天内回复
-
enhancement needs:sonnet ready-for-agent
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复