code-context-mcp
Related Servers
Alternatives to code-context-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to query a local, read-only SQLite code index for status, file outlines, symbol search, references, dependencies, and bounded symbol source without loading the whole repository into context. It currently supports TypeScript and JavaScript through the TypeScript compiler API.MIT
- AlicenseBqualityCmaintenanceIndexes a Python/JS/TS repository into a local SQLite knowledge graph so agents can trace callers, callees, imports, subclasses and covering tests, measure impact radius, rank diff risk, and summarize architecture without grepping files. Exposes these queries as MCP tools alongside an equivalent CLI, with no daemon, embeddings, or network access.10MIT
- AlicenseBqualityDmaintenanceAn MCP server that indexes source code into a local database and provides tools for querying code symbols, dependencies, and tree structure for JavaScript/TypeScript, Java, and Python.7MIT
- FlicenseNot gradedqualityDmaintenanceProvides code intelligence by indexing source code into SQLite and offering MCP tools for symbol search, flow tracing, and context retrieval to assist with code navigation and understanding.-
- AlicenseAqualityCmaintenanceIndexes a mono-repo into a knowledge graph and provides MCP tools to query code structure—packages, components, routes, HTTP calls—without file reads or grep round-trips.722 npmMIT
- FlicenseAqualityBmaintenanceMCP server that indexes TypeScript/React project symbols in memory, enabling agents to find definitions, references, and dependencies without reading the whole repo. Also includes a local visual dashboard with no outbound network calls.10-
TDQS
Scored across 6 tools
Each tool targets a distinct query shape: symbol definition (find_symbol), file-level context (get_file_context), importers (who_imports), directory exports (exports_in), path/summary search (search_files), and a raw SQL escape hatch. Minor overlap exists because get_file_context already reports importers for one file while who_imports generalizes to symbols, and query can replicate any other tool's answer. Descriptions make the boundaries clear enough that misselection is unlikely.
Names mix styles: verb_noun (find_symbol, get_file_context, search_files), a question-phrase (who_imports), a prepositional form (exports_in), and a bare generic noun (query). Each name is individually readable and reflects its description, but there is no single predictable convention an agent can rely on.
Six tools is a well-scoped set for a code-index server, with no filler entries. Each tool covers a distinct navigation need and the SQL tool absorbs exotic queries instead of spawning extra bespoke tools.
Coverage of the core index domain (locate definitions, describe files, trace imports, list directory exports, search paths, raw SQL) is solid, and query fills most gaps. What's missing is reverse usage lookup beyond imports (call sites/references per symbol) and any way to read actual file contents, though the SQL surface partially compensates.