Summary
"Where did I put that file", answered with metadata.
Returning size and creation date alongside the path is what makes this more than a find wrapper: when three files share a name, those two fields usually decide which one you meant. Pass a directory to keep the search inside the tree you care about — left out, it starts at the root and walks everything.
What it is
A Python MCP server that searches the filesystem for files whose path contains a fragment you give, and returns them with their metadata.
What you get
- `search-files` — a required `query` path fragment, and an optional `directory` to search under
- Each match comes back with file name, full path, file size and creation date
- With no directory given, the search runs from the root
- A list rather than a single hit, so ambiguous names still get answered
Requirements
Uv. The client launches it with `uv --directory <path-to-checkout> run file-finder-mcp` over stdio.