Dev Log MCP Component

A Model Context Protocol (MCP) component that manages a development log file. It provides endpoints for reading recent log entries and appending new entries with automatic timestamps.

Features

- Read last X entries from dev_log.md
- Append new entries with automatic timestamps and proper spacing
- Automatic dependency management
- Background process management with logging

Files

- mcp_server.py - Flask implementation of dev log endpoints
- dev_rules.md - Development guidelines and logging format rules
- dev_log.md - The log file containing timestamped entries
- requirements.txt - Python dependencies
- start_server.sh - Dev log service startup script with dependency installation
- stop_server.sh - Dev log service shutdown script

Installation & Usage

The service handles all dependency installation automatically. Just run:

./start_server.sh

This will:
1. Check and install required system dependencies (Python3, pip)
2. Set up a virtual environment
3. Install Python dependencies
4. Start the dev log service in the background
5. Create a log file at devlog.log

To stop the service:

./stop_server.sh

API Endpoints

Read Log Entries

GET http://localhost:5002/read?lines=10

- lines (optional): Number of recent entries to return (default: 10) - Returns: JSON array of log entries

Write Log Entry

POST http://localhost:5002/write
Content-Type: application/json
{

    "entry": "Your log message here"

}

- Automatically prepends timestamp in format: "YYYY-MM-DD HH:MM:SS"
- Adds proper spacing between entries
- Returns: Success/error status

Monitoring

- Process ID is stored in devlog.pid
- Service output is logged to devlog.log
- Check service status: ps -p $(cat devlog.pid)

Log Format

Each entry in dev_log.md follows this format:

## YYYY-MM-DD HH:MM:SS: Your log message here

Entries are separated by newlines for better readability. See dev_rules.md for detailed logging guidelines.