modelcontextprotocol / modelcontextprotocol/inspector
[Discussion] Semantic/fuzzy tool search instead of exact-substring filtering
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.9k
- Forks
- 1.5k
- Avg merge
- 6h 17m
- Merged PRs (30d)
- 151
Description
Which client?
All / shared core
The problem
When a server exposes many similarly-named tools, exact-substring search (once TUI/web have it uniformly) can still make it hard to find the right one if you don't remember its exact name.
Solution you have in mind (optional)
Layer a lightweight fuzzy-match (e.g. Fuse.js, already common in this kind of UI) on top of the search input(s) discussed in the parity-gap issue above (#2430). Flagging as a discussion/nice-to-have rather than a concrete request.
Alternatives or workarounds you have tried
No response
Already built it locally?
No response
Before you submit
- I searched existing issues and this is not a duplicate.
- This is a request for the Inspector itself, not for the MCP specification or an SDK.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the parity-gap issue #2430 and the existing TUI/web search inputs referenced here. Determine the appropriate fuzzy-match behavior and shared-core scope, then define acceptance criteria for finding similarly named tools before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100