Skip to content

feat: Add search capability to the ListPane component to allow users to filter resources, prompts and tools #727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

cameronldroberts
Copy link

@cameronldroberts cameronldroberts commented Aug 17, 2025

This PR adds the ability for the user to search their different types of resources they might get back from their MCP server. For example they may want to search on a particular tool name or description and this PR allows them to do that.

Motivation and Context

After using the tool I was finding myself wanting to search for particular tools and I wasn't able to do that. When the MCP server exposes a number of tools it isn't able to render them all on screen so it required me to scroll through them to find the one I was looking for.

This was mainly because I wanted to quickly navigate the tools but as the ListPane tile is used for the other types as well I figured it would be a good place to add the search so it can be used for those types as well.

How Has This Been Tested?

I have tested this by spinning up a dummy MCP server using fastMCP and connecting my MCP inspector to it. This all worked fine and I was able to filter down the results I got back based on my search string. I've attached a screen recording so that you can see this in action. As well as the manual testing I added some UT to cover the new functionality, this component did not have it's own test suite so I've added that with some basic rendering tests as well.

inspector-search-sr.mov

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

This could be extended to add additional filtering options and/or the ability to control the ordering that the results get displayed. I'm not sure how much additional value that would add so I've not added it as part of this PR but happy to re-visit if people think it's worth doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant