Search Tools MCP Server
Related Servers
Alternatives to Search Tools MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables semantic code search across multiple repositories using natural language queries. Provides intelligent code discovery, symbol lookups, and cross-repo dependency analysis for AI coding agents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables code intelligence through semantic, structural, graph, and text search across indexed repositories, allowing AI agents to quickly locate the exact code they need.5 npm3MIT
- AlicenseAqualityDmaintenanceEnables fast code analysis and navigation through hybrid semantic search, graph-based relationship tracking, and structure exploration across multiple programming languages with optimized indexing for large codebases.83MIT
- AlicenseAqualityDmaintenanceProvides code repository indexing and semantic search capabilities, allowing natural language queries to find relevant code snippets with automatic incremental indexing and multi-language support.14 npm359ISC
- AlicenseNot gradedqualityDmaintenanceEnables semantic code search across multiple repositories using AST-aware chunking and relationship tracking. Supports local LLM embeddings, real-time indexing, and cross-codebase dependency analysis through vector and graph databases.3MIT
- AlicenseNot gradedqualityCmaintenanceProvides semantic code search and code insights via a knowledge graph, enabling AI to understand, navigate, and modify complex projects with deep dependency and architecture analysis.MIT
TDQS
Scored across 21 tools
Each tool targets a specific analysis task, but several overlap (e.g., smart_code_search vs contextual_keyword_search; find_code_hotspots vs coderank_analysis) requiring careful reading of descriptions. The distinct focus areas keep them mostly separable.
Tool names mix various verb prefixes (get_, find_, trace_, analyze_, discover_, map_, identify_) and some names are noun-led (coderank_analysis, contributor_impact_analysis). No consistent pattern emerges, making the surface harder to predict.
21 tools is in the borderline heavy range per the rubric. Each tool covers a distinct analysis scenario, so it is not excessive, but the number is still large and could overwhelm an agent choosing which tool to invoke.
The set covers a wide array of code analysis needs—search, symbols, dependencies, data flow, error handling, performance, testing—and includes several composite tools. Minor gaps like dead code detection don't significantly detract from the overall surface.