An MCP server for maintaining code knowledge across LLM chat sessions
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-sparshdrolia-persistent-code","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Persistent-Code MCP Server with LlamaIndex A Model Context Protocol (MCP) server that creates and maintains a semantic knowledge graph of code generated by Claude. Powered by LlamaIndex, this allows maintaining context across sessions with advanced semantic search capabilities without requiring the entire codebase to be present in the context window. ## Problem & Solution When developing software with Claude: - Context windows are limited, making it difficult to work with large codebases - Previous code context is lost between sessions - Claude lacks persistent understanding of project structure - Redundant explanation of code is required in each session - Maintaining implementation consistency is challenging Persistent-Code solves these problems by: - Creating a knowledge graph of code components and their relationships - Tracking implementation status of each component - Providing tools to navigate, query, and understand the codebase - Assembling minimal necessary context for specific coding tasks - Maintaining persistent knowledge across chat sessions ## LlamaIndex Integration Persistent-Code leverages LlamaIndex to provide enhanced semantic understanding: 1. **Semantic Search**: Find code components based on meaning, not just keywords 2. **Vector Embeddings**: Code is embedded into vector space for similarity matching 3. **Knowledge Graph**: Relationships between components are tracked semantically 4. **Contextual Retrieval**: Related code is retrieved based on semantic relevance This integration allows Claude to understand your codebase at a deeper level: - Find functions based on what they do, not just what they're called - Get more relevant code components when preparing context - Better understand the relationships between components - More accurately retrieve examples of similar implementations ## Installation ### Prerequisites - Python 3.10 or higher - UV package manager (recommended) or pip ### Setting Up ```bash # Clone repository git cl…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.