File Find Mcp

Created By
joisuna year ago
Overview

what is File Find MCP?

File Find MCP is a specialized Model Context Protocol (MCP) server designed for fast file searching within a filesystem, utilizing Rust and powered by ripgrep for high-performance searches.

how to use File Find MCP?

To use File Find MCP, clone the repository from GitHub, build the project using Cargo, and configure it in your MCP-compatible tools by adding the server command to your settings.

key features of File Find MCP?

  • High-performance search using ripgrep
  • File content reader for displaying text file contents
  • Smart file detection that skips binary files
  • MCP integration for compatibility with AI assistants
  • Fallback mechanism using pure Rust implementation if ripgrep is unavailable

use cases of File Find MCP?

  1. Quickly searching for keywords in large codebases
  2. Reading and displaying contents of specific text files
  3. Integrating with AI systems that support the Model Context Protocol for enhanced file search capabilities

FAQ from File Find MCP?

  • What is ripgrep?

Ripgrep is a command-line search tool that recursively searches your current directory for a regex pattern.

  • Do I need to install ripgrep?

Yes, ripgrep must be installed for optimal performance, but a pure Rust implementation is available as a fallback.

  • Is File Find MCP open source?

Yes, File Find MCP is open source and available on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
joisun
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago