Append Log MCP
Give agents a durable append-only JSONL log they can write to and query by recency for audits, traces, and session memory without a full database.
Overview
Append Log MCP is an MCP server for the Operate phase that persists timestamped JSONL log entries and lets agents append records and query them by recency.
What is this MCP server?
- Append-only log MCP with timestamped JSON entries stored in JSONL format
- Configurable tools: append and query exposed via APPEND_LOG_TOOLS
- Docker OCI package roberthouse224/append-log-mcp:1.0.0 with volume append-log-data:/data
- APPEND_LOG_FILE defaults to /data/log.jsonl inside the container for portable persistence
- Server version 1.0.0
- Two available tools: append and query
- Default log path /data/log.jsonl in the container when using APPEND_LOG_FILE default
What problem does it solve?
Agent workflows lose context and accountability when important decisions and tool results only live in chat history with no structured, queryable log.
Who is it for?
Self-hosted agent setups that need a minimal durable event log on disk with MCP-native append and query tools.
Skip if: Teams that need full-text analytics, multi-tenant SaaS logging, or complex retention policies without running their own container.
What do I get? / Deliverables
After Docker setup and MCP registration, your agent can append events to JSONL and pull recent entries for debugging, compliance notes, or session continuity.
- Persistent JSONL log file at the configured APPEND_LOG_FILE path
- MCP tools for appending timestamped JSON entries and querying by recency
Recommended MCP Servers
Journey fit
You reach for this once something is running in production or long-running dev sessions where you need observable, timestamped events agents can read back. Monitoring fits because the server’s core value is persisting and querying chronological entries, not building UI or shipping features.
How it compares
Lightweight append-only log MCP, not a metrics APM suite or relational database MCP.
Common Questions / FAQ
Who is append-log-mcp for?
It is for indie builders and agent operators who want a simple JSONL audit log their MCP client can write to and read from.
When should I use append-log-mcp?
Use it in operate when you need timestamped, append-only persistence for agent actions, debugging, or session replay on infrastructure you control.
How do I add append-log-mcp to my agent?
Run the Docker image roberthouse224/append-log-mcp:1.0.0 with volume append-log-data:/data, set APPEND_LOG_TOOLS to append,query, configure APPEND_LOG_FILE if needed, and register stdio MCP from the package definition.