rev-eng-cursor-regex-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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index.ensureA | Build or refresh the local regex index for a workspace and return the active base revision plus overlay state. |
| index.statusA | Describe the active regex index for a workspace, including corpus selection, freshness, and storage paths, without rebuilding it. |
| index.clearA | Delete cached index data for a workspace. Use this only to recover from stale or corrupt local index state. |
| search.literalA | Find exact text in indexed workspace files. Prefer this over regex when you already know the exact string. |
| search.regexA | Find ECMAScript regular-expression matches in indexed workspace files using sparse n-gram pruning before deterministic verification. |
| search.planA | 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. |
| query.explainA | Explain how the server will decompose a query, what anchors it can extract, and whether the search will fall back to a full scan. |
| document.inspect_termsA | Show the trigrams or sparse n-grams that would be emitted for a file or text snippet, including offsets and rarity weights. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate-with-rev-eng-cursor-regex-mcp | Guide an agent through ensure, explain, search, and narrowing steps. |
| refine-regex-pattern | Rewrite a broad regex into one that keeps stronger literal anchors for sparse planning. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs-algorithms | Blog-to-server mapping for classic trigrams, masked trigrams, suffix arrays, and sparse n-grams. |
| docs-storage-layout | Exact on-disk layout for manifests, lookup tables, postings, and overlays. |
| docs-decision-tree | Canonical MCP-first search policy for exact-string, regex, fallback, and shell escape-hatch decisions. |
| docs-usage-playbook | Recommended agent workflow and failure-handling guidance for the rev-eng-cursor-regex-mcp server. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/blas0/rev-eng-cursor-regex-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server