fw-context-mcp
Related Servers
Alternatives to fw-context-mcp
- AlicenseAqualityAmaintenanceKnot is a semantic and structural codebase indexer designed for AI coding agents and developers navigating large projects. It combines vector search and graph traversal to find code by meaning, analyze impact via reverse dependencies, and explore file architectures.78MIT
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to query a fully local SQLite FTS5 memory index of a codebase, returning high-density identity cards with exact line references, AST symbol contracts, phase maps, and colloquial intent search so agents can work without scanning raw files. It also supports incrementally syncing code changes and enriching knowledge under a six-pillar quality gate, keeping everything on-device with no cloud leakage.5MIT
- FlicenseNot gradedqualityBmaintenanceProvides graph-native code intelligence for coding agents, enabling them to navigate repositories through compact SQLite-backed symbol graphs and retrieve full source only for relevant symbols.-
- AlicenseNot gradedqualityCmaintenanceProvides intelligent code indexing with 15 MCP tools for symbol extraction, hybrid search (FTS5+vector), call graphs, and incremental indexing of local folders and remote repos, enabling token-efficient code retrieval for AI agents.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to efficiently understand and navigate a codebase by providing semantic search over symbols and a reference graph, replacing expensive grep/glob calls with structured tools like definition lookup, caller/callee queries, and change-impact analysis.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a local SQLite-backed structural code graph for bounded, relevant context such as source entities, relationships, call paths, impact analysis, and recorded project mistakes before reading full files.35 npmMIT

Semantic Code Search MCPofficial
AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with structured access to indexed codebases via semantic search, symbol analysis, and file reading tools.13Server Side Public , v 1
TDQS
Scored across 37 tools
Many tools share broad purposes—six search tools and a large family of call-graph/reference tools—so an agent can confuse semantic_search with smart_search or search_code, and get_source with get_symbol_context. The extensive descriptions and explicit cross-references help, but overlap remains substantial, especially in search.
All names are snake_case, mostly following a verb_noun pattern (get_, find_, search_, check_, list_, reset_). Minor deviations are adjective_noun forms such as semantic_search and smart_search, but the set is highly predictable overall.
37 tools is far beyond the 3-15 sweet spot and exceeds the 25-tool threshold that indicates overload. Many are narrow variants of search, reference, and call-graph queries, making the set difficult to navigate at a glance.
The query surface is very comprehensive—symbol search, call graph, references, vector table, dead code, class hierarchy, variables—but lifecycle coverage has notable gaps. There is no tool to initialize a project or trigger a full index/build; only reset_index and single-file reindex_file exist, forcing agents to fall back to CLI instructions for central setup operations.