get_log_files
Get a paginated list of available log files in the specified directory with filtering options
LABSCO SUMMARY
It records the intention, which is the part you cannot reconstruct later.
Git tells you what changed; this records why the assistant did it and what it was working on at the time, in a field that is required rather than optional. That is what makes search_logs worth running at the start of a session — filtering by type and date gets you back the reasoning, not just the diff. The catch is that nothing logs automatically: without an instruction in your rules file the server sits idle.
What it is
An MCP server that gives a coding assistant somewhere to record what it did and why. Each entry is JSON on disk with a summary, structured details, the intention behind the action and the surrounding context, linked to a parent entry and to related entries — so a later session can search the history and pick the work back up.
What you get
- An activity recorded under one of six types —
command_execution,code_generation,file_operation,error_encountered,decision_made,conversation— with summary, intention, context and free-form details, at a level ofdebug,info,warnorerror—log_activity - Hierarchy and ordering across entries:
parentIdfor nesting,sequencefor order, andrelatedIdsfor grouping work that belongs together - Saved log files listed recursively, with paging and a directory depth limit —
get_log_files - Logs searched by type, level, date range, free text, parent id, related ids and sequence range, with paging —
search_logs - Entries written as date-based JSON files in a directory you name per call, created for you if it does not exist
Requirements
No account and no key — it writes to your own filesystem. Every tool takes logsDir as an absolute path; relative paths are not accepted. The npm package name is roo-activity-logger (0.2.0) and it runs without cloning via npx -y github:annenpolka/roo-logger. Logging only happens if the assistant is told to do it, so add a rule to your CLAUDE.md or your Cline/Roo-Code rule file instructing it to log through this server and to search the logs before starting.
Setup effort
One command — npx -y github:annenpolka/roo-logger
USE CASES
01
Picking up a task after a break
Search the logs for the recent entries on this project and read back the intentions and decisions, instead of reconstructing them from the diff.
02
Finding out when something broke
Filter for error_encountered entries in a date range and read the context recorded alongside each one.
03
Keeping a record of why choices were made
Log decision_made entries as they happen, with the intention and the alternatives in the details, so the reasoning survives the session.
04
Grouping a multi-step change into one story
Give related entries a shared parent id and sequence numbers, then retrieve the whole chain later as a single piece of work.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
log_activity
Record an activity log entry with structured data for tracking development activities, decisions, and context
search_logs
Search and filter activity logs with various criteria including date ranges, text search, and activity relationships
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Build from source
TERMINAL
# Clone the repo
git clone https://github.com/annenpolka/roo-logger.git
cd roo-logger
# Install dependencies
npm install
# Build
npm run buildnpx
TERMINAL
npx -y github:annenpolka/roo-loggerMCP Clients
Cline, Roo Code, Claude Code
JSON
{
"mcpServers": {
"roo-activity-logger": {
"command": "npx",
"args": [
"-y",
"github:annenpolka/roo-logger"
],
"env": {},
"disabled": false
}
}
}
