l-log-mcp-server

l-log-mcp-server

The standalone MCP (Model Context Protocol) server for llm-lean-log. It allows AI agents to search and access your coding task history.

MCP server with llm-lean-log

The pairing looks like:

LLM runtime
-[use CLI to write log]->
llm-lean-log (token-cheap, structured CSV)
->
mcp-server
<-[use MCP to read log]->
LLM runtime

llm-lean-log become MCP memory, which gives you:

• auditability (what did the model think last week?)
• debugging (why did it choose X?)
• analytics (token burn, drift, behavior change)
• training data for fine-tuning or evals

How to use?

• Install globally: bun i -g l-log-mcp-server.
• Add the configuration to your AI client's config file.
• Restart your AI client to pick up the new configuration.

Quick Start Configuration

After installing globally, you can get the configuration snippets for your favorite AI client by running:

l-log-mcp-server --config

OpenCode Configuration

Add this to your ~/.opencode.json:

{
  "mcp": {
    "llm-memory": {
      "type": "local",
      "command": ["l-log-mcp-server"],
      "environment": {
        "LLM_LOG_PATH": "/absolute/path/to/your/logs/chat.csv"
      }
    }
  }
}

Read more at: docs/config-for-opencode.md

Claude Desktop / Claude Code Configuration

Add this to your claude_config.json (Desktop) or .claude/settings.json (Code):

{
  "mcpServers": {
    "llm-memory": {
      "command": "l-log-mcp-server",
      "env": {
        "LLM_LOG_PATH": "/absolute/path/to/your/logs/chat.csv"
      }
    }
  }
}

Features / usesage

Resources

• memory://recent: View the last 50 log entries from the project history.
• memory://stats: View statistics about your logs (total entries, last entry date, unique tags).
• memory://last: View the very last log entry from the project history.

Example User Prompts:

• "Show me the last 50 log entries to see what I've been working on recently"
• "What are my project statistics? How many entries do I have and what tags have I used?"
• "What was the very last thing I worked on?"

Tools

• search_logs(query): Search the log history for past problems, solutions, or topics.
• get_task_history(taskName): Get all log entries related to a specific task name.

Example User Prompts:

• "Search my logs for 'database migration' using llm-memory MCP to see how I handled similar issues before"
• "Find all entries related to 'authentication system' using llm-memory MCP to understand the development history"
• "Look up any past 'build errors' using llm-memory MCP to see common solutions"
• "Look up how I solved 'TypeScript compilation errors' using llm-memory MCP in the past"

Prompts

• up: A prompt for daily standup meetings - "What did I do last time and what's next?"
• recent_work: A prompt template to summarize recent activities based on logs.
• learned: Review past mistakes and lessons learned to avoid repeating them.

Example User Prompts:

• "up from llm-memory mcp"
• "recent_work from llm-memory"
• "learned from llm-memory"
• "Help me with my daily standup - what did I do last time and what's next?"
• "Summarize what I've been working on recently"
• "Based on my past mistakes, what should I be careful about in this project?"

Postinstall

The package includes a postinstall script to streamline the setup process for new users.

Why it's needed: Setting up an MCP server requires specific configuration (like environment variables and command paths) that can be easily overlooked. The postinstall script provides an immediate, copy-paste-able configuration snippet tailored for your client (like OpenCode) right after installation.

How it runs: This script is triggered automatically by your package manager (bun, npm, or yarn) immediately after the global or local installation of l-log-mcp-server finishes.

Example output during installation:

✨ l-log-mcp-server summary:
To use this with OpenCode, add the following to your ~/.opencode.json:
{
  "mcp": {
    "llm-memory": {
      "type": "local",
      "command": [
        "l-log-mcp-server"
      ],
      "environment": {
        "LLM_LOG_PATH": "/absolute/path/to/your/logs/chat.csv"
      }
    }
  }
}

Note: Replace /absolute/path/to/your/logs/chat.csv with the actual path to your chat.csv file.
You can also get this config anytime by running: l-log-mcp-server --config

CLI Usage

l-log-mcp-server --help

Install from source

cd packages/mcp-server
bun i
bun run build

For more details about the core logic, see mcp/README.md.