Nisarg-Shah2302/mcp-daily-change-log
If you are the rightful owner of mcp-daily-change-log and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The Model Context Protocol (MCP) server is a professional tool designed to manage daily change logs with features like automatic formatting, intelligent monitoring, and client-ready output.
log_my_work
Automatically generate and log a professional summary of recent development work.
generate_daily_summary
Generate a comprehensive end-of-day summary of all development activities.
analyze_conversation
Analyze user prompts and AI responses to track development progress.
get_monitoring_status
Get the current status of the intelligent monitoring system.
add_daily_log_entry
Manually add a professional entry to the daily change log.
view_recent_entries
View recent changelog entries.
MCP Daily Change Log
A professional Model Context Protocol (MCP) server for managing daily change logs with automatic formatting, intelligent monitoring, and client-ready output. This tool helps developers document their work, track development activities, and generate professional reports.
๐ Features
- Professional Formatting: Automatically converts casual language to professional client-ready format
- Intelligent Monitoring: Real-time tracking of development activities and conversations
- Zero-Friction Entry: Direct input processing without confirmation prompts
- Multiple Input Methods: MCP tools, direct-add script, and command-line interface
- Report Generation: Daily summaries and comprehensive reports
- Category Management: Predefined professional categories for organization
- Tag Support: Flexible tagging system for better organization
- Clean Architecture: Optimized codebase with essential files only (recently cleaned up)
๐ Installation
Prerequisites
- Node.js (version 18 or higher)
- npm (comes with Node.js)
- Claude Desktop (for MCP integration)
Step 1: Clone and Setup
# Clone the repository
git clone https://github.com/yourusername/mcp-daily-change-log.git
cd mcp-daily-change-log
# Install dependencies
npm install
Step 2: Configure MCP Client
Add this configuration to your MCP client configuration file:
For Claude Desktop:
- Linux:
~/.config/claude/claude_desktop_config.json
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"mcp-daily-change-log": {
"command": "node",
"args": ["enhanced-mcp-server.js"],
"cwd": "/path/to/mcp-daily-change-log",
"env": {}
}
}
}
Important: Replace /path/to/mcp-daily-change-log
with the actual absolute path to your project directory.
Step 3: Start MCP Server
# Start the MCP server
npm run mcp-server
Step 4: Restart Claude Desktop
- Completely close Claude Desktop
- Wait 5 seconds
- Restart Claude Desktop
- Check the MCP Tools panel for "mcp-daily-change-log" with green status
๐ Available Commands
MCP Tools (Use in Claude Desktop)
1. log_my_work
Automatically generate and log professional summary of recent development work.
Use: log_my_work
Optional: customHeader - Custom header for the work summary
2. generate_daily_summary
Generate comprehensive end-of-day summary of all development activities.
Use: generate_daily_summary
Optional: finalize (true/false) - Whether to create final polished summary
3. analyze_conversation
Analyze user prompts and AI responses to track development progress.
Use: analyze_conversation
Required: userPrompt - User prompt or command
Optional: aiResponse - AI response or output
Optional: codeChanges - Array of code changes made
4. get_monitoring_status
Get current status of intelligent monitoring system.
Use: get_monitoring_status
Optional: detailed (true/false) - Include detailed activity breakdown
5. add_daily_log_entry
Manually add a professional entry to the daily change log.
Use: add_daily_log_entry
Required: header - Header/title for the log entry
Required: notes - Notes content
Optional: category - Category from predefined list
Optional: tags - Array of tags for the entry
6. view_recent_entries
View recent changelog entries.
Use: view_recent_entries
Optional: days - Number of days to look back (default: 7)
Direct Commands (Terminal)
Direct-Add Script (Recommended Alternative)
# Add an entry with all parameters
node direct-add.js "Header" "Notes" "Category" "tag1,tag2"
# Examples:
node direct-add.js "Bug Fix" "Fixed login issue" "Bug Fixes" "auth,frontend"
node direct-add.js "Feature Implementation" "Added user dashboard" "Feature Implementation" "ui,backend"
node direct-add.js "Daily Summary" "Completed all sprint tasks" "Documentation" "summary,completion"
MCP Server Management
# Start MCP server
npm run mcp-server
# Alternative: Start server directly
node enhanced-mcp-server.js
๐ Available Categories
- Feature Implementation - New features and enhancements
- Bug Fixes - Issue resolution and fixes
- Documentation - Documentation updates and creation
- Refactoring - Code restructuring and optimization
- Testing - Test creation and validation
- DevOps - Deployment and infrastructure
- UI/UX - User interface and experience improvements
- Performance - Optimization and speed improvements
- Security - Security enhancements and fixes
๐ฏ User Activities
Daily Development Workflow
-
Start Your Day
npm run mcp-server
-
Work Normally
- The system automatically tracks your development activities
- Continue coding, testing, and development tasks
-
Log Your Work (Multiple Options)
Option A: Using MCP Tools in Claude Desktop
Use: log_my_work
Option B: Using Direct-Add Script
node direct-add.js "Task Header" "Task description" "Category" "tags"
-
Generate Daily Summary
Use: generate_daily_summary
Professional Entry Creation
Quick Entry
node direct-add.js "Client Meeting" "Discussed project requirements" "Documentation" "client,meeting"
Detailed Entry
node direct-add.js "Authentication System" "โข Implemented JWT authentication\nโข Added password reset functionality\nโข Created user registration flow" "Feature Implementation" "auth,security,backend"
Monitoring and Analysis
Check System Status
Use: get_monitoring_status with detailed=true
Analyze Conversations
Use: analyze_conversation with userPrompt="Implemented new feature" and aiResponse="Feature implemented successfully"
View Recent Work
Use: view_recent_entries with days=7
Report Generation
Daily Reports
Use: generate_daily_summary with finalize=true
Weekly Reports
Use: view_recent_entries with days=7
๐ File Organization
The tool automatically creates and manages:
mcp-daily-change-log/
โโโ change-notes/ # Daily changelog files
โ โโโ 2025-07-15-change-log.md
โ โโโ 2025-07-14-change-log.md
โ โโโ 2025-07-13-change-log.md
โโโ lib/ # Core libraries
โ โโโ dailyLogManager.js # File management & entry creation
โ โโโ intelligentMonitor.js # Real-time activity monitoring
โ โโโ professionalFormatter.js # Professional text formatting
โโโ enhanced-mcp-server.js # Enhanced MCP server v3.0
โโโ direct-add.js # Direct entry script (reliable alternative)
โโโ config.js # Configuration settings
โโโ package.json # Dependencies & scripts
โโโ package-lock.json # Dependency lock file
โโโ README.md # Comprehensive documentation
๐จ Professional Transformations
The tool automatically converts casual language to professional format:
Casual Input | Professional Output |
---|---|
"fixed bug" | "Resolved functionality issue" |
"worked on feature" | "Developed feature implementation" |
"tested stuff" | "Validated system components" |
"client meeting" | "Client Communication Session" |
"code review" | "Code Quality Assessment" |
๐ Sample Output
# Daily Progress Report - 2025-07-15
## Executive Summary
This document outlines the development activities and progress made on 2025-07-15.
---
## Feature Implementation
- Developed user authentication module with JWT integration.
- Implemented password reset functionality with email verification.
- Created comprehensive user registration flow with validation.
**Logged at:** 14:30:22
**Tags:** #auth, #security, #backend
## Bug Fixes
- Resolved login timeout issues affecting user sessions.
- Fixed responsive design problems on mobile devices.
**Logged at:** 16:45:10
**Tags:** #frontend, #mobile, #ui
๐ง Configuration
Edit config.js
to customize:
export default {
// Base directory for change logs
changeLogDir: 'change-notes',
// File format
fileFormat: '{date}-change-log.md',
// Available categories
categories: [
'Feature Implementation',
'Bug Fixes',
'Documentation',
// Add custom categories
],
// Entry template
entryTemplate: '## {header}\n\n{notes}\n\n**Logged at:** {time}\n\n'
};
๐จ Troubleshooting
MCP Server Issues
Problem: "0 tools enabled" in Claude Desktop
Solution:
- Verify configuration file location and content
- Ensure absolute path is correct in configuration
- Restart Claude Desktop completely
- Check Node.js version (18+)
Problem: Server fails to start
Solution:
# Check Node.js version
node --version
# Reinstall dependencies
npm install
# Test server directly
node enhanced-mcp-server.js
File Writing Issues
Problem: Entries not appearing in files
Solution:
# Use direct-add as reliable alternative
node direct-add.js "Test Entry" "Testing file writing" "Testing" "test"
# Check file permissions
ls -la change-notes/
๐ค Integration Examples
With Development Workflow
# After completing a feature
node direct-add.js "User Dashboard" "Completed user dashboard with analytics" "Feature Implementation" "ui,analytics"
# After fixing bugs
node direct-add.js "Bug Resolution" "Fixed authentication timeout issues" "Bug Fixes" "auth,security"
# End of day summary
Use: generate_daily_summary
With Team Collaboration
# Before standup meeting
Use: view_recent_entries with days=1
# For client updates
Use: generate_daily_summary with finalize=true
# For sprint reviews
Use: view_recent_entries with days=7
๐ Best Practices
- Regular Logging: Log work as you complete tasks
- Descriptive Headers: Use clear, professional headers
- Proper Categorization: Use appropriate categories for organization
- Meaningful Tags: Add relevant tags for better filtering
- Daily Summaries: Generate end-of-day summaries for reporting
๐ Security & Privacy
- Local Processing: All data processed locally
- No External Requests: No data sent to external services
- Sensitive Data Protection: Automatic sanitization of passwords/tokens
- Client-Safe Output: Professional format suitable for client presentation
๐ Support
For issues or questions:
- Check the troubleshooting section above
- Verify your installation follows all steps
- Ensure all dependencies are properly installed
- Test with direct-add script as alternative
๐งน Recent Cleanup (2025-07-15)
The codebase has been recently optimized for better maintainability:
- Removed 5 redundant documentation files from
docs/
directory - Eliminated duplicate README files (MCP-README.md merged into main README.md)
- Removed sample configuration files (claude-desktop-config.json)
- Streamlined file structure with only essential files
- Maintained 100% functionality while reducing complexity
- All core features tested and verified after cleanup
The system now has a cleaner, more focused architecture with comprehensive documentation in a single README.md file.
๐ License
MIT License - Feel free to use and modify as needed.
Ready to start professional development logging! ๐