Claude Code Organizer

English | 简体中文 | 繁體中文 | 日本語 | 한국어

Organize all your Claude Code memories, skills, MCP servers, and hooks — view by scope hierarchy, move between scopes via drag-and-drop.

The Problem

Claude Code silently creates memories, skills, and MCP configs 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.

This isn't just messy — it hurts your AI's performance. Every session, Claude loads all configs from the current scope plus everything inherited from parent scopes into your context window. Wrong-scope items = wasted tokens, polluted context, and lower accuracy. A Python pipeline skill sitting in global gets loaded into your React frontend session. Duplicate MCP entries initialize the same server twice. Stale memories contradict your current instructions.

"Just ask Claude to fix it"

You could ask Claude Code to manage its own config. But you'll go back and forth — ls one directory, cat each file, try to piece together the full picture from fragments of text output. There's no command that shows the entire tree across all scopes, all items, all inheritance at once.

The fix: a visual dashboard

npx @mcpware/claude-code-organizer

One command. See everything Claude has stored — organized by scope hierarchy. Drag items between scopes. Delete stale memories. Find duplicates. Take control of what actually influences Claude's behavior.

Example: Project → Global

You told Claude "I prefer TypeScript + ESM" while inside a project, but that preference applies everywhere. Open the dashboard, drag that memory from Project to Global. Done. One drag.

Example: Global → Project

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.

Example: Delete stale memories

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.

Features

• Scope-aware hierarchy — See all items organized as Global > Workspace > Project, with inheritance indicators
• Drag-and-drop — Move memories between scopes, skills between global and per-repo, MCP servers between configs
• Move confirmation — Every move shows a confirmation modal before touching any files
• Same-type safety — Memories can only move to memory folders, skills to skill folders, MCP to MCP configs
• Search & filter — Instantly search across all items, filter by category (Memory, Skills, MCP, Config, Hooks, Plugins, Plans)
• Detail panel — Click any item to see full metadata, description, file path, and open in VS Code
• Full per-project scanning — Every scope shows all item types: memories, skills, MCP servers, configs, hooks, and plans
• Real file moves — Actually moves files in ~/.claude/, not just a viewer
• 45 E2E tests — Playwright test suite with real filesystem verification after every operation

Why a Visual Dashboard?

Claude Code can already list and move files via CLI — but you're stuck playing 20 questions with your own config. The dashboard gives you full visibility in one glance:

Quick Start

Option 1: npx (no install needed)

npx @mcpware/claude-code-organizer

Option 2: Global install

npm install -g @mcpware/claude-code-organizer
claude-code-organizer

Option 3: Ask Claude

Paste this into Claude Code:

Run npx @mcpware/claude-code-organizer — it's a dashboard for managing Claude Code settings. Tell me the URL when it's ready.

Opens a dashboard at http://localhost:3847. Works with your real ~/.claude/ directory.

What It Manages

Scope Hierarchy

Global                       <- applies everywhere
  Company (workspace)        <- applies to all sub-projects
    CompanyRepo1             <- project-specific
    CompanyRepo2             <- project-specific
  SideProjects (project)     <- independent project
  Documents (project)        <- independent project

Child scopes inherit parent scope's memories, skills, and MCP servers.

How It Works

1. Scans ~/.claude/ — discovers all projects, memories, skills, MCP servers, hooks, plugins, plans
2. Resolves scope hierarchy — determines parent-child relationships from filesystem paths
3. Renders dashboard — scope headers > category bars > item rows, with proper indentation
4. Handles moves — when you drag or click "Move to...", actually moves files on disk with safety checks

Comparison

We looked at every Claude Code config tool we could find. None offered visual scope hierarchy + drag-and-drop cross-scope moves in a standalone dashboard.

Platform Support

Project Structure

src/
  scanner.mjs       # Scans ~/.claude/ — pure data, no side effects
  mover.mjs         # Moves files between scopes — safety checks + rollback
  server.mjs        # HTTP server — routes only, no logic
  ui/
    index.html       # HTML structure
    style.css        # All styling (edit freely, won't break logic)
    app.js           # Frontend rendering + SortableJS + interactions
bin/
  cli.mjs            # Entry point

Frontend and backend are fully separated. Edit src/ui/ files to change the look without touching any logic.

API

The dashboard is backed by a REST API:

License

MIT

More from @mcpware

Author

ithiria894 — Building tools for the Claude Code ecosystem.