Search Code MCP
Related Servers
Alternatives to Search Code MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables structural code search and refactoring across 20+ programming languages using ast-grep patterns, with safe dry-run mode and flexible filtering.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover open-source libraries worth reusing through multi-signal repository ranking and to search real code with sub-50ms local regex/semantic queries federated to live GitHub, grep.app, and package-registry backends. It exposes seven tools over stdio—repo search, code search, repo profile/tree, file and docs fetching, and a usage guide—with structured filters, typed pre-execution errors, and a byte-identical CLI twin.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to understand and navigate codebases through structural analysis. Provides code mapping, symbol search, and impact analysis using ast-grep for accurate parsing of Python, JavaScript, TypeScript, and Go projects.452MIT
- FlicenseDqualityDmaintenanceEnables AI agents to perform semantic search over codebases by converting natural language queries into efficient search patterns like grep and ripgrep. It utilizes LLMs to verify relevance and find code snippets that traditional keyword-based searches might miss.1-
- AlicenseAqualityCmaintenanceProvides AI assistants with progressive code intelligence to explore repository structure, find symbols, and assess the impact of changes using ast-grep.3MIT
- AlicenseAqualityDmaintenanceProvides LLM-optimized filesystem access with intelligent file pagination for large files, lightning-fast ripgrep-powered code search with regex support, and security sandboxing to safely explore and search codebases.73 npm1MIT
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.