file-finder-mcp
# file-finder-mcp MCP Server
A MCP server for searching files in the filesystem based on a path fragment.
## Components
### Resources
The server implements a file search system:
- Each file resource includes:
- File name
- Full path
- File size
- Creation date
### Tools
The server provides one tool:
- `search-files`: Searches for files matching a given path fragment.
- Takes `query` as a required string argument.
- Takes `directory` as an optional string argument to specify the base directory for the search. If not provided, the search runs in the root directory.
- Returns a list of matching files with their metadata.
## Quickstart
### Install
Replace the contents of the `cline_mcp_settings.json` file with the following configuration:
```json
{
"mcpServers": {
"file-finder-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/stleubaev/Desktop/ClineTest/file-finder-mcp",
"run",
"file-finder-mcp"
]
}
}
}
```
## Testing
The testing was conducted using the Gemini model with the following prompt:
```
hi can you find files called file_to_find on my desktop using my mcp server
```
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search-files' has a clear and distinct purpose, so agents cannot misselect between non-existent alternatives.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'search-files' follows a verb_noun pattern, but consistency cannot be assessed across a set of one.
A single tool is too few for most server purposes, as it severely limits functionality and scope. For a 'file-finder' server, one might expect additional tools like list directories, filter by type, or get file metadata, making this feel incomplete and thin.
The server's domain appears to be file searching, but with only a search tool, there are significant gaps. For example, no tools exist to navigate directories, retrieve file details, or handle errors, which could lead to agent failures in broader file-related tasks.