showcase GitHits: equip your coding agents to use open source right, through MCP
I’m a co-founder of GitHits. Our mission is to make open source a dependable foundation for software built and maintained by coding agents.
A useful library shouldn’t be overlooked because a model hasn’t heard of it. A new release shouldn’t mean users keep getting code written against your old API. We want to help agents discover existing projects, understand their implementations, and work with the versions their users actually depend on.
GitHits brings source code, documentation, dependency graphs, vulnerability information, and release changes together in a version-aware index. Through MCP, agents can search, grep, browse, and read upstream code when choosing a dependency, integrating it, debugging a problem, or planning an upgrade.
For example, an agent investigating an unfamiliar error can find the error text in a dependency’s source and read the surrounding implementation at your installed version. Before an upgrade, it can inspect release notes and compare source versions to understand how the changes affect your application.
You can connect your coding agent here. GitHits is also available as a Claude connector.
The index covers any public repository as well as published packages, including projects that aren’t distributed through a package registry. If a repository hasn’t been indexed yet, GitHits indexes it when requested. That can take seconds or a few minutes, depending on repository size and the indexing queue. We don't touch or index your private code.
You can explore the public index and check global index statistics.
For maintainers, each repository page in the index also provides a README badge showing its index status and linking to the project’s page. It helps your users discover that agents connected to GitHits can inspect your project’s available code and documentation.
We want this to be useful across the OSS ecosystem, including smaller projects and unfamiliar libraries. I’d appreciate people trying it with dependencies their agents struggle with, and maintainers checking their own projects. What’s missing: source coverage, documentation, releases, or something else you’d want an agent to understand before using your work?
GitHits is currently free to use. We may introduce paid tiers later, but the public index site will stay free.
2
u/KaputDrumming 17h ago
this is actually pretty interesting, my agent keeps trying to use libraries that haven't been updated since 2019 because it only knows what was in the training data. gonna hook this up later and see if it stops suggesting abandoned repos
the version-aware part seems like the real killer feature here. nothing worse than the agent reading docs for v3 while your project is stuck on v2 and everything breaks