Claude Code Config 343ee4a4

MCP运维云端

提供方 joeyism

运维云端 stdio · 本地进程 Token 社区 / 第三方 Claude
查看接入方式

一个用于管理Claude Code配置文件的终端用户界面(TUI)应用,提供MCP服务器、项目和对话的层次化管理功能。

一句话选型结论

按资料字段整理

Claude Code Config 343ee4a4 属于运维云端类 MCP 服务器,stdio · 本地进程,Token,可直接接入 Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 21 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

配置管理Python本地部署终端界面JSON编辑器对话管理MCP服务器

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
pip install claude-code-config

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Claude Code Config 343ee4a4当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方joeyism上游标注的维护方 joeyism
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

14.7 KB
来自项目仓库与上游目录的原文,未做删改

Claude Code Config

A modern Terminal User Interface (TUI) application for managing Claude Code configuration files (~/.claude.json). Simplify the management of MCP servers, projects, and conversations with an intuitive hierarchical interface.

Features

MCP Server Management

  • Hierarchical View: Browse global and project-level MCP servers in a tree structure
  • Add, Edit, Delete: Full CRUD operations for MCP server configurations
  • Copy Servers: Quickly duplicate server configurations with visual clipboard tracking
  • Move Servers: Move servers between global scope and projects
  • Multi-Scope Support: Manage both global and project-specific servers
  • Sensitive Value Masking: API keys and secrets masked by default (press V to toggle)

Project & Conversation Management

  • Project Browser: View all your Claude Code projects with server, conversation, and history counts
  • Real Conversation Management: Browse, view details, and delete actual .jsonl conversation files from filesystem
  • Conversation Statistics: See message count, file size, and age for each conversation
  • Conversation Cleanup: Delete old conversations with full metadata visibility
  • History Management: View, delete, and move history items between projects
  • Project Organization: See which MCP servers are configured for each project

Safety & Reliability

  • Automatic Backups: Creates timestamped backups before every save
  • Undo/Redo System: Full undo/redo support with Ctrl+Z/Ctrl+Y (up to 50 actions)
  • JSON Validation: Ensures your configuration remains valid
  • Rollback Support: Easily restore from backups if needed
  • Non-destructive Operations: Confirm before deleting
  • Error Logging: Persistent error log with export capability (press l to view)

Advanced Features

  • Environment Variable Support: Handle ${VAR} syntax in server configs
  • HTTP/SSE Servers: Support for stdio, HTTP, and SSE server types with headers support
  • Large File Handling: Efficiently manages large config files (handles multi-MB files)
  • Visual Navigation: Intuitive tree-based navigation with focus management
  • Visual Change Indicators: See unsaved changes with * in title bar and orange save button
  • Enhanced Clipboard: Copy/paste servers and history with visual status tracking

Installation

From PyPI```bash

pip install claude-code-config


### From Source```bash
git clone https://github.com/joeyism/claude-code-config.git
cd claude-code-config
pip install -e .

Usage

Launch the TUI application:```bash
claude-config

or use the short alias

ccm


### Keyboard Shortcuts

#### Navigation
- `↑/↓` or `j/k`: Navigate tree
- `Enter` or `Space`: Expand/collapse tree nodes
- `Right/Left`: Expand/collapse nodes

#### Actions
- `a`: Add new MCP server or history item
- `e`: Edit selected server or history item
- `d`: Delete selected item (servers, conversations, or history)
- `c`: Copy selected server or history item to clipboard
- `p`: Paste from clipboard
- `m`: Move server or history item to different project
- `v`: View pasted content details

#### File Operations
- `s`: Save changes
- `r`: Reload from disk
- `q` or `Ctrl+C`: Quit (with confirmation if unsaved changes)

#### Advanced Features
- `V`: Toggle sensitive value masking (show/hide secrets)
- `Ctrl+Z`: Undo last action
- `Ctrl+Y`: Redo action
- `u`: View undo/redo history
- `l`: View error log
- `x`: Clear clipboard
- `?`: Show help

## Configuration File Structure

The tool manages `~/.claude.json`, which contains:

- **mcpServers**: Global MCP (Model Context Protocol) server configurations
- **projects**: Project-specific settings, including:
  - **mcpServers**: Project-level MCP server configurations
  - **conversations**: Conversation history for each project (note: actual conversations are `.jsonl` files in `~/.claude/projects/`)
  - **history**: User input history for quick access
  - Various project-specific settings
- **other settings**: Various Claude Code settings (preserved)

### Hierarchical Structure```
Claude Configuration
├── Global Servers (1)
│   └── 📡 terraform-cloud-mcp
└── Projects
    ├── 📁 delorean (3s, 15c, 14h)
    │   ├── MCP Servers (3)
    │   │   ├── 📡 mcp_server_mysql
    │   │   ├── 📡 replicate_server
    │   │   └── 📡 bigquery
    │   ├── Conversations (15)
    │   │   └── 💬 Implement user auth (4 days ago)
    │   └── History (14)
    │       └── 📝 ...
    └── 📁 web (2s, 8c, 20h)
        └── ...

MCP Server Format

Stdio Server:```json
{
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-example"],
"env": {
"API_KEY": "${API_KEY}"
}
}


**HTTP Server:**```json
{
  "type": "http",
  "url": "https://api.example.com/mcp",
  "headers": {
    "Authorization": "Bearer ${API_TOKEN}"
  }
}

Development

Setup Development Environment```bash

Clone the repository

git clone https://github.com/joeyism/claude-code-config.git
cd claude-code-config

Install with development dependencies

pip install -e ".[dev]"


### Running Tests```bash
# Run full test suite
pytest tests/

# Or run quick validation tests
python test_phase1_simple.py

Code Formatting```bash

black claude_code_config/
ruff check claude_code_config/


## Why Use Claude Code Config?

The `~/.claude.json` file can grow to several megabytes with hundreds of projects and servers. Manual editing becomes:
- **Error-prone**: Easy to break JSON syntax
- **Difficult**: Hard to find specific servers across projects
- **Risky**: No automatic backups
- **Time-consuming**: Navigating large nested structures

Claude Code Config solves these problems with:
- Visual tree navigation
- Safe editing with validation and undo/redo
- Automatic backups
- Quick search and filtering
- Conversation management with file size tracking

## Common Use Cases

1. **Clean up old conversations**: Free up space by deleting conversations (with file size info and total statistics)
2. **Manage history items**: View, delete, or move history entries between projects (with undo support)
3. **Organize MCP servers**: Move servers between global and project scopes
4. **Copy server configs**: Duplicate working configurations for new projects (with clipboard tracking)
5. **Audit server usage**: See which projects use which MCP servers
6. **Safely edit configs**: Make changes with undo/redo safety net
7. **Protect secrets**: Browse configs without exposing API keys (automatic masking feature)
8. **Track conversation growth**: Monitor conversation file sizes and clean up large old conversations

## Recent Enhancements (January 2026)

### Phase 1: UX Improvements

**Undo/Redo System**
- Full undo/redo functionality with `Ctrl+Z` (undo) and `Ctrl+Y` (redo)
- Stores up to 50 previous states with automatic snapshots before destructive operations
- View undo/redo history with `u` key
- Smart clearing after save/reload
- Provides safety net for accidental changes

**Visual Indicators for Changes**
- Title bar shows `*` when configuration is modified
- Subtitle displays "⚠ Unsaved changes" when there are unsaved modifications
- Save button changes from green to orange and shows `*` when changes are present
- Automatic updates after any modification
- Clear visual feedback prevents accidental data loss

**Enhanced Clipboard**
- Status bar at top shows clipboard contents: servers or history items
- Visual feedback with icons (📋) and colored messages
- New `x` shortcut to quickly clear clipboard
- Shows detailed summary: "Server 'name' · Env: 2 vars · Headers: 1 items"
- Type-aware clipboard distinguishes between servers and history items

**Persistent Error Log**
- Press `l` to view comprehensive error log
- Stores last 100 errors with full details (message, traceback, context)
- Features: browse errors, export to file, clear log, filter by severity
- Enhanced notifications with 15-second timeout include error log hint
- Helps troubleshoot issues without losing error information

**Improved Dialogs**
- Move server dialog now consistent with move history dialog
- Clear target selection interface
- Better user experience for moving items between projects

**New Keyboard Shortcuts:**
- `Ctrl+Z`: Undo last action
- `Ctrl+Y`: Redo
- `u`: View undo/redo history
- `l`: View error log
- `x`: Clear clipboard

**Files Added:**
- `claude_code_config/undo.py`: Undo/redo manager implementation
- `claude_code_config/error_log.py`: Error logging system
- `tests/test_phase1.py`: Comprehensive test suite

### Real Conversation Management

**The Discovery**
The tool originally looked for conversations in `~/.claude.json` under `projects[path].conversations`, but this field is always empty. Claude Code actually stores conversations as `.jsonl` files in `~/.claude/projects//`. Many users had hundreds of conversations but couldn't see or manage them!

**Solution Implemented:**

1. **ConversationFile Model** (`conversations.py`)
   - Parses `.jsonl` conversation files from filesystem
   - Extracts rich metadata: title (from first user message), creation date, message count, file size
   - Provides human-readable formatters for age ("4 days ago") and size (KB/MB)
   - Supports deletion of actual conversation files

2. **ConversationScanner** (`conversations.py`)
   - Automatically scans `~/.claude/projects/` directory on startup
   - Groups conversations by project for organized display
   - Provides statistics: total conversations, projects, cumulative size
   - Efficient scanning: only reads first 50 lines for metadata extraction
   - Performance optimized for large conversation files

3. **Enhanced ConfigManager** (`config.py`)
   - Integrated ConversationScanner for real-time filesystem scanning
   - New method: `get_conversations(project_path)` - retrieve conversations for specific project
   - New method: `get_all_conversations()` - get all conversations grouped by project
   - New method: `get_conversation_stats()` - get comprehensive statistics

4. **Updated TUI** (`tui.py`)
   - Loads real conversations from filesystem instead of config file
   - Tree display shows conversation title and age: "💬 Implement user auth (4 days ago)"
   - Detail panel shows comprehensive metadata:
     - Full title
     - Conversation ID
     - Message count
     - File size in KB/MB
     - Human-readable age
     - Full file path location
   - Delete functionality now removes actual `.jsonl` files from disk
   - Displays up to 50 conversations per project for UI performance

**Usage:**

View conversations:
1. Launch `claude-config`
2. Navigate to any project in the tree
3. Expand project node to see "Conversations (N)"
4. Expand to see all conversations with titles and ages
5. Select a conversation to see full details in right panel

Delete old conversations:
1. Select a conversation from the tree
2. Press `d` to delete
3. Confirm deletion in dialog (shows conversation title)
4. The `.jsonl` file is permanently removed from filesystem

**Example Statistics:**
- Testing revealed 302 conversations across 12 projects
- Total size: 30.85 MB of conversation data
- Top project: `python-movie-maker` with 86 conversations

**Technical Details:**
- File format: `~/.claude/projects//.jsonl`
- Each line in file is a JSON object (one message per line)
- Performance: Only first 50 lines read for metadata
- Display limit: 50 conversations per project shown in UI

### Security: Sensitive Value Masking

**The Problem**
When browsing MCP servers, sensitive values like API keys, tokens, and secrets were visible in plain text in environment variables and headers. This posed security risks from shoulder surfing, accidental screenshots, screen sharing, and clipboard status exposure.

**Solution:**

**Default Masking**
- All environment variable and header values are masked by default for security
- Shows `****` instead of actual values in detail panel
- Applies automatically to both global and project-scoped servers
- Masking resets to enabled state on each app launch (session-based security)

**Toggle Visibility**
- Press `V` (capital V) to temporarily toggle masking on/off
- Visual notification appears: "🔒 Sensitive values masked" or "👁 Sensitive values visible"
- State persists during session but resets to masked on app restart
- Allows revealing values when needed without compromising default security

**Masked Display Example:**```
Environment Variables:
  API_KEY = ****
  SECRET_TOKEN = ****

Headers:
  Authorization = ****
  CONTEXT7_API_KEY = ****

Press 'e' to edit | [*****] (V to toggle)

Unmasked Display (after pressing V):```
Environment Variables:
API_KEY = sk-1234567890abcdef...
SECRET_TOKEN = token123...

Headers:
Authorization = Bearer xyz123...
CONTEXT7_API_KEY = ctx7sk-abc...

Press 'e' to edit | [SHOWN] (V to toggle)
```

Protected Clipboard
- Clipboard status bar shows summary instead of actual values
- Example: 📋 Clipboard: Server 'context7' · Env: 2 vars · Headers: 1 items
- No sensitive data exposed in status bar even when copied
- Protects against accidental exposure during screen sharing

Visual Indicators
- [*****] indicator shown when values are masked (default)
- [SHOWN] indicator appears when values are visible
- Indicator appears in detail panel with toggle instructions
- Color-coded notifications (info for masked, warning for visible)

Edit Form Behavior
- When editing server (press e), form always shows real unmasked values
- Necessary for editing and saving configuration changes
- Only browsing view uses masking for security
- Edit form operates independently with full access to values

Security Benefits:
- Default secure posture (masked on startup)
- Prevents shoulder surfing and unauthorized viewing
- Safe for screenshots and screen recordings
- Protected during demos and screen sharing sessions
- Session-based: automatically resets to secure state

Implementation:
- 7 locations modified in tui.py
- ~40 lines added for complete masking system
- Performance impact: Negligible (<1ms per operation)
- Files modified: claude_code_config/tui.py

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/AmazingFeature)
  3. Commit your changes (git commit -m &#x27;Add some AmazingFeature&#x27;)
  4. Push to the branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

  • Built with Textual - a modern TUI framework for Python
  • Designed for use with Claude Code by Anthropic
  • Inspired by the need for better configuration management tools for complex JSON files

Support

If you encounter any issues or have suggestions, please open an issue on GitHub.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Claude Code Config 343ee4a4 怎么安装?

在客户端按下面的安装命令接入:pip install claude-code-config。装完在客户端配置里引用同一个包或端点。

Claude Code Config 343ee4a4 怎么在 Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Claude Code Config 343ee4a4 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Claude Code Config 343ee4a4 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Claude Code Config 343ee4a4 支持哪些客户端?

资料标注支持 Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Claude Code Config 343ee4a4 能提供哪些能力?

资料显示能力标签包括 配置管理、对话管理、Python、Claude。具体工具清单以官方文档为准。

Claude Code Config 343ee4a4 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Claude Code Config 343ee4a4 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。