Knowing MCP Server

Content-addressed code graph with 22 MCP tools for AI agents. Exposed over MCP by the knowing mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Self-adapting code intelligence engine. Observes its own graph density and adjusts retrieval strategy automatically. 38 edge types, 28 MCP tools, 263 equivalence classes, cryptographic proofs. Gets smarter with scale, not dumber.

• Staleness detection for free. — Changed file = new hash = stale edges are known without scanning
• Caching for free. — Same package root = same results. 93x speedup on unchanged queries
• Integrity for free. — Verify all stored hashes and snapshot chain continuity. 98ms
• History for free. — Each snapshot is a Merkle root tied to a git commit. Walk the chain
• Feedback expiration for free. — Feedback stores the package Merkle root. Code changes = root changes = old feedback is invisible
• Proofs for free. — Merkle path from leaf to root is a self-contained cryptographic proof

Adding it to your client

The server ships on npm as @blackwell-systems/knowing, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• untrack_repo — Evict all data for a repository (nodes, edges, files, snapshots, feedback, task memory, graph notes)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the knowing mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Knowing's toolset — untrack_repo — is a fair guide to whether it matches your workflow. It is maintained by blackwell-systems; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.