DAZ Command MCP Server
An MCP server that provides session-based shell command execution and file management with intelligent LLM-powered summarization. It enables users to manage isolated workflows and track progress through automated event logging and session history.
README
DAZ Command MCP Server

A Model Context Protocol (MCP) server that provides session-based command execution with intelligent LLM-powered summarization.
🚀 Features
- 🔧 Session Management: Create, open, and manage isolated command execution sessions
- ⚡ Command Execution: Run shell commands with timeout controls and working directory management
- 📁 File Operations: Read and write text files with comprehensive error handling
- 🤖 LLM Summarization: Automatic session progress tracking using structured LLM responses
- 📋 Event Logging: Complete audit trail of all operations within sessions
- 🔒 Thread-Safe: Robust concurrent operation with proper synchronization
📦 Installation
Prerequisites
- Python 3.8+
fastmcplibrarydazllmlibrary for LLM integration
Quick Setup
- Clone this repository:
git clone https://github.com/yourusername/daz-command-mcp.git
cd daz-command-mcp
- Install dependencies:
pip install -r requirements.txt
- Configure your LLM model in the script (default:
lm-studio:openai/gpt-oss-20b)
🎯 Usage
Starting the Server
python main.py
Available Tools
Session Management
daz_sessions_list()- List all sessions and identify the active onedaz_session_create(name, description)- Create and activate a new sessiondaz_session_open(session_id)- Open and activate an existing sessiondaz_session_current()- Get details of the currently active sessiondaz_session_close()- Close the current sessiondaz_session_rename(old_name, new_name)- Rename an existing sessiondaz_session_delete(session_name)- Delete a session by moving to deleted_sessions
Command & File Operations
All command and file operations require an active session and context parameters:
daz_command_cd(directory, current_task, summary_of_what_we_just_did, summary_of_what_we_about_to_do)- Change working directorydaz_command_read(file_path, current_task, summary_of_what_we_just_did, summary_of_what_we_about_to_do)- Read a text filedaz_command_write(file_path, content, current_task, summary_of_what_we_just_did, summary_of_what_we_about_to_do)- Write a text filedaz_command_run(command, current_task, summary_of_what_we_just_did, summary_of_what_we_about_to_do, timeout=60)- Execute shell commands
Learning & Instructions
daz_add_learnings(learning_info)- Add important discoveries and context to the sessiondaz_instructions_read()- Read current session instructionsdaz_instructions_add(instruction)- Add a new instruction to the sessiondaz_instructions_replace(instructions)- Replace all instructions with a new listdaz_record_user_request(user_request)- Record a user request at the start of multi-step tasks
Example Workflow
# Create a new session
daz_session_create("Setup Project", "Setting up a new Python project with dependencies")
# Navigate to project directory
daz_command_cd("/path/to/project",
"Setting up Python project",
"Created new session for project setup",
"Navigate to project root directory")
# Run commands
daz_command_run("pip install -r requirements.txt",
"Setting up Python project",
"Navigated to project directory",
"Install project dependencies")
# Read configuration
daz_command_read("config.json",
"Setting up Python project",
"Installed dependencies successfully",
"Review current configuration settings")
# Write new file
daz_command_write("setup.py", "...",
"Setting up Python project",
"Reviewed configuration file",
"Create package setup file")
🏗️ Architecture
Session Storage
Sessions are stored as JSON files in the sessions/ directory with the following structure:
{
"id": "unique-session-id",
"name": "Session Name",
"description": "Detailed description",
"created_at": 1692123456.789,
"updated_at": 1692123456.789,
"summary": "LLM-generated summary",
"progress": "Current progress status",
"current_directory": "/current/working/dir",
"events_count": 42
}
Event Logging
Every operation is logged with comprehensive details in event_log.jsonl:
{
"timestamp": 1692123456.789,
"type": "run|read|write|cd|user_request|learning",
"current_task": "The task being worked on",
"summary_of_what_we_just_did": "What was just completed",
"summary_of_what_we_about_to_do": "What's planned next",
"inputs": {...},
"outputs": {...},
"duration": 0.123
}
LLM Integration
The server uses asynchronous LLM processing to maintain session summaries:
- 🔄 Background Processing: Summarization runs in a separate thread
- 🛡️ Fault Tolerance: LLM failures don't affect MCP operations
- 📋 Structured Output: Uses Pydantic models for reliable parsing
- ⚙️ Configurable Model: Easy to switch between different LLM providers
⚙️ Configuration
LLM Model
Edit the LLM_MODEL_NAME constant in src/models.py:
LLM_MODEL_NAME = "your-model-name"
Session Directory
Sessions are stored in ./sessions/ by default. This can be modified by changing the SESSIONS_DIR constant in src/models.py.
🛠️ Error Handling
- 🔄 Graceful Degradation: Operations continue even if LLM summarization fails
- 📝 Comprehensive Logging: All errors are logged to stderr
- ✅ Input Validation: Robust parameter checking and sanitization
- 🔒 File Safety: Atomic file operations prevent corruption
🔗 Integration
This MCP server integrates with Claude Desktop and other MCP-compatible clients. Add it to your MCP configuration:
{
"mcpServers": {
"daz-command": {
"command": "python",
"args": ["/path/to/main.py"]
}
}
}
📁 Project Structure
daz-command-mcp/
├── README.md # This file
├── main.py # Entry point
├── requirements.txt # Dependencies
├── images/ # Documentation images
├── sessions/ # Session storage (auto-created)
└── src/ # Source code
├── __init__.py
├── command_executor.py # Command execution logic
├── history_manager.py # Session history management
├── mcp_tools.py # MCP tool definitions
├── models.py # Data models and constants
├── session_manager.py # Session lifecycle management
├── summary_generator.py # LLM summary generation
├── summary_worker.py # Background summarization worker
├── utils.py # Utility functions
└── tests/ # Unit tests
├── test_add_learnings.py
├── test_initialization_fix.py
├── test_llm_system_integration.py
├── test_new_parameter_system.py
└── test_summary_generation.py
🧪 Testing
Run the comprehensive test suite:
# Run all tests
python -m pytest src/tests/
# Run specific test
python -m pytest src/tests/test_summary_generation.py -v
# Run with coverage
python -m pytest src/tests/ --cov=src
🤝 Contributing
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Add tests if applicable
- Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Submit a pull request
📜 License
[Add your license here]
📦 Dependencies
- fastmcp: MCP server framework
- dazllm: LLM integration library
💬 Support
For issues and questions, please open an issue on GitHub or contact [your contact information].
Built with ❤️ for the Model Context Protocol ecosystem
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。