Reposearch

Created By
happyZYMa year ago
A mcp server to provide better content search than Cline's builtin `search_files` tools. Features: - [x] control the filter by `.reposearchignore` file, and use gitignore format. - [x] support regex for searching - output format control: - [x] whether include content in result - [ ] include surrounding lines - [x] tokens boom prevention Notes: - Currently you need to tell Cline to stop using `search_files` in the system prompt.
Overview

what is Reposearch?

Reposearch is an MCP server designed to provide enhanced content search capabilities compared to Cline's built-in search_files tools.

how to use Reposearch?

To use Reposearch, you need to set it up by running the server command node path/to/mcp-server-reposearch/index.js and configure it to stop using Cline's search_files in the system prompt.

key features of Reposearch?

  • Control filtering using a .reposearchignore file with gitignore format.
  • Support for regex-based searching.
  • Output format control, including options to include content in results.
  • Prevention of token explosion during searches.

use cases of Reposearch?

  1. Searching for specific content in large codebases.
  2. Filtering search results based on custom ignore patterns.
  3. Utilizing regex to find complex patterns in files.

FAQ from Reposearch?

  • Can Reposearch handle all types of files?

Yes! Reposearch can search through various file types as long as they are supported by the MCP server.

  • Is there a limit to the regex patterns I can use?

No, you can use any valid regex pattern, but be cautious of performance with very complex patterns.

  • How do I control the output format?

You can specify whether to include content in the results and whether to include surrounding lines.

Server Config

{
  "mcpServers": {
    "mcp-server-reposearch": {
      "command": "node",
      "args": [
        "path/to/mcp-server-reposearch/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
happyZYM
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