dreamgraph
Builds a persistent knowledge graph of your codebase to catch breaking changes, auto-generate documentation, and enable cross-system reasoning without re-sca…
DreamGraph is a graph-first cognitive layer (graph → MCP → CLI → dashboard → extension) that builds a persistent knowledge graph to reason, validate changes, and generate docs.
- Detect API contract violations before deployment
- Auto-generate service dependency diagrams from code
- Validate schema migrations against dependent systems
Builds a persistent knowledge graph of your codebase to catch breaking changes, auto-generate documentation, and enable cross-system reasoning without re-scanning on every query.
Teams managing complex multi-service architectures who need to validate architectural decisions and keep docs in sync with code.
https://github.com/mmethodz/dreamgraph
By mmethodz
How to Get It
claude plugins install mmethodz/dreamgraph
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me detect API contract violations before deployment
Trust Signals Auto-scanned
Community Pulse Emerging
Discussed on Hacker News, Reddit
- Show HN: DreamGraph MCP v5 – An open source autonomous cognitive layer — Hacker News · 4 pts
- Show HN: DreamGraph – An autonomous cognitive layer for software systems — Hacker News · 4 pts
- Show HN: DreamGraph MCP v5.1 – Autonomous Cognitive Layer for Software Systems — Hacker News · 2 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 112 GitHub stars; 3 contributors; last commit 19d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 112 GitHub stars; 3 contributors; last commit 19d ago; license no license.