/ 디렉터리 / 플레이그라운드 / claude-code-organizer
● 커뮤니티 mcpware ⚡ 바로 사용

claude-code-organizer

제작: mcpware · mcpware/claude-code-organizer

Audit Claude Code memories, MCPs, and skills in a dashboard — plus a scanner that catches tool-poisoning attempts.

claude-code-organizer by mcpware is a local dashboard + MCP scanner. It shows exactly what Claude Code loads into context (with per-item token counts), flags MCP servers with suspicious or obfuscated tool descriptions, and helps clean duplicate configs across project and global scopes.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

claude-code-organizer.replay ▶ 준비됨
0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "claude-code-organizer": {
      "command": "npx",
      "args": [
        "-y",
        "claude-code-organizer"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "claude-code-organizer": {
      "command": "npx",
      "args": [
        "-y",
        "claude-code-organizer"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "claude-code-organizer": {
      "command": "npx",
      "args": [
        "-y",
        "claude-code-organizer"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "claude-code-organizer": {
      "command": "npx",
      "args": [
        "-y",
        "claude-code-organizer"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "claude-code-organizer",
      "command": "npx",
      "args": [
        "-y",
        "claude-code-organizer"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json
{
  "context_servers": {
    "claude-code-organizer": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "claude-code-organizer"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add claude-code-organizer -- npx -y claude-code-organizer

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: claude-code-organizer

Audit what's preloaded into every Claude Code session

👤 Power users whose context starts half-full before they type ⏱ ~15 min beginner

언제 쓸까: Responses feel slow or context fills fast and you suspect too many memories/skills.

사전 조건
  • Claude Code installed with existing memories/MCPs — Standard CC setup
흐름
  1. Launch the dashboard
    Run npx @mcpware/claude-code-organizer and open the dashboard.✓ 복사됨
    → Browser opens with all scopes visible
  2. Sort by token cost
    In the dashboard, sort memories/skills by token count — what are the top 5 biggest?✓ 복사됨
    → Clear top-offender list
  3. Prune ruthlessly
    Delete or move to project scope the ones that aren't global concerns.✓ 복사됨
    → Token budget drops

결과: Smaller preloaded context, faster sessions, lower per-call cost.

함정
  • Deleting a memory that a teammate relies on — If it's team-wide, move to project scope rather than delete

Scan your MCP servers for tool-poisoning attempts

👤 Anyone installing community MCPs ⏱ ~10 min intermediate

언제 쓸까: Before or after installing an MCP from an unfamiliar publisher.

흐름
  1. Run the scanner
    Scan all configured MCP servers for suspicious patterns in tool descriptions.✓ 복사됨
    → Report with NEW/CHANGED/CLEAN per server
  2. Investigate flags
    For every flagged finding, show the exact tool description and which pattern fired.✓ 복사됨
    → Explanations linking pattern → evidence
  3. Disable or remove bad actors
    Disable the flagged MCP from project scope and re-scan.✓ 복사됨
    → Clean second run

결과: MCPs that try to smuggle instructions via tool descriptions are caught before they compromise a session.

함정
  • False positives on legitimate servers using unusual language — Review the pattern match; false positives don't hurt, but re-enable after verifying
  • Scanner only catches embedded-prompt-style attacks, not all malicious behavior — Still review source for MCPs that execute code on your box

Deduplicate MCP configs across global and project scopes

👤 Developers with layered .mcp.json + ~/.claude configs ⏱ ~5 min beginner

언제 쓸까: Same MCP registered twice in different scopes causing odd behavior.

흐름
  1. Detect duplicates
    Find MCP servers registered in multiple scopes.✓ 복사됨
    → List of duplicates with their scopes
  2. Consolidate
    Keep the project-scope definition; remove from global.✓ 복사됨
    → Single canonical entry

결과: A cleaner, lower-confusion config.

조합

다른 MCP와 조합해 10배 효율

claude-code-organizer + jetski

Organizer audits your local config; Jetski audits server-side usage

After organizer trimmed memories, check Jetski's analytics for any drop in tool-call failures.✓ 복사됨
claude-code-organizer + marm-systems

Move long-lived memory from CC memories into a proper memory MCP

Find memories in CC that are just factual project notes; propose moving them into MARM-Systems via marm_contextual_log.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
list_scopes (none) Full audit free
scan_mcps (none) or target server After adding any MCP, or periodically free (connects to each MCP briefly)
token_report scope? Before pruning free
dedupe (none) Config hygiene free

비용 및 제한

운영 비용

API 쿼터
None
호출당 토큰
Reports: 500-3000 tokens
금액
Free
Run the scanner after every new MCP install — it's the cheapest defense.

보안

권한, 시크릿, 파급범위

자격 증명 저장: Reads your CC config files; doesn't transmit
데이터 외부 송신: Local dashboard only; connects to MCP servers only to read tool definitions

문제 해결

자주 발생하는 오류와 해결

Dashboard port in use

Kill the previous instance or set a different port via env.

확인: lsof -i :<port>
Scanner can't reach a stdio MCP

The scanner spawns the same command your client does; make sure the command works from terminal.

확인: Run the MCP command manually
False positive on an MCP you trust

Review the match, add it to an allowlist in organizer settings if it's clearly benign.

확인: Re-run scan with allowlist

대안

claude-code-organizer 다른 것과 비교

대안언제 쓰나단점/장점
JetskiYou want server-side analytics and auth, not local config cleanupDifferent concern — runtime vs setup
Manual grep through ~/.claudeYou enjoy painNo scanner, no UI

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기