by mcpware
Organize all your Claude Code configs in one dashboard — memories, skills, MCP servers, commands, agents, rules, hooks. Drag-and-drop between scopes.
# Add to your Claude Code skills
git clone https://github.com/mcpware/claude-code-organizer
English | 简体中文 | 繁體中文 | 廣東話 | 日本語 | 한국어 | Español | Bahasa Indonesia | Italiano | Português | Türkçe | Tiếng Việt | ไทย
Organize all your Claude Code memories, skills, MCP servers, commands, agents, rules, and hooks — view by scope hierarchy, move between scopes via drag-and-drop.
100+ stars in 5 days! This project had 11 stars when I first posted it on Reddit 3 days ago. Real users tested it, gave feedback, and helped shape what it is today. First open source project — thank you to everyone who starred, tested, and reported issues. This is just the beginning.

Demo video recorded by AI automatically using Pagecast
Two things happen silently every time you use Claude Code — and neither one is visible to you.
This is a real project directory after two weeks of use:

If you start a Claude Code session under this directory, 70.9K tokens are already loaded before you start any conversation. That's 35.4% of your 200K context window — gone before you type a single character. Estimated cost just for this overhead: $1.06 USD per session on Opus, $0.21 on Sonnet.
The remaining 64.5% is shared between your messages, Claude's responses, and tool results before context compression kicks in. The fuller the context, the less accurate Claude becomes — an effect known as context rot.
Where does 70.9K come from? It includes everything we can measure offline — your CLAUDE.md, memories, skills, MCP server definitions, settings, hooks, rules, commands, and agents — tokenized per-item. Plus an estimated system overhead (~21K tokens) for the immutable scaffold Claude Code loads on every API call: the system prompt, 23+ built-in tool definitions, and MCP tool schemas.
And that's just what we can count. It does not include runtime injections — tokens Claude Code silently adds during a session:
Your actual mid-session usage is significantly higher than 70.9K. You just can't see it.
Claude Code silently creates memories, skills, MCP configs, commands, agents, and rules every time you work — and dumps them into whatever scope matches your current directory. A preference you wanted everywhere? Trapped in one project. A deploy skill that belongs to one repo? Leaked into global, contaminating every other project.
It also creates duplicate memories without asking. In the screenshot above, you can see three separate memories about Slack updates — "Keep structure in Slack messages", "Slack updates don't always need a specific recipient", and "Always use slack-update skill for reports" — all saying essentially the same thing, each one wasting tokens every session.
A Python pipeline skill sitting in global gets loaded into your React frontend session. Duplicate MCP entries initialize the same server twice. Stale memories from two weeks ago contradict your current instructions. Every wrong-scope item wastes tokens and degrades accuracy.
You have no way to see the full picture. No command shows all items across all scopes, all inheritance, all at once.
npx @mcpware/claude-code-organizer
One command. See everything Claude has stored — organized by scope hierarchy. See your token budget before you start. Drag items between scopes. Delete stale memories. Find duplicates. Take control of what actually influences Claude's behavior.
First run auto-installs a
/ccoskill — after that, just type/ccoin any Claude Code session to open the dashboard.
Open the dashboard, click Context Budget, switch to By Tokens — the biggest consumers are at the top. A 2.4K token CLAUDE.md you forgot about? A skill duplicated across three scopes? Now you see it. Clean it up, save 10-20% of your context window.
You told Claude "I prefer TypeScript + ESM" while inside a project, but that preference applies everywhere. Drag that memory from Project to Global. Done. One drag. A deploy skill sitting in global only makes sense for one repo? Drag it into that Project scope — other projects won't see it anymore.
Claude auto-creates memories from things you said casually, or things it thought you wanted remembered. A week later they're irrelevant but still loaded into every session. Browse, read, delete. You control what Claude thinks it knows about you.
We analyzed the source code of every Claude Code tool we could find — analytics dashboards (9K+ stars), desktop apps (600+ stars), VS Code extensions, TUI session managers, terminal statuslines. None offered true scope hierarchy + drag-and-drop cross-scope moves in a standalone dashboard.
| Feature | Claude Code Organizer | Desktop app (600+⭐) | VS Code extension | Analytics dashboards | TUI tools | |---------|:---:|:---:|:---:|:---:|:---:| | True scope hierarchy (Global > Workspace > Project) | Yes | No | Partial (no workspace) | No | No | | Drag-and-drop moves | Yes | No | No | No | No | | Cross-scope moves | Yes | No | One-click | No | No | | Undo on every action | Yes | No | No | No | No | | Bulk operations | Yes | No | No | No | No | | Real MCP server management | Yes | Global only | Stub (icon only) | No | No | | Context budget (token breakdown) | Yes | No | No | No | No | | Commands + Agents + Rules | Yes | No | No | No | No | | Session management | Yes | No | No | Yes | Yes | | Search & filter | Yes | No | Yes | Yes | No | | MCP tools (AI-accessible) | Yes | No | No | No | No | | Zero dependencies | Yes | No (Tauri+React) | No (VS Code) | No (Next.js/FastAPI) | No (Python) | | Standalone (no IDE) | Yes | Yes | No | Yes | Yes |
skills-lock.json~/.claude/, not just a viewernpx @mcpware/claude-code-organizer
npm install -g @mcpware/claude-code-organizer
claude-code-organizer
No comments yet. Be the first to share your thoughts!