Knowing
Let agents query a content-addressed code graph so navigation and impact analysis stay stable as files churn.
Overview
Knowing is an MCP server for the Build phase that serves a content-addressed code graph through 22 tools for AI agents.
What is this MCP server?
- Content-addressed code graph for deterministic structure identity
- 22 MCP tools tailored to graph traversal and agent queries
- npm package @blackwell-systems/knowing with stdio transport
- Complements file-read workflows with relationship-aware context
- Version 0.4.1 from blackwell-systems/knowing on GitHub
- Content-addressed code graph model
- Package version 0.4.1
Community signal: 10 GitHub stars.
What problem does it solve?
Agents lose the plot in bigger repos because plain file search does not preserve stable structure or dependency context across edits.
Who is it for?
Solo builders with non-trivial codebases who want graph-level codebase intelligence in the agent loop via local MCP.
Skip if: Greenfield hello-world repos where ripgrep and single-file context are enough, or teams that cannot run a local Node graph indexer.
What do I get? / Deliverables
Your agent queries a content-addressed graph via MCP so refactors, reviews, and follow-up fixes target the right neighborhoods of the codebase.
- 22 graph-oriented MCP tools wired to your repo
- Stable structural context for agent-driven edits and reviews
Recommended MCP Servers
Journey fit
Build is the canonical shelf because the code graph is created and consumed while implementing; the same graph supports review at Ship and targeted changes in Operate. Agent-tooling fits a dedicated MCP layer that models repository structure for agents rather than shipping end-user product UI.
How it compares
Local code-graph MCP server, not hosted GitHub search or a generic architecture markdown skill.
Common Questions / FAQ
Who is Knowing for?
Indie developers using MCP-enabled agents who need relationship-aware codebase queries beyond linear file reads.
When should I use Knowing?
During Build for implementation and refactors, at Ship for review-style impact questions, and in Operate when iterating on known subsystems.
How do I add Knowing to my agent?
Install @blackwell-systems/knowing from npm, configure stdio MCP in your client, point it at your repository root per the project README, and invoke the 22 graph tools from agent sessions.