Skip to main content
Glama

AI Conversation Logger MCP

中文版 | 日本語版

An intelligent MCP (Model Context Protocol) server designed specifically for AI assistants to automatically log and manage conversation history with developers.

🎯 Core Features

  • 🤖 AI-Driven Logging - All content is determined and provided by the AI assistant

  • 📝 Pure Save Mode - MCP only formats and stores, no content extraction or analysis

  • 🔄 Designed for AI Retrospection - Log format optimized for AI to quickly understand project history

  • 🏷️ Smart Organization - Auto-organize by project and date with tagging support

  • 🔍 Powerful Search - Multi-dimensional search by keywords, files, tags, and time range

  • 📊 Context Suggestions - Smart recommendations based on file associations

Related MCP server: OpenClaw Memory

🚀 Quick Start

1. Install Dependencies

npm install

2. Build Project

npm run build

3. Configure Claude Code

Add MCP server configuration to Claude Code's config file (~/.claude.json):

{
  "mcpServers": {
    "conversation-logger": {
      "command": "node",
      "args": ["/path/to/ai-conversation-logger-mcp/dist/index.js"]
    }
  }
}

4. Restart Claude Code

Restart Claude Code to apply the configuration.

📚 API Tools

1. log_conversation - Core Logging Tool

Records every AI-user interaction with structured information:

interface LogConversationParams {
  userRequest: string;      // User's original request + uploaded file descriptions
  aiTodoList: string[];     // AI's execution plan (list even for view-only tasks)
  aiSummary: string;        // AI's operation summary (3-5 sentences)
  fileOperations?: string[]; // File operations in format: "action filepath - description"
  title?: string;           // Conversation title (optional)
  tags?: string[];          // Tag array (optional)
  project?: string;         // Project name (auto-detected if not provided)
}

2. search_conversations - Search Tool

Search through conversation history with multiple filters:

interface SearchParams {
  keywords?: string[];     // Keyword search
  filePattern?: string;    // File name pattern search
  days?: number;          // Recent N days
  project?: string;       // Project filter (defaults to current)
  tags?: string[];        // Tag filter
  limit?: number;         // Result limit (default: 10)
}

3. get_context_suggestions - Context Recommendations

Get relevant historical context based on current work:

interface ContextParams {
  currentInput: string;    // Current user input
  currentFiles?: string[]; // Currently involved files
  project?: string;        // Project filter (optional)
}

📁 Storage Structure

Logs are stored in the project's ai-logs/ directory:

project-root/
├── ai-logs/
│   ├── 2025-08-07.md     # Daily conversation logs
│   ├── 2025-08-06.md
│   └── config.json       # Project configuration
├── src/
└── ...

📝 Log Format

Each conversation is recorded with the following structure:

## [Timestamp] Title #tags

### 🗣️ User Request
[Original user request]

### 📋 AI Execution Plan
- [x] Completed task
- [ ] Pending task

### 🤖 AI Summary
[Summary of what was accomplished]

### 📂 File Operations
- **Created** `path/to/file` - Purpose description
- **Modified** `path/to/file` - What was changed
- **Deleted** `path/to/file` - Reason for deletion

### 🏷️ Tags
#module #technology #type

🎯 Usage Principles

When to Log

All conversations should be logged, including:

  • New feature development

  • Bug fixes (any size)

  • Code refactoring

  • Configuration changes

  • Code explanations and analysis

  • Technical Q&A

  • Code reviews

  • Any project-related dialogue

Key Points

  1. AI-Driven Content - AI determines what information to log

  2. Complete Context - Include all relevant details for future reference

  3. Focus on "What" not "How" - Emphasize functionality over technical details

  4. Consistent Format - Maintain standardized markdown structure

🛠️ Development

Development Mode

npm run dev

Run Tests

npm test

Code Linting

npm run lint
npm run lint:fix

TypeScript Check

npm run type-check

🔧 Technical Stack

  • TypeScript - Type-safe development

  • MCP SDK - Model Context Protocol implementation

  • Node.js - Runtime environment

  • Jest - Testing framework

📄 License

MIT

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

📮 Contact

For issues or suggestions, please open an issue on GitHub.

Available Tools

4 tools
get_context_suggestionsC

获取相关上下文建议

基于当前输入和文件推荐历史记录

Inputs: currentInput (required), currentFiles, project.

list_projectsC

List all projects with optional statistics

Inputs: includeStats.

log_conversationA

记录AI对话 - 所有会话都要记录

使用规范: • userRequest: 用户原始需求+上传文件说明 • aiTodoList: 你的执行计划清单(即使只是查看也要列出) • aiSummary: 你的操作总结(3-5句话,包括解释、分析等) • fileOperations: 文件操作总结,格式:"动作 文件路径 - 说明"(可为空) • title: 对话标题(可选) • tags: 标签数组(可选)

Inputs: userRequest (required), aiTodoList (required), aiSummary (required), fileOperations, +3 more.

search_conversationsC

搜索历史对话记录

支持: • 关键词搜索 • 文件名模式搜索 • 时间范围筛选 • 标签过滤

Inputs: keywords, filePattern, days, project, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have distinct purposes: get_context_suggestions provides recommendations, list_projects enumerates projects, log_conversation records conversations, and search_conversations finds historical data. There is minor potential confusion between get_context_suggestions and search_conversations, as both involve retrieving conversation-related information, but their descriptions clarify that one is for recommendations and the other for direct searches.

    Naming Consistency3/5

    The tool names follow a mixed pattern: get_context_suggestions and search_conversations use verb_noun format, while list_projects and log_conversation use verb_noun but with slight inconsistency in structure. The naming is readable but lacks strict uniformity, as seen in the variation between 'get_' and 'search_' prefixes and the absence of a consistent convention across all tools.

    Tool Count4/5

    With 4 tools, the count is appropriate for a conversation logging server, covering core functions like listing, logging, searching, and context suggestions. It is slightly lean but reasonable, as each tool serves a distinct role without obvious redundancy or bloat, though it might benefit from additional tools for advanced management tasks.

    Completeness4/5

    The tool set covers essential CRUD-like operations for conversation logging: list_projects for reading, log_conversation for creating, and search_conversations for querying, with get_context_suggestions adding utility. Minor gaps exist, such as the lack of update or delete tools for conversations or projects, but agents can likely work around these limitations for basic logging workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      Provides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.
      16
      61 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Automatically records AI conversation turns and code changes to local Markdown files to provide persistent context across chat sessions. It enables AI agents to search history through MCP tools and provides a web viewer for browsing past discussions.
      3
      4
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to query and store a team's historical development experience through semantic search, so lessons and decisions persist across conversations.
      9
      132 PyPI
      1
      MIT