Skip to content
Back to search

claude-code-tool-manager

GUI app to manage MCP servers for Claude Code

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tylergraydev--claude-code-tool-manager/badge.svg)](/listings/tylergraydev--claude-code-tool-manager)

HTML

<a href="/listings/tylergraydev--claude-code-tool-manager"><img src="/api/listings/tylergraydev--claude-code-tool-manager/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

macOS (Homebrew)

brew tap tylergraydev/cctm
brew install --cask claude-code-tool-manager

Direct Download

Download from [Releases](https://github.com/tylergraydev/claude-code-tool-manager/releases):

| Platform | Download | |----------|----------| | Windows | `.msi` or `.exe` | | macOS | `.dmg` (Intel & Apple Silicon) | | Linux | `.AppImage` or `.deb` |

<details> <summary><strong>Build from source</strong></summary>

Requires [Node.js](https://nodejs.org/) 18+, [Rust](https://www.rust-lang.org/tools/install) 1.70+, and [Tauri prerequisites](https://tauri.app/start/prerequisites/).

git clone https://github.com/tylergraydev/claude-code-tool-manager.git
cd claude-code-tool-manager
npm install
npm run tauri build

Output: `src-tauri/target/release/bundle/`

</details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 159 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Claude Code Tool Manager
  2. [![Build Status](https://github.com/tylergraydev/claude-code-tool-manager/actions/workflows/build.yml/badge.svg)](https://github.com/tylergraydev/claude-code-tool-manager/actions/workflows/build.yml)
  3. [![Release](https://img.shields.io/github/v/release/tylergraydev/claude-code-tool-manager)](https://github.com/tylergraydev/claude-code-tool-manager/releases/latest)
  4. [![Downloads](https://img.shields.io/github/downloads/tylergraydev/claude-code-tool-manager/total)](https://github.com/tylergraydev/claude-code-tool-manager/releases)
  5. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
  6. A desktop app for managing MCP servers, Commands, Skills, Sub-Agents, and Hooks across multiple AI coding assistants.
  7. ### Supported Editors
  8. | Editor | Config Location | Format |
  9. |--------|-----------------|--------|
  10. | [Claude Code](https://docs.anthropic.com/en/docs/claude-code) | `~/.claude.json` | JSON |
  11. | [OpenCode](https://opencode.ai) | `~/.config/opencode/opencode.json` | JSON |
  12. | [Codex CLI](https://github.com/openai/codex) | `~/.codex/config.toml` | TOML |
  13. | [GitHub Copilot CLI](https://githubnext.com/projects/copilot-cli) | `~/.copilot/mcp-config.json` | JSON |
  14. | [Cursor](https://cursor.com) | `~/.cursor/mcp.json` | JSON |
  15. | [Gemini CLI](https://github.com/google-gemini/gemini-cli) | `~/.gemini/settings.json` | JSON |
  16. Enable the editors you use in Settings, and your MCP configurations will sync to all of them automatically.
  17. ![Claude Code Tool Manager](imgs/project-assign.gif)
  18. ## The Problem
  19. Claude Code configuration is scattered across your filesystem—`~/.claude.json`, `~/.claude/commands/`, project-level configs—and managing it means hand-editing JSON and markdown files.
  20. **Claude Code Tool Manager** gives you a single visual interface to see everything, quickly toggle tools on/off per project, and import configs by pasting JSON or CLI commands.
  21. ## Features
  22. **MCP Testing** — Connect to any MCP server and execute its tools directly from the app. Validate your configurations actually work before assigning them to projects.
  23. ![MCP Testing](imgs/mcp-testing-12s.gif)
  24. **AI-Controllable** — Ships with its own MCP server, so Claude Code (or any MCP client) can manage your tool configurations programmatically. Ask Claude to "add this MCP to my project" and it just works.
  25. **MCP Servers** — Create, edit, and organize MCP configurations. Supports stdio, HTTP, and SSE transports. Import by pasting JSON or `claude mcp add` commands.
  26. **Commands** — Create and manage slash commands (invoked via `/command-name`). Stored as single markdown files in `.claude/commands/`.
  27. **Skills** — Build agent skills that Claude can invoke automatically based on context. Stored as directories with `SKILL.md` and supporting files in `.claude/skills/`.
  28. **Sub-Agents** — Define custom sub-agents with specialized capabilities. Auto-discovers from `~/.claude/agents/`.
  29. **Hooks** — Create and manage Claude Code hooks that run on events like task completion, notifications, and tool use. Includes a sound notification wizard to play sounds when Claude needs your attention or finishes a task.
  30. **Profiles** — Save and restore named configurations of your globally-enabled MCPs, skills, subagents, commands, and hooks. Snapshot your current setup, then switch between "Work" and "Personal" configurations with one click.
  31. **Status Line Builder** — Design custom terminal status lines for Claude Code with a visual builder. Choose from 25+ segment types (model, cost, context window, git branch, vim mode, token counts, usage stats, and more), apply Powerline themes, or browse and install premade status lines from the community gallery.
  32. **Spinner Verbs** — Customize the action verbs shown in the Claude Code spinner while it works (e.g., "Pondering", "Crafting", "Scheming"). Add, edit, delete, and reorder verbs with drag-and-drop, toggle individual verbs on/off, and choose between append or replace mode. Syncs directly to `~/.claude/settings.json`.
  33. **Projects** — Scan for existing projects, assign tools globally or per-project, and keep everything in sync with Claude's config files. Search and filter to quickly find projects and available tools.
  34. **Usage Analytics** — Visualize your Claude Code usage patterns with interactive charts: daily activity, model usage breakdown with donut charts, daily token consumption by model, peak hours heatmap, and estimated API costs. Reads directly from `~/.claude/stats-cache.json`.
  35. **Insights Viewer** — View Claude's session quality reports and friction analysis. Displays the HTML insights report and session facets with outcome tracking, helpfulness ratings, and friction trend charts. Reads from `~/.claude/usage-data/`.
  36. **Session Explorer** — Browse individual Claude Code sessions per project. Drill into session transcripts with conversation timelines showing role badges, tool call tags, and per-message token usage. Includes project comparison cards, sortable session tables, tool frequency charts, and estimated API cost per session. Parses JSONL files from `~/.claude/projects/`.
  37. ## Installation
  38. ### macOS (Homebrew)
  39. ```bash
  40. brew tap tylergraydev/cctm
  41. brew install --cask claude-code-tool-manager
  42. ```
  43. ### Direct Download
  44. Download from [Releases](https://github.com/tylergraydev/claude-code-tool-manager/releases):
  45. | Platform | Download |
  46. |----------|----------|
  47. | Windows | `.msi` or `.exe` |
  48. | macOS | `.dmg` (Intel & Apple Silicon) |
  49. | Linux | `.AppImage` or `.deb` |
  50. <details>
  51. <summary><strong>Build from source</strong></summary>
  52. Requires [Node.js](https://nodejs.org/) 18+, [Rust](https://www.rust-lang.org/tools/install) 1.70+, and [Tauri prerequisites](https://tauri.app/start/prerequisites/).
  53. ```bash
  54. git clone https://github.com/tylergraydev/claude-code-tool-manager.git
  55. cd claude-code-tool-manager
  56. npm install
  57. npm run tauri build
  58. ```
  59. Output: `src-tauri/target/release/bundle/`
  60. </details>
  61. ## Quick Start
  62. 1. **Scan** — Click "Scan for MCPs" to detect existing configurations
  63. 2. **Add** — Go to MCP Library → Add MCP (or paste a config)
  64. 3. **Assign** — Open a project and toggle the tools you need
  65. ### Importing MCPs
  66. Paste JSON:
  67. ```json
  68. {
  69. "mcpServers": {
  70. "filesystem": {
  71. "command": "npx",
  72. "args": ["-y", "@modelcontextprotocol/server-filesystem", "~/Documents"]
  73. }
  74. }
  75. }
  76. ```
  77. Or paste a CLI command:
  78. ```
  79. claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem ~/Documents
  80. ```
  81. ## Configuration Locations
  82. | Scope | MCPs | Commands | Skills | Sub-Agents | Hooks |
  83. |-------|------|----------|--------|------------|-------|
  84. | Global | `~/.claude.json` | `~/.claude/commands/` | `~/.claude/skills/` | `~/.claude/agents/` | `~/.claude/settings.json` |
  85. | Project | `.claude/.mcp.json` | `.claude/commands/` | `.claude/skills/` | `.claude/agents/` | `.claude/settings.json` |
  86. ## Multi-Editor Sync
  87. When you enable multiple editors in Settings:
  88. - **Global MCPs** sync to each editor's global config file
  89. - **Project MCPs** sync to project-level configs (e.g., `.cursor/mcp.json`, `.gemini/settings.json`)
  90. - **Detection** finds installed editors via PATH or app bundles
  91. This means you can manage your MCP configurations once and have them available in Claude Code, Cursor, Gemini CLI, and more simultaneously.
  92. ## Development
  93. ```bash
  94. npm install # Install dependencies
  95. npm run tauri dev # Development mode
  96. npm test # Run tests
  97. npm run tauri build # Production build
  98. ```
  99. ## Tech Stack
  100. Svelte 5 + SvelteKit • Tauri 2 + Rust • SQLite • Tailwind CSS v4
  101. ## Contributing
  102. PRs welcome! Fork → branch → commit → PR.
  103. ## License
  104. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.