Skip to main content
Glama
nachogeinfor-ops

code-context

by nachogeinfor-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to code-context

No user-submitted related servers found.

    Related Servers

    • engram-mcp

      lowbridgee
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables semantic and keyword search over Claude Code conversation history stored locally, using hybrid search, local embeddings, and time-decay scoring.
      10 npm
      MIT

    • ContextAtlas

      traviswye
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives Claude Code a curated atlas of your codebase, fusing LSP-grade structure with architectural intent from ADRs, git history, and test associations for single-call context bundles.
      35 npm
      7
      MIT

    • ClaudeHistoryMCP

      jhammant
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that makes Claude Code conversation history searchable and proactively useful by indexing past sessions with hybrid BM25+TF-IDF search, extracting decisions and solutions, and auto-injecting relevant project context at session start.
      9
      3 npm
      66
      MIT

    • mcplens

      vmsfigueredo
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that provides AI coding assistants with semantic search capabilities over codebases. It indexes code using local embeddings and exposes tools for efficient code retrieval, saving tokens and improving response quality.
      31 npm
      4
      MIT

    • mcp-deepcontext

      jmerelnyc
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server enabling symbol-aware semantic search in Claude Code, allowing precise location of functions, types, and implementations via a symbol graph and embeddings.
      9
      MIT
    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

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    All 8 tools have clearly distinct purposes, with no overlap. Each tool's description explicitly states when to use it instead of alternatives, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    Tool names consistently use lowercase with underscores, following a verb_noun pattern (e.g., find_definition, get_file_tree, search_repo). The only exception is 'refresh', which is a verb alone but still fits the action-oriented style.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a code context assistant. Each tool provides essential functionality without redundancy, covering diff analysis, symbol navigation, project structure, git history, and reindexing.

    Completeness5/5

    The tool surface comprehensively covers the code context domain: diff explanation, symbol definition/references, file tree, project summary, recent changes, reindexing, and semantic search. No obvious gaps exist for typical code understanding tasks.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources