Dev Log MCP Component

What is Dev Log MCP Component?

An MCP server that manages a development log file (dev_log.md). It provides API endpoints to read recent log entries and append new entries with automatic timestamps. Designed for developers who want to keep a chronological record of their work.

How to use Dev Log MCP Component?

Run ./start_server.sh to automatically install dependencies, set up a virtual environment, and start the Flask service on port 5002. Use the /read endpoint to fetch recent entries and the /write endpoint to add new entries. Stop the service with ./stop_server.sh.

Key features of Dev Log MCP Component

• Read last X entries from dev_log.md via GET /read
• Append new entries with automatic timestamps via POST /write
• Automatic dependency management (Python3, pip, virtualenv)
• Background process management with PID file (devlog.pid)
• Service output logging to devlog.log

Use cases of Dev Log MCP Component

• Keeping a timestamped log of daily development activities
• Automating logging from CI/CD pipelines or scripts
• Viewing recent changes in a project without opening a file
• Maintaining a shared log for team collaboration

FAQ from Dev Log MCP Component

What dependencies does the server require?

Python3, pip, and a virtual environment are automatically installed and configured by start_server.sh. All Python dependencies are listed in requirements.txt.

How do I check if the service is running?

Run ps -p $(cat devlog.pid) to see if the process is active. The process ID is stored in devlog.pid.

What is the log entry format?

Each entry in dev_log.md follows the pattern ## YYYY-MM-DD HH:MM:SS: Your log message here with newlines between entries.

How do I stop the service?

Execute ./stop_server.sh, which will terminate the background process.

Where is the service output logged?

The Flask output and errors are written to devlog.log in the server’s root directory.