Claude Code Manager

See all your MCP servers, skills, commands, rules, and CLAUDE.md files in one place — across every project on your machine

Quick Start | Features | Usage | Configuration | Contributing

Quick Start

Option 1: pip (simplest)

pip install ccmanager
ccmanager ~/Projects

Option 2: uv tool (fastest, isolated)

uv tool install ccmanager
ccmanager ~/Projects

Don't have uv? Install it: curl -LsSf https://astral.sh/uv/install.sh | sh

Option 3: From Source

git clone https://github.com/simonstrumse/claude-code-manager.git
cd claude-code-manager
pip install -e .
ccmanager ~/Projects

On macOS, pip installs to ~/Library/Python/3.x/bin/ which may not be in PATH. Fix:

echo 'export PATH="$HOME/Library/Python/3.9/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc

Or use uv tool above — it handles PATH automatically.

Features

• Multi-Project Scanning — Scan an entire folder of projects and see all configurations at a glance
• 6 Configuration Tabs — Projects, MCP Servers, Skills, Commands, Rules, CLAUDE.md
• Content Preview — Press Enter to view full content of any skill, command, rule, or CLAUDE.md
• Cross-Navigation — Jump between projects and their MCP servers with g and s keys
• Project Discovery — Find Claude Code projects scattered across your system
• Usage Analytics — See which MCP servers are used most across your projects
• Privacy Mode — Toggle p to redact project names for screenshots

Usage

Launch the TUI

ccmanager ~/Projects      # Scan a projects folder
ccmanager                 # Scan current directory

Keyboard Navigation

Tabs Overview

What It Scans

The tool understands Claude Code's configuration precedence:

Scanned Locations

• MCP Servers: Enterprise, User, Project, Local levels
• Skills: ~/.claude/skills/*/SKILL.md and .claude/skills/*/SKILL.md
• Commands: ~/.claude/commands/*.md and .claude/commands/*.md
• Rules: ~/.claude/rules/**/*.md and .claude/rules/**/*.md
• CLAUDE.md: Root, .claude/, subdirectories, local variants

Project Structure

claude-code-manager/
├── mcp_tui.py          # Main TUI application (Textual)
├── mcp_scanner.py      # Configuration scanning logic
├── mcp_data.py         # Data models and classes
├── mcp_config.py       # User settings management
├── mcp_operations.py   # Project move/consolidate operations
├── requirements.txt    # Python dependencies
└── CHANGELOG.md        # Development history

Contributing

Contributions welcome! This is a learning project, so please be patient and constructive.

Development Setup

git clone https://github.com/YOUR_USERNAME/claude-code-manager.git
cd claude-code-manager
python3 -m venv venv && source venv/activate
pip install -e .

Guidelines

1. Test your changes — Make sure the TUI runs without crashing
2. Follow existing patterns — Look at how similar features are implemented
3. Document changes — Update CHANGELOG.md for significant changes
4. Keep it simple — Prefer readable code over clever code

Troubleshooting

• Make sure you're pointing to a directory that contains Claude Code projects
• Projects need .git, .mcp.json, or .claude/ folder to be detected

Run with --debug to see what paths are being checked:

ccmanager --debug ~/Projects

The scanner looks for:

• MCP servers: ~/.claude.json → mcpServers key (camelCase!)
• Skills: ~/.claude/skills/*/SKILL.md (each skill needs its own folder)
• Project MCP: .mcp.json → mcpServers key in each project

Common issues:

• Wrong key name (mcp_servers vs mcpServers)
• Skills missing SKILL.md file inside the folder

• Make sure your terminal supports Unicode
• Try a different terminal (iTerm2, Alacritty, Windows Terminal)
• Ensure terminal is at least 100 columns wide

• Tab to focus the detail panel first
• Then press Enter
• Press Escape or 'q' to close the preview

License

MIT License — see LICENSE file.

Acknowledgments

• Built with Textual — the amazing Python TUI framework
• Inspired by the need to understand Claude Code's configuration system
• Thanks to Anthropic for creating Claude Code

Safe Computing Reminder: Always review code from the internet before running it. This tool only reads your configuration files — it doesn't modify anything without your explicit action.