Atlas / MCP servers / annenpolka / Roo Logger

Roo LoggerSAFE

Name: Roo Logger
Author: annenpolka

mcp/annenpolka/roo-logger

MCP server by annenpolka · cline · mcp server · model context protocol · Audited 2026-10-09

⚑ Report / re-scan Source ↗

An MCP server for logging activity in Roo Code/Cline.

Verdict

SAFE

Grade

Trust score

89 /100

Exposed tools

3 3r · 0w · 0d

Transport

stdio

License

MIT

Stars

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

日本語版はこちら | 中文版

TL;DR

What is it? — This is an MCP server that automatically logs AI coding assistant activities such as command executions and code generation (supports Roo Code, Cline, Claude Code, etc.).
What does it do? — It saves activity history as JSON files, which you can search and analyze later.
How do I use it? — Add it to your Claude Code, Cline, or Roo-Code settings to enable automatic activity logging.

Overview

Roo Activity Logger is an MCP (Model Context Protocol) server that automatically records AI coding assistant development activities — including command executions, code generation, file operations, and more. It supports Claude Code, Cline, Roo-Code, and other MCP-compatible AI assistants. All logs are saved in JSON format, making it easy to search, analyze, and restore context at any time.

How activity logging works

flowchart TD
A[Roo's Action] --> B[Select Activity Type]
B --> C[Log via log_activity]
C --> D[Provide Log Info- Summary- Details- Intention- Context]
D --> E[Specify Save Directory]
E --> F[Save as JSON file]

How to search logs and restore context when resuming a task

flowchart TD
G[Resume Task] --> H[Search with search_logs]
H --> I[Set Search Filters- Type- Date Range- Text]
I --> J[Retrieve Related Activities- Parent/Child- Sequence- Related IDs]
J --> K[Restore Context & Resume- Review Past Intentions- Understand Progress]

Sample Log Entry

Here is an example of a file_operation log entry saved as JSON:

{
"id": "75add15d-8d5b-4e60-b327-fde785050c86",
"timestamp": "2025-04-10T01:58:02.905Z",
"type": "file_operation",
"level": "info",
"summary": "Inserted mermaid diagram into README.md",
"details": {
"file": "README.md",
"operation": "insert_content",
"insertedLines": "mermaid co

Read from source at commit a741e815a123OBSERVED · 2026-10-09

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code

claude mcp add roo-activity-logger -- npx -y [email protected]

claude-desktop

{
  "mcpServers": {
    "roo-activity-logger": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}

Exposed tools (3)

3 read · 0 write · 0 destructive.

Tool	Risk	Description
`get_log_files`	read	Get a paginated list of available log files in the specified directory with filtering options
`log_activity`	read	Record an activity log entry with structured data for tracking development activities, decisions, and context
`search_logs`	read	Search and filter activity logs with various criteria including date ranges, text search, and activity relationships

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

Layer	What it checks	Result
L0	Provenance & inventory	PASS
L1	Static analysis of the code	PASS
L2	Instruction surface (what it tells the agent)	PASS
L3	Class-specific surface	PASS
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: none-observed
Network: none-observed
Shell: none-observed
Dependencies: not all pinned
Secrets in source: none-found

Findings (7)

LOWInventory / provenance · inv.hidden_file · CWE-1104

.clinerules

.clinerules

Why it matters. hidden member outside the usual dotfiles

Fix. review its purpose