codetex-mcp
Related Servers
Alternatives to codetex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with deterministic, offline repository intelligence including AST symbol indexing, import/dependency graphs, and bounded context summaries via the Model Context Protocol.MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with structured, deterministic repository intelligence—file tree, dependencies, hotspots, and git history—via Model Context Protocol, enabling them to understand codebases without reconstructing architecture from scratch.367 npm1MIT
- AlicenseNot gradedqualityBmaintenanceTurns a codebase into a queryable graph with semantic search, call graphs, and control/data flow analysis, served to AI coding agents via the Model Context Protocol.206 npmMIT
- FlicenseNot gradedqualityBmaintenanceTransforms local Git repositories into queryable, context-rich knowledge bases via AST-aware chunking and Git metadata, enabling AI assistants to search and understand codebases with semantic precision.-
- AlicenseAqualityBmaintenanceA semantic code context server that connects your local repository to AI assistants via the Model Context Protocol, enabling dynamic codebase exploration without copy-pasting.590 npm3MIT
- AlicenseBqualityDmaintenanceProvides IDE-like semantic code retrieval and editing tools for LLMs, enabling precise code understanding and manipulation in large codebases via the Model Context Protocol.25MIT
TDQS
Scored across 7 tools
Each tool targets a distinct concern: repo-level overview, file context, symbol detail, semantic search, status, syncing, and repo listing. There is no meaningful overlap or ambiguity between tool boundaries.
Tool names consistently follow a snake_case verb_noun pattern, mostly using get_ for retrieval actions. Minor variation like search_context and sync_repo still fit the same predictable style.
Seven tools is well-scoped for a code context and indexing server. Each tool earns its place by covering a distinct retrieval or maintenance operation without unnecessary bloat.
The set covers repository overview, file context, symbol detail, semantic search, status, sync, and listing—covering the core workflows well. The main gap is the lack of explicit repo registration or full-sync tools, though these may be handled externally.