roo-logger

Roo Activity Logger is an MCP server that automatically records AI coding assistant activities such as command executions, code generation, file operations, and more. It stores these activities as JSON logs that you can search, filter, and analyze later. To use it, add the roo-logger MCP entry to your Cline, Roo-Code, or Claude Code configuration so that actions like command executions, code generation, and file operations get logged automatically. The system is designed to integrate with Roo-Code, Cline, and Claude Code ecosystems, producing structured log entries that include type, summary, details, intention, context, and IDs for tracing relationships across activities. You can then rely on the search and restore capabilities to review past work or resume tasks with context preserved.

Prerequisites:

• Node.js (recommended LTS) and npm are installed on your system
• Git is available if you plan to clone the repository for development or local builds

Install and run via npx (no local clone required):

• Ensure you have an internet connection
• Use this MCP server entry in your configuration (as shown in mcp_config) to fetch and run the package on demand

If you want to develop or run locally:

1. Clone the repository git clone https://github.com/annenpolka/roo-logger.git
2. Install dependencies cd roo-logger npm install
3. Build the project (if needed by the project setup) npm run build
4. Run locally using your built entry point (example shows using a local dist/index.js): { "mcpServers": { "roo-logger": { "command": "node", "args": ["/path/to/your/local/roo-logger/dist/index.js"], "env": {}, "disabled": false } } }
5. Verify that logs directory and any required directories exist or are created automatically as described in the project notes

Tips and notes:

• The logger saves logs as JSON files organized by date; you can customize the save directory per activity using logsDir in log entries.
• When using the npx approach, you don’t need to clone the repo, but for customization or local testing, building locally is recommended.
• If you encounter issues, ensure your environment has network access for npx or that the local dist/index.js path is correct.
• Typical environment variables are left empty; fill in ENV values if your deployment requires specific paths or permissions (e.g., logs storage location).
• The MCP tool supports several activity types such as command_execution, code_generation, file_operation, error_encountered, decision_made, and conversation; ensure your logging calls provide the required fields (type, summary, intention, context, logsDir).
• For best results, consistently log meaningful intention and context to aid searchability and task restoration.