{"repo":"PatrickSys/codebase-context","free":true,"listed":false,"github":"https://github.com/PatrickSys/codebase-context","clone":"git clone https://github.com/PatrickSys/codebase-context.git","description":"Codebase Context gives AI agents understanding of your codebase through semantic code search, team conventions, patterns, and memory, so they use fewer tokens, spend less time, and produce better, more familiar output.","language":"TypeScript","stars":61,"topics":["ai-coding","claude","cursor","developer-tools","mcp","model-context-protocol","semantic-search","copilot","mcp-server","code-intelligence"],"license":null,"category":"mcp-servers","readme_excerpt":"codebase-context Map your team's conventions before your AI agent starts searching. You're tired of AI agents writing code that \"just works\" but still misses how your team actually builds things. They search too broadly, pick generic examples, and spend tokens exploring before they understand the shape of the repo. codebase-context changes the first step. Start with a bounded conventions map that shows the architecture, dominant patterns, and strongest local examples. Then search for the exact file, symbol, or workflow you need. Here's what codebase-context does: Starts with a bounded conventions map - The first call shows architecture layers, active patterns, golden files, and next calls without dumping vendored repos, fixtures, generated output, or oversized entrypoint lists into the default surface. Finds the right local example - Search does not just return code. Each result comes back with pattern signals, file relationships, and quality indicators so the agent can move from the map to the most relevant local example instead of wandering through raw hits. Knows what is current - Conventions are detected from your code and git history, not only from rules you wrote. The map distinguishes what is common from what is rising or declining, and points at the files that best represent the current direction. Adds support signals when you need them - Team memory and edit-readiness checks stay available, but as supporting context after the map and search have already narrowed the ","default_branch":null,"files":null,"tree":[],"storefront":"/r/PatrickSys","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/PatrickSys/codebase-context/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}