Chatlog

Created By
sjzara year ago
Overview

what is Chatlog?

Chatlog is a tool designed to retrieve and manage chat data from local databases, specifically for WeChat users on Windows and macOS. It provides a user-friendly interface and command-line tools for accessing chat records and multimedia messages.

how to use Chatlog?

To use Chatlog, install the application, run it to access the Terminal UI, and follow the prompts to decrypt data and start the HTTP service for API access.

key features of Chatlog?

  • Retrieves chat data from local database files.
  • Supports Windows and macOS systems.
  • Provides a Terminal UI and command-line tool.
  • Offers an HTTP API for querying chat records, contacts, and group chats.
  • Integrates seamlessly with AI assistants via MCP SSE protocol.
  • Supports multimedia messages and automatic data decryption.
  • Allows multi-account management.

use cases of Chatlog?

  1. Accessing and managing WeChat chat history.
  2. Integrating with AI assistants for enhanced chat functionalities.
  3. Analyzing chat data through HTTP API for statistics and dashboards.

FAQ from Chatlog?

  • Can Chatlog retrieve data from all WeChat versions?

Chatlog supports WeChat versions 3.x and 4.0.

  • Is Chatlog free to use?

Yes! Chatlog is free to use for everyone.

  • How do I migrate chat data from my phone?

You can migrate data by using the WeChat settings on your phone to transfer chat history to your computer.

Server Config

{
  "mcpServers": {
    "chatlog": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:5030/sse"
      ],
      "_comment1": "This is a MCP SSE Server, must be installed locally to be used.",
      "_comment2": "Config Consultation: https://github.com/sjzar/chatlog/blob/main/docs/mcp.md"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sjzar
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago