ripgrep-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Search files for patterns using ripgrep (rg) |
| advanced-searchC | Advanced search with ripgrep with more options |
| count-matchesB | Count matches in files using ripgrep |
| list-filesA | List files that would be searched by ripgrep without actually searching them |
| list-file-typesA | List all supported file types in ripgrep |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: basic search, advanced search, counting matches, listing files, and listing file types. No overlap in functionality.
Most tools follow a verb_noun pattern with hyphens (count-matches, list-files, list-file-types). 'search' is a single verb and 'advanced-search' is adjective_noun, but the pattern is still clear and predictable.
With 5 tools, the server covers core ripgrep features without being too narrow or bloated. The count is well-suited for the domain.
The tool set covers search, counting, file listing, and file type listing. A minor gap might be the lack of a tool for grep-like context lines, but core workflows are well-supported.