mcpware/claude-code-organizer
Organize all your Claude Code memories, skills, MCP servers, and hooks — view by scope hierarchy, move between scopes via drag-and-drop
Platform-specific configuration:
{
"mcpServers": {
"claude-code-organizer": {
"command": "npx",
"args": [
"-y",
"claude-code-organizer"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
Organize all your Claude Code memories, skills, MCP servers, and hooks — view by scope hierarchy, move between scopes via drag-and-drop.
Ever asked Claude Code to "remember this", only to find it saved the memory to the wrong scope?
You're inside a project folder, you tell Claude to remember a preference — and it saves it to that project's scope. Switch to another project, and Claude has no idea. That memory is trapped.
The reverse happens too — skills or memories sitting in global scope that really only apply to one repo, leaking into everything else.
Want to fix it? You'd have to manually dig through ~/.claude/ and its encoded-path folders (-home-user-projects-my-app/), find the right file, and move it yourself.
Claude Code Organizer fixes this.
You told Claude to remember "I prefer TypeScript + ESM" while inside a project, but that preference applies everywhere. Open the dashboard, drag that memory from Project scope to Global scope. Done.
You have a deploy skill sitting in global, but it only makes sense for one repo. Drag it into that Project scope — other projects won't see it anymore.
---
Loading reviews...