Skip to main content
Glama
kapillamba4

Code Memory

by kapillamba4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Code Memory

No user-submitted related servers found.

    Related Servers

    • vibe-hnindex

      AndyAnh174
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server to index your codebase once and search it across AI sessions with keyword, semantic, or hybrid search, keeping all data on disk.
      90 npm
      4
      MIT

    • codesteer-atlas

      LuisCarlosLopes
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server for semantic code search using Tree-sitter AST parsing, local embeddings, and hybrid search; enables indexing and querying codebases entirely offline.
      5
      MIT

    • mcp-local-rag

      damoqiongqiu
      A
      license
      A
      quality
      A
      maintenance
      A fully local RAG MCP server for semantic code search and code intelligence, using AST-level chunking and hybrid search to pinpoint functions, classes, and APIs. No cloud, no API keys, zero setup.
      16
      61 npm
      13
      MIT

    • Tea Rags MCP

      artk0de
      A
      license
      Not graded
      quality
      A
      maintenance
      A high-performance MCP server for semantic search and codebase indexing using the Qdrant vector database. It features optimized embedding pipelines, AST-aware chunking, and git metadata enrichment for fast, privacy-focused local or remote search.
      382 npm
      22
      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.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct, well-defined purpose: checking index status, finding dead code, getting stats, indexing, searching code, searching docs, and searching history. No overlaps or ambiguous boundaries.

    Naming Consistency5/5

    All tool names use a consistent snake_case pattern with descriptive verbs (check, find, get, index, search) followed by the target domain (index_status, dead_code, index_stats, codebase, code, docs, history). Minor variations in length do not hinder predictability.

    Tool Count5/5

    With 7 tools, the set is well-scoped for a code intelligence server. Each tool provides essential functionality (indexing, search, dead code analysis, stats, history) without redundancy or bloat.

    Completeness5/5

    The tool surface covers the full lifecycle: indexing (index_codebase), status checks (check_index_status, get_index_stats), code and documentation search (search_code, search_docs), dead code detection (find_dead_code), and git history (search_history). There are no obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources