count-matches answers "how common is this" without returning a single hit, list-files answers "what would this even search" before you pay for the scan, and maxResults bounds whatever is left. advanced-search carries the flags that usually decide the outcome — fixedStrings when the pattern is literal text that looks like a regex, invertMatch when the interesting files are the ones without the match, includeHidden when the answer is in something ripgrep skips by default.
A ripgrep wrapper in five tools: a plain pattern search, an advanced search that exposes ripgrep's flags as parameters, a count-only mode, a dry run that lists the files a search would cover, and ripgrep's own type list.
- Pattern search with case sensitivity, a file glob, surrounding context lines and a result cap
- The flags that decide whether a search is useful, as parameters: fileType, fixedStrings, invertMatch, includeHidden, followSymlinks, showFilenamesOnly
- Counts instead of matches, per file or per matching line
- The set of files a search would cover, listed without running the search
- The file types ripgrep knows, so fileType is passed a name it recognises
Ripgrep (rg) available on the machine, and Node on your PATH.
One command — npx -y mcp-ripgrep@latest