Sinter MCP server

sinter

A local code knowledge graph for coding agents, shipped as one static binary. sinter builds a typed, directed graph of a repository's symbols with tree-sitter and keeps it fresh incrementally. Start in an unfamiliar repository with sinter map: it returns a bounded structural inventory with module node/file counts, dependency hubs measured by graph in-degree, documentation entry points, and graph-health limitations. It does not infer runtime entry points or domain ownership. Then use the graph for focused work:

cross-file and cross-language (sinter affected). Traversal stops at hubs and names them; test dependents are counted, not listed, unless asked for.

• Reverse blast radius — what transitively depends on a symbol,

(sinter impact), plus --expect for the unfinished-refactor check: direct dependents of a symbol the diff did not touch.

• Paths — how one symbol reaches another (sinter path).
• Diff impact — which symbols and tests a changeset can affect

(sinter grep '' --within 'affected()'), replacing the run-affected-then-grep-the-files pipeline.

• Bounded text search — a regex search whose corpus is a graph traversal

syntax provides the necessary type information, sinter resolves self receivers, locally typed receivers, typed fields, and explicit static/class calls. Complete receiver-call binding often requires a fresh SCIP index; zero setup is not compiler-complete resolution.

• Polyglot, zero setup — syntax-only graphs work without an LSP. When the

starting points from names, docs, paths, signatures, string literals, and limited call evidence. Its confidence line reflects the evidence class of the top hit; --explain adds the ranking-margin bucket and that bucket's holdout count with a 95% interval (the holdout is 46 cases, so the interval is wide). The bucket is not a per-result probability; ask is a navigator, not a semantic answer engine.

• Calibrated lexical navigation — sinter ask ranks content-bearing

card with its definition (attributes included) and a one-line used-by tally; --body adds the source (whole when it fits in 60 lines, else up to the byte budget), --impls the type's impl blocks, and show @file:line names the enclosing symbol. A span over 8 KB or 200 lines is a black hole no body dump can show: the card outlines it instead, listing the nested definitions, literal branches and command literals inside it with their line numbers (--outline forces it).

• Symbol orientation — sinter show turns a selected symbol into a compact

the task against real node names (fuzzy when needed, shown as term ~> symbol) and seeds from them, returning edit candidates, string literals and hand-maintained mirrors that mention the task's terms, and affected tests as runnable commands with the symbol that reached each. It never abstains while it has hits. Add --workspace to rank candidates across declared member repositories in one packet.

• Task evidence packet — sinter context "" resolves identifiers in

depth-one call edges in an explicit corpus scope. Its decision is one of violated, holdsforindexedsnapshot, or notproven; it never claims runtime exhaustiveness. sinter assert deletable tallies every depth-one dependent across all scopes, grouped by scope.

• Snapshot-scoped assertions — sinter assert no-callers checks

with a stable symbol key. sinter verify-doc re-resolves managed citations and fails on moved, missing, invalid, or identity-free references.

• Citation maintenance — sinter cite emits a Markdown location

distributed systems: blast radius, paths, and PR impact across service boundaries

• Cross-repo workspaces — federated graphs over many repos for

Shortened. The full README is on GitHub.