Code Expert MCP Server
Related Servers
Alternatives to Code Expert MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceIntelligently analyzes codebases to enhance LLM prompts with relevant context, featuring adaptive context management and task detection to produce higher quality AI responses.2MIT
- AlicenseAqualityDmaintenanceProvides intelligent code context and analysis through semantic compression, AST parsing, and multi-language support. Offers 60-80% token reduction while enabling AI assistants to understand codebases through local analysis, OpenAI-enhanced insights, and GitHub repository integration.617 npm3MIT
- AlicenseNot gradedqualityDmaintenanceProvides 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
- AlicenseNot gradedqualityCmaintenanceProvides structured, token-efficient code context for AI assistants by indexing codebases with AST-level analysis, supporting 17+ languages, enabling semantic search, call-site tracking, and PR attribution.77 PyPI41MIT
- AlicenseAqualityBmaintenanceSelf-hosted semantic code search for AI coding agents. Indexes many repositories at once with tree-sitter AST chunking, local llama.cpp embeddings and Qdrant, so Claude Code, Cursor, Codex and any MCP client can find code by meaning, trace usages and callers, and read the git history behind each chunk. No API keys, and your code never leaves your machine.21834MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve compact structural codebase context through repository architecture summaries, AST symbol extraction, cyclomatic complexity scoring, and TODO/FIXME hotspot search.1MIT
TDQS
Scored across 14 tools
Tools are mostly distinct, but there is some overlap between list_repos, get_repo_status, and list_repository_branches for repository status and branch information. Additionally, get_repo_file_content and get_repo_structure both provide directory listings, though they serve different purposes. Descriptions help clarify when to use each.
The majority of tools follow a verb_noun pattern (list_, get_, delete_, clone_, start_, stop_). Minor deviations include 'list_repos' using an abbreviation and 'get_source_repo_map' breaking the 'get_repo_*' pattern. Overall, naming is predictable and consistent.
14 tools is an appropriate number for a server focused on repository lifecycle management and code analysis. Each tool serves a clear purpose without unnecessary bloat, and the count fits within the well-scoped range.
The server provides complete CRUD for cached repositories (clone, refresh, delete, get status) and a comprehensive set of analysis tools (structure, critical files, source map, documentation, file content). The domain is fully covered with no obvious dead ends.