AgentStack
MCP unreviewed MIT Self-run

Knowledge Master

mcp-subzone-knowledge-master · by subzone

Local-first knowledge graph for developers. Graph-native RAG with MCP server, blast radius analysis, convention enforcement. Your AI agent's permanent memory.

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add mcp-subzone-knowledge-master

Open-source listing — not yet scanned by AgentStack. Follow the source repository for install instructions.

Security review

⚠ Flagged

1 finding(s); flagged for manual review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures
  • high Pipes remote content directly into a shell (remote code execution).

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Knowledge Master? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

⚡ Knowledge Master

Your codebase's memory. A local knowledge graph that gives AI agents real understanding of your architecture — not just text search.

[](LICENSE)


Why

Every time you start a new AI chat, it forgets everything. You re-explain your architecture, conventions, dependencies. Knowledge Master gives your AI permanent, structured memory about your entire system.

Unlike flat RAG tools that return "chunks about X", Knowledge Master builds a graph — so it can answer "what breaks if I change X?" by traversing actual relationships.

What it does

  • 🔍 Semantic search across all your code, docs, and configs
  • 🕸️ Knowledge graph — relationships between services, people, repos, technologies
  • 💥 Blast radius — "what depends on this service/file/technology?"
  • 📏 Convention enforcement — detects and enforces your team's patterns
  • 🤖 MCP server — plugs directly into AI agents (Kiro, Claude, Cursor)
  • 🖥️ Web UI — search, browse, visualize your knowledge graph
  • 🔒 Local-first — nothing leaves your machine

Prerequisites

| Dependency | macOS | Ubuntu/Debian | Windows | |---|---|---|---| | Docker | brew install colima && colima start or Docker Desktop | sudo apt install docker.io docker-compose-plugin | Docker Desktop | | Ollama | brew install ollama && ollama serve | curl -fsSL https://ollama.com/install.sh \| sh | Ollama installer | | Python 3.11+ | brew install python@3.12 | sudo apt install python3.12 python3.12-venv | python.org |

Quick Start

# Install (pick one)
pipx install knowledge-master         # recommended (isolated, clean)
pip install knowledge-master           # or with pip

# Or via Homebrew (macOS)
brew install pipx && pipx install knowledge-master

# Or from source
git clone https://github.com/subzone/knowledge-master.git
cd knowledge-master
python3 -m venv .venv && source .venv/bin/activate
pip install -e .

# One command setup
km start

# Index your first repo
km index ~/path/to/your/project

# Search
km search "authentication flow"

# Check blast radius
km blast-radius postgres

# Start web UI with graph visualization
km serve

Requirements: Docker, Ollama, Python 3.11+

Features

Semantic Search with Graph Context

$ km search "how does auth work"
┌────────┬──────────────────────┬─────────────────────┬──────────────────────┐
│ Score  │ Source               │ Context             │ Preview              │
├────────┼──────────────────────┼─────────────────────┼──────────────────────┤
│ 0.847  │ src/auth/service.py  │ repo:myapp, by:Alex │ JWT token validat... │
│ 0.791  │ docs/auth.md         │ repo:myapp          │ Authentication f...  │
└────────┴──────────────────────┴─────────────────────┴──────────────────────┘

Blast Radius Analysis

$ km blast-radius auth-service
💥 Blast radius: auth-service
├── ⚙️ user-service (Service, via DEPENDS_ON)
├── ⚙️ payment-service (Service, via DEPENDS_ON)
├── 📦 frontend (Repo, via USES_SERVICE)
└── 👤 Alex (Person, via AUTHORED)

4 entities affected

Convention Enforcement

$ km check-conventions ~/my-project
  ✓ src/ directory (structure)
  ✓ separate test directory (testing)
  ✗ snake_case files (file-naming)
  ✓ Repository pattern (design-pattern)

1 convention(s) violated

Web UI & Graph Visualization

$ km serve
Knowledge Master UI → http://127.0.0.1:9999

Interactive force-directed graph showing your entire knowledge topology:

  • 📦 Repos (blue) → 🔧 Technologies (red)
  • ⚙️ Services (orange) → Dependencies
  • 👤 People → Authorship
  • 📏 Conventions (purple)

MCP Integration (AI Agents)

Add to your Kiro/Claude agent config:

{
  "mcpServers": {
    "knowledge": {
      "command": "km-server"
    }
  }
}

Your AI agent gets these tools:

  • search — semantic search with graph context
  • blast_radius — dependency analysis
  • check_conventions — verify code follows team patterns
  • index_repo — add new repos to the knowledge base

Architecture

┌─────────────────────────────────────────────────┐
│                  Your AI Agent                    │
│              (Kiro / Claude / Cursor)             │
└────────────────────┬────────────────────────────┘
                     │ MCP Protocol
┌────────────────────▼────────────────────────────┐
│              Knowledge Master                    │
│                                                  │
│  ┌──────────┐  ┌────────────┐  ┌────────────┐  │
│  │  Search  │  │Blast Radius│  │ Conventions│  │
│  └────┬─────┘  └─────┬──────┘  └─────┬──────┘  │
│       │               │               │         │
│  ┌────▼───────────────▼───────────────▼──────┐  │
│  │            FalkorDB (Graph + Vector)       │  │
│  │                                           │  │
│  │  [Repo]──USES_TECH──▶[Tech]              │  │
│  │    │                                      │  │
│  │    ├──DEFINES_SERVICE──▶[Service]         │  │
│  │    │                      │               │  │
│  │    ├──FOLLOWS──▶[Convention]              │  │
│  │    │                                      │  │
│  │  [Person]──AUTHORED──▶[Document]          │  │
│  │                          │                │  │
│  │                    [Chunk + Embedding]     │  │
│  └───────────────────────────────────────────┘  │
│                                                  │
│  ┌───────────────────────────────────────────┐  │
│  │         Ollama (nomic-embed-text)          │  │
│  └───────────────────────────────────────────┘  │
└──────────────────────────────────────────────────┘

Commands

| Command | Description | |---|---| | km start | Boot Docker + pull embedding model | | km stop | Stop containers | | km index | Index a git repo or docs directory | | km search | Semantic search with re-ranking | | km blast-radius | Multi-layer dependency analysis | | km safe-to-change | Risk assessment (safe/risky/dangerous) | | km who-owns | File ownership (git blame, recency-weighted) | | km check-conventions | Verify code follows detected patterns | | km connect | Pull from external MCP (email, Slack) | | km setup | Auto-configure MCP for AI tools | | km watch | File watcher with auto re-index | | km upgrade | Migrate graph schema | | km prune | Remove stale/orphaned data | | km changelog | Generate CHANGELOG.md | | km list | Show indexed repos, techs, stats | | km remove | Remove a source | | km serve | Start web UI at http://127.0.0.1:9999 | | km status | Check system health |

What gets extracted automatically

When you index a repo, Knowledge Master detects:

| Category | Examples | |---|---| | Tech stack | Languages, frameworks, packages from dependency files | | Services | From docker-compose.yml and K8s manifests | | Dependencies | Service-to-service relationships | | Conventions | File naming (snake_case/kebab-case), folder structure, design patterns | | People | Git commit authors and file ownership | | Code structure | Functions, classes, chunked by AST-aware boundaries |

Feature Status

| Feature | Status | Notes | |---|---|---| | Semantic search + re-ranking | ✅ Stable | Two-pass retrieval with confidence scoring | | Knowledge graph (FalkorDB) | ✅ Stable | Nodes, edges, vector index, schema versioning | | CLI (14 commands) | ✅ Stable | start, index, search, blast-radius, safe-to-change, who-owns, etc. | | MCP server (8 tools) | ✅ Stable | search, blastradius, safetochange, whoowns, check_conventions, index, status | | REST API | ✅ Stable | /api/v1/ with OpenAPI docs | | Web UI + graph viz | ✅ Stable | htmx + D3, search, file browser, graph | | Git repo indexing | ✅ Stable | Parses code, extracts authors, detects tech stack | | Multi-language static analysis | ✅ Stable | Python (ast), TypeScript, Go, Rust (tree-sitter) | | Blast radius (multi-layer) | ✅ Stable | Imports → services → people, confidence levels | | safe-to-change risk assessment | ✅ Stable | Blast radius + test coverage = risk score | | Git blame ownership | ✅ Stable | Recency-weighted (3x/2x/1x) | | Schema migrations | ✅ Stable | Auto-migrate, km upgrade | | Deduplication | ✅ Stable | Content hash, skips unchanged | | Convention detection | ⚡ Basic | Folder structure + file naming patterns | | Email connector (ms-365) | 🧪 Experimental | Works, requires external MCP setup | | km watch | 🧪 Experimental | Polling-based, may change |

Legend: ✅ Stable — ⚡ Basic (works, limited scope) — 🧪 Experimental (may change)

Comparison

| Feature | Knowledge Master | Generic RAG | GitHub Copilot | Glean | |---|---|---|---|---| | Graph relationships | ✅ | ❌ | ❌ | Partial | | Blast radius analysis | ✅ | ❌ | ❌ | ❌ | | Convention enforcement | ✅ | ❌ | ❌ | ❌ | | Local-first (no cloud) | ✅ | ✅ | ❌ | ❌ | | MCP integration | ✅ | ❌ | ❌ | ❌ | | Multi-repo intelligence | ✅ | Partial | ❌ | ✅ | | Cost | Free | Free | $19/mo | $15-30/mo |

Development

# Run tests
pytest

# Lint
ruff check knowledge_master/

# Run MCP server directly
python -m knowledge_master.server

# Run CLI directly
python -m knowledge_master.cli status

Security

Knowledge Master runs entirely on your machine. No data leaves localhost.

  • All ports bound to 127.0.0.1 (not accessible from LAN)
  • Ollama runs locally — no cloud API calls
  • MCP server uses stdio (no network exposure)
  • Optional API key auth for REST endpoints
# Enable API key auth
export KM_API_KEY=$(openssl rand -hex 32)
km serve

See [SECURITY.md](SECURITY.md) for full security model, risks, and hardening guide.

Troubleshooting

| Issue | Fix | |---|---| | km start fails with "Docker not running" | Start Docker: colima start (macOS) or sudo systemctl start docker (Linux) | | km start fails with "Ollama not found" | Install Ollama from https://ollama.com and run ollama serve | | km index is slow | First run downloads the embedding model (~274MB). Subsequent runs are fast. | | Web UI shows "Connection refused" | Make sure containers are running: km start | | Search returns poor results | Index more content. Quality improves with more context in the graph. | | Port 9999 already in use | Use km serve --port 8888 |

License

MIT

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.