CristianoCiuti/reponova

<p align="center"> <img src="https://img.shields.io/npm/v/reponova?style=flat-square&color=cb3837&logo=npm" alt="npm version" /> <img src="https://img.shields.io/npm/dm/reponova?style=flat-square&color=blue" alt="npm downloads" /> <img src="https://img.shields.io/node/v/reponova?style=flat-square&color=339933&logo=node.js&logoColor=white" alt="node version" /> <img src="https://img.shields.io/github/license/CristianoCiuti/reponova?style=flat-square&color=green" alt="license" /> <img src="https://img.shields.io/badge/MCP-compatible-8A2BE2?style=flat-square" alt="MCP compatible" /> </p> <p align="center"> <img src="media/reponova-social.jpg" alt="RepoNova" width="600" /> </p> <h1 align="center">🤖 RepoNova 🔭</h1> <p align="center"> <strong>Turn your codebase into a knowledge graph. Query it with AI.</strong> </p> <p align="center" style="font-style: italic;"> Knowledge graph builder &amp; <a href="https://modelcontextprotocol.io/">MCP</a> server for AI code assistants.<br/> Extracts symbols, relationships, and semantics from your code — then exposes the entire structure<br/> as 11 graph tools that any MCP-compatible agent can use. </p>

---

⚠️ Alpha — Active Development APIs, config format, and CLI may change between releases. Already usable in production workflows. Open an issue if something doesn't work.

---

Why RepoNova?

AI agents read files one at a time. They don't understand how your codebase fits together — which functions call what, which modules depend on which, where the architectural bottlenecks are.

RepoNova fixes that. It builds a persistent knowledge graph of your entire codebase (or multiple repos) and gives your AI agent 11 specialized tools to query it: search, impact analysis, shortest path, semantic similarity, community detection, and more.

One build. Persistent graph. Instant queries across sessions. No re-reading files. No burning tokens o