Pare Search
Let agents search the codebase with ripgrep and fd and get consistent typed JSON hits instead of guessing from unstructured grep output.
Overview
io.github.Dave-London/pare-search is an MCP server for the Build phase that returns typed JSON from ripgrep and fd code search operations.
What is this MCP server?
- Exposes ripgrep and fd operations through MCP with typed JSON result shapes
- stdio npm package @paretools/search (v0.8.1) for local agent hosts
- Reduces missed matches when agents parse long ripgrep buffers incorrectly
- Fits refactor and bug-hunt workflows that need path, line, and match metadata
- From the Pare repo family alongside python and test servers for uniform JSON
- Server version 0.8.1
- Two search backends: ripgrep and fd
- npm identifier @paretools/search, stdio transport
Community signal: 128 GitHub stars.
What problem does it solve?
Unstructured ripgrep output overflows context and causes agents to skip relevant files or misread match boundaries.
Who is it for?
Indie builders whose agents need fast repo-wide text and file search with machine-readable results during implementation.
Skip if: Builders who want semantic code graphs, IDE-only search, or cloud-hosted code indexing without local rg/fd.
What do I get? / Deliverables
Registering @paretools/search gives your agent filterable, typed search hits for safer refactors and faster file targeting.
- Typed JSON search results from ripgrep and fd MCP tools
- More reliable agent-driven codebase navigation in local repos
Recommended MCP Servers
Journey fit
Code navigation and symbol discovery happen continuously while building features, refactors, and integrations. Agent-tooling is the right shelf because the value is structuring search for MCP clients during implementation, not publishing or ops monitoring.
How it compares
Structured ripgrep/fd MCP bridge, not a managed codebase search SaaS or documentation crawler.
Common Questions / FAQ
Who is io.github.Dave-London/pare-search for?
It is for developers using MCP agents who want ripgrep and fd results in JSON while exploring or editing a local repository.
When should I use io.github.Dave-London/pare-search?
Use it whenever the agent must find symbols, strings, or files across the project during build or debug sessions instead of raw shell grep.
How do I add io.github.Dave-London/pare-search to my agent?
Install @paretools/search from npm, configure it as a stdio MCP server in your client settings, and install ripgrep and fd on your machine so the tools are callable.