rev-eng-cursor-regex-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rev-eng-cursor-regex-mcp search for 'async function' in the codebase"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
rev-eng-cursor-regex-mcp
rev-eng-cursor-regex-mcp is a portable TypeScript Model Context Protocol server for fast literal and regex search over local workspaces. It uses a sparse n-gram index for candidate pruning, then performs deterministic verification against the real file contents.
Features
index.ensure,index.status, andindex.clearfor local index lifecycle managementAutomatic
.gitignorebootstrap for the local.rev-eng-cursor-regex-mcp/cache when that cache lives inside the workspacesearch.literalfor exact-string searchsearch.regexfor ECMAScript regex search with sparse n-gram planningquery.explainfor anchor extraction and fallback analysisdocument.inspect_termsfor trigram, masked-trigram, and sparse-term diagnosticsStatic resources for algorithm notes, storage layout, and agent workflow guidance
Reusable prompts for investigation flow and regex refinement
stdioand Streamable HTTP entrypoints
Related MCP server: File Search MCP
Requirements
Node.js 20 or newer
Quick Start From Source
npm install
npm run build
npm run start:stdioThis starts the MCP server over stdio from a fresh clone with no global install required.
Run Modes
Run over stdio from a local clone:
npm run start:stdioRun over Streamable HTTP from a local clone:
npm run start:httpRun the built CLI directly:
node dist/cli.js stdio
node dist/cli.js http --host 127.0.0.1 --port 3333Run without cloning after the package is published:
npx rev-eng-cursor-regex-mcp stdio
npx rev-eng-cursor-regex-mcp http --host 127.0.0.1 --port 3333Environment
REV_ENG_CURSOR_REGEX_MCP_WORKSPACE_ROOT: default workspace rootREV_ENG_CURSOR_REGEX_MCP_INDEX_DIR: parent directory where.rev-eng-cursor-regex-mcp/is createdREV_ENG_CURSOR_REGEX_MCP_BOOTSTRAP_GITIGNORE: when set tofalse,0,off, orno, skip automatic.gitignorebootstrappingREV_ENG_CURSOR_REGEX_MCP_HTTP_HOST: default HTTP bind hostREV_ENG_CURSOR_REGEX_MCP_HTTP_PORT: default HTTP bind port
Verify A Fresh Clone
npm install
npm run typecheck
npm test
npm run buildClaude Desktop Example
{
"mcpServers": {
"rev-eng-cursor-regex-mcp": {
"command": "node",
"args": [
"/absolute/path/to/rev-eng-cursor-regex-mcp/dist/cli.js",
"stdio"
]
}
}
}Notes
Git workspaces use a commit-keyed base index plus a mutable overlay for working-tree changes.
index.ensureadds the cache directory to.gitignoreautomatically when the cache root lives inside the workspace. PassbootstrapGitignore: falseor setREV_ENG_CURSOR_REGEX_MCP_BOOTSTRAP_GITIGNORE=falseto opt out.Non-git workspaces fall back to snapshot mode with
.gitignore-style filtering.Ignore-case regex searches fall back to a deterministic full scan because the sparse index is case-sensitive.
Available Tools
8 toolsdocument.inspect_termsInspect TermsARead-only
Show the trigrams or sparse n-grams that would be emitted for a file or text snippet, including offsets and rarity weights.
Inputs: mode (required), path, text, maxTerms. Returns: mode, notes, terms, termCount
index.clearClear IndexADestructive
Delete cached index data for a workspace. Use this only to recover from stale or corrupt local index state.
Inputs: scope (required), workspaceRoot. Returns: elapsedMs, storageDir, clearedScope, removedPaths
index.ensureEnsure IndexAIdempotent
Build or refresh the local regex index for a workspace and return the active base revision plus overlay state.
Inputs: excludeGlobs, forceRebuild, includeGlobs, workspaceRoot, +2 more. Returns: elapsedMs, sourceMode, storageDir, baseIndexId, +8 more
index.statusIndex StatusARead-only
Describe the active regex index for a workspace, including corpus selection, freshness, and storage paths, without rebuilding it.
Inputs: workspaceRoot. Returns: ready, byteSize, fileCount, sourceMode, +5 more
query.explainExplain Query PlanARead-only
Explain how the server will decompose a query, what anchors it can extract, and whether the search will fall back to a full scan.
Inputs: pattern (required), flags. Returns: valid, plannerMode, branchAnchors, fallbackReason, +8 more
search.literalSearch LiteralARead-only
Find exact text in indexed workspace files. Prefer this over regex when you already know the exact string.
Inputs: needle (required), pathGlobs, afterLines, maxResults, +4 more. Returns: plan, matches, elapsedMs, queryKind, +8 more
search.planPlan Search WorkflowARead-only
Plan the MCP-first search workflow for an exploratory objective and recommend whether to ensure the index, use literal search, explain a regex, or run regex search.
Inputs: objective (required), pathHints, workspaceRoot, knownExactString, +1 more. Returns: reasoning, fallbackPlan, mustEnsureIndex, suggestedRegexArgs, +4 more
search.regexSearch RegexARead-only
Find ECMAScript regular-expression matches in indexed workspace files using sparse n-gram pruning before deterministic verification.
Inputs: pattern (required), flags, pathGlobs, afterLines, +5 more. Returns: plan, matches, elapsedMs, queryKind, +8 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: index management (ensure, status, clear), search (literal, regex, plan), query explanation (explain), and document inspection (inspect_terms). No functional overlap.
All tools follow a consistent 'category.action' dot notation (e.g., index.ensure, search.literal), making naming predictable and easy to understand.
8 tools is well within the ideal 3-15 range. The count is sufficient to cover the domain without being excessive.
The tool set covers index lifecycle, two search modes, planning, explanation, and n-gram inspection. A potential gap is the lack of a tool to list indexed files explicitly, but index.status provides similar info. Otherwise, it's well-rounded.
Related MCP Connectors
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Ask a codebase what calls what: search, blast radius, paths between symbols, and diffs.
Securely search and manage workspace context files for AI agents and teams.
Search indexed code, trace dependencies, assess change impact, and recall repository memory.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables searching text across configured local workspaces using ripgrep. Provides secure text search capabilities within defined workspace boundaries through both MCP server and CLI interfaces.MIT
- AlicenseAqualityDmaintenanceEnables blazingly fast file and content searching in large codebases using ripgrep, with intelligent filtering, fuzzy finding, and directory tree visualization while respecting .gitignore and avoiding common bloat directories.424 npm2MIT

Cometix Indexerofficial
AlicenseNot gradedqualityDmaintenanceA local indexing and retrieval service that enables semantic code search by wrapping Cursor's backend RepositoryService. It provides tools for indexing local workspaces and performing incremental semantic searches with automatic synchronization.67MIT- AlicenseAqualityCmaintenanceExtremely fast local hybrid code search for agents.152MIT