Code Memory

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/kapillamba4-code-memory

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

6 read · 0 write · 0 delete · 1 not yet classified

Secrets

None asked for

Install scripts

Not scanned yet

Runs as

Python package

Tools (7)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• check_index_status

  USE THIS TOOL to check if the codebase has been indexed and whether search tools will return results. Call this BEFORE search_code or search_docs if you're unsure about indexing state. TRIGGER - Call this tool when: - You're unsure if the codebase has been indexed - search_code or search_docs returned empty results - Starting work on a new project or session - You want to verify index health before searching This tool checks the SQLite database for indexed symbols and documentation chunks. It's a lightweight diagnostic - much faster than re-indexing. INTERPRETING RESULTS: - If "indexed" is …

• find_dead_code

  USE THIS TOOL to find functions, methods, and classes that look like dead code (defined but never called). PREREQUISITE: This tool requires indexing. If results are empty or you haven't indexed this session, call index_codebase(directory) first. HOW IT WORKS: Cross-references the indexed symbol table against the indexed reference table. Any symbol with no reference outside its own definition body is flagged as a candidate. Each candidate is scored with a confidence in [0.0, 0.99] and a list of human-readable reasons explaining the verdict. TRIGGER - Call this tool when the user asks: - "Fin…

• get_index_stats

  USE THIS TOOL to get comprehensive statistics about the code index. This tool provides detailed metrics about the index health, including file counts, symbol distributions, embedding model info, and database size. TRIGGER - Call this tool when: - You want to understand what's in the index - Debugging search quality issues - Checking index freshness or coverage - Monitoring database size and health Do NOT use this tool for: - Checking if indexing is needed (use check_index_status) - Searching for code (use search_code) Args: directory: Path to the project directory. Returns: Dictio…

• index_codebase

  YOU MUST CALL THIS TOOL FIRST before using search_code or search_docs. Use this tool to build the searchable index that powers all other code intelligence features. TRIGGER: Call this tool immediately when: - Starting a new session with this codebase - search_code or search_docs returns empty or unexpected results - You haven't indexed recently or files have been modified - User asks about code structure, definitions, or documentation This tool performs TWO critical operations: 1. CODE INDEXING: Uses tree-sitter for language-agnostic AST extraction (Python, JavaScript/TypeScript, Java, Kotli…

• search_code

  USE THIS INSTEAD OF grep/glob/find for ANY code search. This tool provides SEMANTIC code understanding - it finds related concepts, not just text matches. STOP: Before using grep, rg, find, or glob, use this tool instead. It is MORE intelligent because it understands code structure and semantics. PREREQUISITE: This tool requires indexing. If results are empty or you haven't indexed this session, call index_codebase(directory) first. This tool uses HYBRID RETRIEVAL (BM25 keyword search + dense vector semantic search with Reciprocal Rank Fusion) - far more intelligent than grep or filename pa…

• search_docs

  USE THIS TOOL for conceptual understanding and "how does X work?" questions. Search markdown documentation, READMEs, and code docstrings using semantic search. PREREQUISITE: This tool requires indexing. If results are empty or you haven't indexed this session, call index_codebase(directory) first. TRIGGER - Call this tool when the user asks: - "How does [feature] work?" - "Explain the architecture of..." - "What are the setup/installation instructions?" - "Show me the documentation for..." - "Why was this designed this way?" - Any question answered by README, CHANGELOG, or docstrings IMPORT…

• search_history

  USE THIS TOOL for Git history queries: understanding WHY changes were made, debugging regressions, or finding commit context. This tool operates on the local Git repository. TRIGGER - Call this tool when the user asks: - "Why was this code changed?" / "Who changed this?" - "When was X introduced?" / "Find commits about X" - "Debug this regression" / "What broke this?" - "Show me the history of this file" - "Who wrote this line?" (blame) - "What changed in commit X?" This tool does NOT require indexing - it queries Git directly. WHEN TO USE EACH search_type: 1. "commits" - USE WHEN: - Us…

Signals

Stars

49

Forks

11

Open issues

3

Contributors

3

Weekly downloads

79

Last commit

May 20, 2026 (5 months ago)

Last release

May 20, 2026 (5 months ago)

Last package publish

May 20, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.kapillamba4/code-memory

Version

1.0.33

Auth

No auth

Packages

pypi code-memory

License

MIT

Repository

github.com/kapillamba4/code-memory

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql