Skip to main content
Glama
AB498

Code Context Provider MCP

by AB498
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Code Context Provider MCP

No user-submitted related servers found.

    Related Servers

    • mcp-codebase-intelligence

      g-tiwari
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.
      9 npm
      1
      MIT

    • syntax-map-mcp

      kht6163
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables code analysis of JavaScript, TypeScript, TSX, Python, and Rust files using Tree-sitter, providing symbol listing, definition/reference lookup, AST queries, LSP-style features, and SQLite indexing for efficient cross-file searches.
      2 npm
      MIT

    • smart-explore

      VasyaYovbak
      F
      license
      A
      quality
      C
      maintenance
      Enables token-efficient structural code exploration using tree-sitter AST parsing, with tools for symbol search, outlines, source unfolding, call graphs, and related-file discovery.
      1
      -

    • XRAY MCP

      srijanshukla18
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to understand and navigate codebases through structural analysis. Provides code mapping, symbol search, and impact analysis using ast-grep for accurate parsing of Python, JavaScript, TypeScript, and Go projects.
      4
      52
      MIT

    • codelens-mcp

      segentic-lab
      A
      license
      A
      quality
      F
      maintenance
      A deterministic structural code map server for AI agents, giving them the shape of a codebase (imports, exports, classes, functions, signatures, comments, TODO-markers) without reading whole files into context. Powered by tree-sitter WASM grammars, it runs anywhere Node 18+ works.
      7
      2 npm
      1
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose focused on providing project context.

    Naming Consistency5/5

    The naming follows a consistent verb_noun pattern (get_code_context), and with only one tool, there is no inconsistency to evaluate. The naming is clear and descriptive.

    Tool Count2/5

    A single tool is generally too few for most MCP server purposes, as it limits functionality and can feel thin. For a 'Code Context Provider', one tool may not cover all potential needs like updating or filtering context, making it borderline inadequate.

    Completeness2/5

    The tool set is severely incomplete for the implied domain of code context provision. While it offers a comprehensive overview, there are obvious gaps such as tools for updating context, filtering by file type, or handling specific symbols, which could lead to agent workarounds or failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources