Skip to main content
Glama
lfnovo

Code Expert MCP Server

by lfnovo

Related Servers

Alternatives to Code Expert MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Intelligently analyzes codebases to enhance LLM prompts with relevant context, featuring adaptive context management and task detection to produce higher quality AI responses.
      2
      -
    • A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      6
      10 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides 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.
      74 PyPI
      41
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding assistants with deep, semantic understanding of local codebases via AST-aware chunking, cross-repo symbol graphs, and architectural memory, enabling context-aware code search and dependency tracing.
      11
      MIT

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues