Install
$ agentstack add mcp-oyekamal-claude-code-flow-visualizer β scanned Β· β verified, works with Claude Code, Cursor, and more.
Security review
β PassedNo issues found. Passed automated security review. Β· v0.1.0 How review works β
- β Prompt-injection patterns
- β Secret / credential exfiltration
- β Dangerous shell & filesystem operations
- β Untrusted network calls
- β Known-malicious package signatures
What it can access
- β Network access No
- β 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work βAbout
Claude Code Flow Visualizer β See Your Entire Agent Harness as an Interactive Graph
Visualize any Claude Code configuration (CLAUDE.md, subagents, skills, slash commands, hooks, MCP servers, schedulers) as one interactive flow diagram β straight from a GitHub URL, a ZIP, or a local folder. No install for your target repo, no backend, 100% client-side.
Why
Claude Code agent setups live as scattered markdown files: CLAUDE.md, .claude/agents/*.md, .claude/skills/*/SKILL.md, commands, settings.json hooks, and .mcp.json connectors. To understand how an existing harness works β which agent delegates to which, what skills fire when, where Notion/database/MCP connections plug in β you'd normally have to open and read every single file.
This tool parses the whole project and renders it as a wired graph in seconds:
- π€ Agents with model + tool badges, delegation edges traced from prompt bodies
- π Skills attached to the agents and commands that actually reference them
- β¨οΈ Slash commands, πͺ lifecycle hooks, β° schedulers (GitHub Actions / cron)
- π MCP connectors and ποΈ memory / state stores drawn as distinct node types
- π¨ Pipeline lints: broken delegation references, duplicate agent names, circular delegation, orphan skills, reviewers with write access, orchestrators missing the
Tasktool, vague trigger descriptions
Quick Start
git clone https://github.com/oyekamal/claude-code-flow-visualizer.git
cd claude-code-flow-visualizer
npm install
npm run dev # β http://localhost:5173
Then either:
- Paste a GitHub repo (
owner/repo, full URL, or a/tree/branch/subfolderlink) and hit VISUALIZE - Upload a ZIP (GitHub β Code β Download ZIP) β fully offline
- Upload a folder β point it at any local clone
- Or click LOAD DEMO HARNESS to explore a sample multi-agent content pipeline
Features
Interactive canvas
Pan, zoom, and drag nodes. Hover or select any node to highlight its wiring. Edge styles encode meaning: solid = delegation, dashed = skill use, dotted = MCP connection, dash-dot = state reads/writes, animated = scheduled loop.
Node inspector with raw source
Click any agent, skill, command, hook, or connector to see its description trigger, model, tools, incoming/outgoing references β and the underlying markdown file, side by side.
Pipeline lints ("don't break my harness")
The validator catches the ways multi-agent pipelines actually break:
| Check | Level | |---|---| | Delegation to an agent/skill that doesn't exist | error | | Orchestrator delegates but lacks the Task tool | error | | Duplicate agent names (later file shadows earlier) | warn | | Circular delegation loops | warn | | Reviewer/validator agents holding write tools | warn | | Skills never referenced by anything (dead weight) | warn | | Missing or vague descriptions (agents never auto-trigger) | warn/info | | MCP servers configured but never used | info |
Three import transports
- GitHub API + raw.githubusercontent (supports private repos via token)
- jsDelivr mirror β no rate limits for public repos
- Claude API relay β works even inside sandboxed previews where only
api.anthropic.comis reachable
Unparseable content is never dropped β it's counted and preserved verbatim.
How it works
files β parser β project model β graph builder β layered layout β SVG canvas. A single React component (~1,700 lines, no graph library): minimal YAML-frontmatter parser, path classifier for the .claude contract, reference extraction from prompt bodies (backticked names, @mentions, delegation verbs), BFS-layered layout with barycenter ordering, and a lint pass over the resulting graph.
Testing
End-to-end tested with Playwright (test_e2e.py): empty state, demo graph, inspector, lint panel, live GitHub import, ZIP import.
python3 -m venv .venv && .venv/bin/pip install playwright && .venv/bin/playwright install chromium
npm run dev &
.venv/bin/python test_e2e.py
Roadmap
- Canvas β files: edit nodes in the UI and regenerate valid markdown (two-way sync)
- Impact analysis + diff preview before writing changes back
- Pre-built agent/skill library and flow templates (orchestratorβworkers, builder+validator, scheduled loop with memory)
Keywords
Claude Code visualizer Β· CLAUDE.md viewer Β· Claude subagents graph Β· .claude directory explorer Β· AI agent orchestration diagram Β· multi-agent pipeline visualization Β· MCP server map Β· agent harness debugging Β· Anthropic Claude agents
License
MIT Β© oyekamal
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source β we do not rehost the code.
- Author: oyekamal
- Source: oyekamal/claude-code-flow-visualizer
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.