Search Code 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | High-performance unified code search engine combining ripgrep (regex/text) and ast-grep (AST patterns and YAML rules). Supports pagination with searchId and offset/limit for large results. |
| replaceA | Structural code refactoring and replacement engine. Supports AST rewrite or Regex/Text replacement. By default, runs in dryRun mode producing a unified diff preview to ensure safe operations before writing changes to disk. |
| countA | Count matching lines or total occurrences of a pattern in files without retrieving match content, saving tokens. |
| dump_treeA | Inspect the concrete syntax tree (CST) or AST of code to discover exact node kinds and structure for crafting ast-grep patterns. |
| find_symbolsA | Find code symbols (functions, classes, interfaces, methods, types, variables, structs, enums) across the codebase. Automatically selects best available engine: Universal Ctags -> ast-grep -> ripgrep regex heuristic. |
| list_filesB | Quickly list files matching glob patterns or file types without scanning contents. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a fairly distinct purpose: search finds matches, replace rewrites, count tallies, find_symbols targets declarations, dump_tree inspects AST, list_files enumerates files. There is minor overlap between search, count, and find_symbols since all match patterns, but the descriptions make the boundaries clear enough to choose correctly.
Naming is mostly a verb or verb_noun pattern (dump_tree, find_symbols, list_files) with a few bare single-verb names (search, replace, count). All snake_case and readable, with only minor deviation from a strict verb_noun convention.
Six tools is well-scoped for a code search/refactor server, with each tool earning its place (search, replace, count, inspect, symbols, listing). No redundancy or bloat.
The surface covers discovery (list_files, dump_tree, find_symbols), search (search, count), and mutation (replace with dry-run), forming a coherent lifecycle. Minor gaps like reading file contents or explicit symbol-level navigation exist but core workflows are covered.