MCP Chat Logger
MCP Chat Logger是一个简单而强大的聊天记录保存工具,可以将聊天历史保存为Markdown格式文件,便于后续查看和分享。
功能特点
- 支持大模型调用工具将聊天历史保存为格式化的Markdown文件
- 自动为每条消息添加时间戳
- 自定义保存目录
- 支持会话ID标识不同的对话
下一阶段
添加Overview功能
安装步骤
Installing via Smithery
To install MCP Chat Logger for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @AlexiFeng/MCP_Chat_Logger --client claude
- 克隆这个代码库:
git clone https://github.com/yourusername/MCP_Chat_Logger.git
cd MCP_Chat_Logger
- 安装依赖: 提前安装uv
uv add "mcp[cli]"
使用方法
- 在项目目录启动mcp服务
uv run chat_logger.py
- 在cursor/cherry studio中添加mcp服务器配置 "chat_logger": { "name": "chat_logger", "isActive": false, "command": "uv", "args": [ "--directory", "项目路径(例如~/MCP_Chat_Logger/)", "run", "chat_logger.py" ] }
项目结构
MCP_Chat_Logger/
├── chat_logger.py # 核心功能实现
├── chat_logs/ # 默认保存目录
├── README.md # 项目说明
├── README_zh.md # 中文说明
├── README_en.md # 英文说明
└── .gitignore # Git忽略文件
贡献指南
欢迎提交问题和拉取请求!如果您想贡献代码,请遵循以下步骤:
- Fork这个仓库
- 创建您的特性分支 (
git checkout -b feature/amazing-feature) - 提交您的更改 (
git commit -m 'Add some amazing feature') - 推送到分支 (
git push origin feature/amazing-feature) - 开启一个Pull Request
许可证
该项目采用MIT许可证 - 详情请查看 LICENSE 文件。
Metadata
Release files for iflow-mcp_alexifeng-mcp_chat_logger 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_alexifeng_mcp_chat_logger-0.1.0.tar.gz | 3.9 kB | Without provenance | Details for iflow_mcp_alexifeng_mcp_chat_logger-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_alexifeng_mcp_chat_logger-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_alexifeng_mcp_chat_logger-0.1.0-py3-none-any.whl |
Total release size: 8.6 kB
Release files / iflow_mcp_alexifeng_mcp_chat_logger-0.1.0.tar.gz
| Download URL | iflow_mcp_alexifeng_mcp_chat_logger-0.1.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32e4af9ea3ec5a85ce8e1f3b4018e645e8d625f76de134ac63f669663a069bb3
|
|
BLAKE2b-256 checksum How to use checksums |
6d43abbed7ff27eb3fbbd14ddf43996f615bfd3daf45e0b8b38c70d1b877d402
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_alexifeng_mcp_chat_logger-0.1.0-py3-none-any.whl
| Download URL | iflow_mcp_alexifeng_mcp_chat_logger-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af923559a4b41f8fb895ffe07fb46786d48888d7fc02899fc2b479146c7f729a
|
|
BLAKE2b-256 checksum How to use checksums |
d23e61808bbc15df70c8e93b8201bae1cd4ed4165ee50beaa9e17e0489534947
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_alexifeng-mcp_chat_logger 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.