u/skvark

I'm really happy to see MCP moving to a stateless approach.

The original stateful session model made remote MCP servers unnecessarily difficult to operate. Horizontal scaling, load balancing, failover, and serverless deployments all became more complicated because requests were tied to server-side session state.

A stateless protocol lets any instance handle any request, which is how modern HTTP services are expected to behave. It simplifies infrastructure, improves reliability, and makes remote MCP deployments much easier to scale.

This feels like the right direction for the protocol. Microsoft has a good overview of the changes:

https://techcommunity.microsoft.com/blog/appsonazureblog/mcp-just-went-stateless-%E2%80%94-what-the-2026-spec-changes-about-scaling-on-app-servic/4530222

Coding agents can grep, search, and read your local repository, but they can't do the same thing across the open-source code your application depends on.

When an agent needs to understand a dependency, find a working implementation, or investigate version-specific behavior, it often falls back to documentation and web search. The actual answer is frequently in source code, issues, discussions, or pull requests.

We've been working on exposing that context through MCP and CLI.

The tools roughly map to following workflows:

Finding examples

Search for implementation examples across repositories, issues, discussions, and pull requests with get_example. Returns prior art, how did others do something, how to solve some specific problem, how is something supposed to be used. This is also exposed in our current UI, the next features are only through our CLI or MCP.

Navigating a specific repository or package

Search within a repository or package with search, list files with code_files, read source files and line ranges with code_read, and grep with code_grep.

Same workflow that your coding agent is using locally, just almost instantly available for any repo or package out there. No cloning needed, GitHits handles everything automatically.

Reading documentation

Discover available docs with docs_list and read pages with docs_read.

Inspecting packages

Inspect package metadata with pkg_info, dependency trees with pkg_deps, known vulnerabilities with pkg_vulns, changelogs with pkg_changelog, and upgrade changes with pkg_upgrade_review.

The index is version-aware, so agents can inspect the code and package data for the versions they're actually working with.

Get started with

npx githits@latest init

or

https://githits.com for manual sign up

Happy to answer questions about retrieval, indexing, MCP integration, or how we're thinking about dependency context for coding agents.