Chat Export MCP server
2026년 11월 14일 커밋로컬 Chrome extension 브릿지를 통해 AI 클라이언트가 웹 LLM 제공업체의 채팅 세션을 목록화, 읽기, 내보내기 및 상호작용할 수 있도록 합니다.
다른 이름 svergio/chat-export-server, chat-export-server
- 스타
- 1
- Tools
- 2
- 다운로드, 30일
- —
- 최신 버전
- 1.0.4
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- MIT
Chat Export MCP란?
로컬 Chrome extension 브릿지를 통해 AI 클라이언트가 웹 LLM 제공업체의 채팅 세션을 목록화, 읽기, 내보내기 및 상호작용할 수 있도록 합니다. 2개 도구를 제공합니다. 예: platforms_list, chat_ask.
프로젝트 README에서 생성된 요약
Chat Export MCP server 정보
Chat Export는 로컬 Chrome extension을 브릿지로 사용하여 AI agent가 웹 기반 LLM 세션과 상호작용할 수 있는 방법을 제공합니다. 비용이 많이 드는 벤더 HTTP API나 클라우드 기반 데이터 경로에 의존하는 대신, 이 MCP server는 브라우저에서 이미 로그인하여 사용 중인 웹 인터페이스에 연결합니다. 127.0.0.1에서 실행되는 로컬 프로세스가 WebSockets를 통해 extension과 통신하는 방식으로 작동하며, 이를 통해 Cursor와 같은 도구가 기존 채팅을 관리할 수 있습니다.
개발자는 이 MCP server를 사용하여 ChatGPT, Claude, DeepSeek, Perplexity, GitHub Copilot web을 포함한 8개의 서로 다른 웹 제공업체에서 세션을 목록화, 읽기, 내보내기, 생성 및 삭제할 수 있습니다. 시스템은 작업 큐를 통해 장시간 실행되는 작업을 관리하며, 스레드 데이터에는 로컬 SQLite 캐시를 사용합니다. 모든 데이터가 로컬 머신에 머물기 때문에 채팅 내용과 세션 데이터가 컴퓨터 외부로 유출되지 않으며, 다양한 LLM 제공업체를 위한 별도의 API 키를 제공할 필요가 없습니다.
활용 사례
- 1채팅 세션 관리 자동화AI 클라이언트가 여러 웹 제공업체의 기존 대화 기록을 목록화하고 내보낼 수 있습니다.
- 2웹 인터페이스를 통한 프롬프트 실행chat_ask 도구를 사용하여 agent가 특정 웹 LLM 세션에 프롬프트를 보내도록 지시할 수 있습니다.
- 3브라우저 프로필과 IDE agent 동기화MCP 클라이언트를 특정 Chrome 프로필에 바인딩하여 올바르게 로그인된 세션을 대상으로 지정할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Chat Export MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Chat Export MCP 설치
$ claude mcp add --env 'CHAT_EXPORT_MCP_TOKEN=<YOUR_CHAT_EXPORT_MCP_TOKEN>' chat-export-server -- docker run -i --rm ghcr.io/svergio/chat-export-server:1.0.4Cursor에 Chat Export MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"chat-export-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/svergio/chat-export-server:1.0.4"
],
"env": {
"CHAT_EXPORT_MCP_TOKEN": "<YOUR_CHAT_EXPORT_MCP_TOKEN>"
}
}
}
}VS Code에 Chat Export MCP 설치
.vscode/mcp.json
{
"servers": {
"chat-export-server": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/svergio/chat-export-server:1.0.4"
],
"env": {
"CHAT_EXPORT_MCP_TOKEN": "<YOUR_CHAT_EXPORT_MCP_TOKEN>"
}
}
}
}VS Code CLI에 Chat Export MCP 설치
$ code --add-mcp '{"name":"chat-export-server","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/svergio/chat-export-server:1.0.4"],"env":{"CHAT_EXPORT_MCP_TOKEN":"<YOUR_CHAT_EXPORT_MCP_TOKEN>"}}'Claude Desktop에 Chat Export MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"chat-export-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/svergio/chat-export-server:1.0.4"
],
"env": {
"CHAT_EXPORT_MCP_TOKEN": "<YOUR_CHAT_EXPORT_MCP_TOKEN>"
}
}
}
}Codex에 Chat Export MCP 설치
$ codex mcp add chat-export-server --env 'CHAT_EXPORT_MCP_TOKEN=<YOUR_CHAT_EXPORT_MCP_TOKEN>' -- docker run -i --rm ghcr.io/svergio/chat-export-server:1.0.4Codex config.toml에 Chat Export MCP 설치
~/.codex/config.toml
[mcp_servers.chat-export-server] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/svergio/chat-export-server:1.0.4"] [mcp_servers.chat-export-server.env] CHAT_EXPORT_MCP_TOKEN = "<YOUR_CHAT_EXPORT_MCP_TOKEN>"
Gemini CLI에 Chat Export MCP 설치
$ gemini mcp add -s user -e 'CHAT_EXPORT_MCP_TOKEN=<YOUR_CHAT_EXPORT_MCP_TOKEN>' chat-export-server docker -- run -i --rm ghcr.io/svergio/chat-export-server:1.0.4Gemini settings.json에 Chat Export MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"chat-export-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/svergio/chat-export-server:1.0.4"
],
"env": {
"CHAT_EXPORT_MCP_TOKEN": "<YOUR_CHAT_EXPORT_MCP_TOKEN>"
}
}
}
}Chat Export MCP 도구 2
README에서 감지됨platforms_listchat_ask
| platforms_list | — | |
| chat_ask | — |
구성
CHAT_EXPORT_MCP_TOKEN비밀Optional pre-set MCP Bearer token (cem_…); otherwise generated on first start
CHAT_EXPORT_HOMEData directory for SQLite cache, keys and exports
CHAT_EXPORT_HOSTHTTP bind host (default 127.0.0.1; use 0.0.0.0 in containers)
CHAT_EXPORT_PORTHTTP port for /mcp, /ws and /health (default 8765)
| 이름 | 설명 | 유형 |
|---|---|---|
| CHAT_EXPORT_MCP_TOKEN | Optional pre-set MCP Bearer token (cem_…); otherwise generated on first start | 비밀 |
| CHAT_EXPORT_HOME | Data directory for SQLite cache, keys and exports | |
| CHAT_EXPORT_HOST | HTTP bind host (default 127.0.0.1; use 0.0.0.0 in containers) | |
| CHAT_EXPORT_PORT | HTTP port for /mcp, /ws and /health (default 8765) |
자동 검사
2026년 11월 13일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능svergio/chat-export-server is public and reachablegithub.com/svergio/chat-export-server ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/svergio/chat-export-server ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음2 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기chat-export-server
Local MCP server for the Chat Export Chrome extension. List, read, export, create, delete, and ask in your own chats on eight web providers (ChatGPT, Grok, X Grok, Claude, GitHub Copilot, Qwen, DeepSeek, Perplexity) — through the extension in your browser. Everything stays on 127.0.0.1: job queues, SQLite chat cache, audit log, optional dashboard UI.
Listed on Glama (v1.0.5, TDQS 4.4/5).
Standalone
chat-export-server plus the Chrome extension is a complete local stack. Browser chat ops run through the extension WebSocket bridge — no Chrome DevTools MCP, Playwright, or vendored agent code. Ship with native install, Docker / Colima, or Kubernetes (deploy/k8s). Any MCP client (Cursor, Claude Desktop, Open WebUI, local LLMs such as Bonsai-27B) is optional.
Why this MCP (for awesome-list reviewers)
Most LLM MCP servers wrap a vendor HTTP API (keys, quotas, cloud data path). Chat Export is different: the agent talks MCP to a local process; that process drives the web UIs you are already logged into via the Chrome extension bridge. No OpenAI/Anthropic/xAI API keys for chat ops, no chat bodies leaving 127.0.0.1, and delete/create stay off until you opt in (allowDestructive + confirm). Pair with the extension zip; point Cursor (or any MCP client) at http://127.0.0.1:8765/mcp.
The problem
IDE agents need structured access to web LLM sessions without pasting cookies or paying per-token cloud APIs. You want MCP tools, retries, and queues — but data must not leave your machine.
What you get
| Platform | Automation |
|---|---|
| ChatGPT | list / get / export / create / delete / ask |
Grok (grok.com) |
same |
| X Grok | same |
| Claude | same |
| GitHub Copilot web | same |
Qwen (chat.qwen.ai) |
same |
DeepSeek (chat.deepseek.com) |
same |
Perplexity (perplexity.ai) |
same |
Architecture
chat-export-server binds on loopback (by default), hosts the extension browser hub over WebSocket (/ws, ceb_ tokens), exposes Streamable HTTP MCP at /mcp for IDE agents (cem_/cek_), runs per-browser job lanes with a SQLite chat cache and WAL, and optionally serves the embedded dashboard at /dashboard/ plus /dashboard/api. Long operations (chat_ask, bulk export, delete with gates) go through the job queue instead of blocking MCP.
Install paths: native Node 22 CLI (npm run build, chat-export-server start), Docker / Colima (Dockerfile + Compose on 127.0.0.1:8765), or Kubernetes (kubectl apply -k deploy/k8s, port-forward for the Chrome bridge). Full Mermaid diagrams and endpoint map: Wiki — Architecture. Operators: Native and Kubernetes deployment · Use cases · MCP tools and profiles.
Quick start (3 steps)
- Extension — load chat-export-extension unpacked; enable bridge in popup; open provider tabs logged in.
- Server —
npm install && npm run build,chat-export-server key new,chat-export-server start→http://127.0.0.1:8765. - MCP client — point to
http://127.0.0.1:8765/mcpwithAuthorization: Bearer <key>; runbrowsers_bindthenchats_list/chats_export/chat_ask.
Wiki: MCP tools and profiles.
Install and build
npm install
npm run build # tsc -> dist/
npm link # optional: chat-export-server on PATH
Requires Node 22.13+ (node:sqlite).
| Script | Purpose |
|---|---|
npm run build |
compile to dist/ |
npm run typecheck |
tsc --noEmit |
npm start |
node dist/cli/index.js start |
npm run dev |
tsx watch src/cli/index.ts start |
npm run mcp |
stdio MCP attached |
First run
chat-export-server key new # print once; hash stored
chat-export-server start
# WS /ws, /ext — extension bridge
# MCP /mcp — Bearer key
# GET /health
Data under ~/.chat-export (override CHAT_EXPORT_HOME):
~/.chat-export/
config.json # host, port, exportDir
keys.json # hashes only (chmod 600)
audit.log # MCP/RPC audit
exports/ # chats_export output
chat-export-server key rotate
chat-export-server key list
chat-export-server status
Configuration
Environment variables
Copy .env.example to .env in the server directory (or set CHAT_EXPORT_ENV_FILE), then chmod 600 .env. Never commit .env (gitignored); keep secrets out of .env.example. Container and process env override config.json where noted.
| Variable | Purpose |
|---|---|
CHAT_EXPORT_HOME |
Data directory (default ~/.chat-export; /data in Docker) |
CHAT_EXPORT_HOST |
Bind address (127.0.0.1 locally; use 0.0.0.0 in containers) |
CHAT_EXPORT_PORT |
HTTP port (default 8765) |
CHAT_EXPORT_ALLOWED_HOSTS |
Extra Host header names allowed (comma-separated) |
CHAT_EXPORT_DASHBOARD_ENABLED |
true / false |
CHAT_EXPORT_ADMIN_USER / CHAT_EXPORT_ADMIN_PASS |
Dashboard login (overrides config.json) |
CHAT_EXPORT_MCP_TOKEN |
Optional preset cem_… token hash on start |
CHAT_EXPORT_BROWSER_TOKENS |
browserId:ceb_…[:label] comma list for auto-enroll |
CHAT_EXPORT_ALLOW_DESTRUCTIVE |
true / false |
CHAT_EXPORT_DB_DRIVER |
DB driver override (sqlite default) |
CHAT_EXPORT_DB_URL |
DB URL when not using default SQLite path |
CHAT_EXPORT_SKIP_MCP_CONFIG |
Set 1 to skip auto-writing Cursor MCP config on key new |
Docker and Colima
This repo ships a multi-stage Dockerfile (Node 22 Alpine, non-root user, CHAT_EXPORT_HOME=/data, listen 0.0.0.0:8765, /health check). Docker Desktop is not required — use Colima on macOS:
colima start
docker context use colima # or: docker --context colima …
cp .env.example .env # set CHAT_EXPORT_ADMIN_PASS at minimum
docker --context colima compose build
docker --context colima compose up -d
curl -sS http://127.0.0.1:8765/health
Published only on 127.0.0.1:8765. Persistent data: Compose volume chat-export-data → /data.
Stop when finished so a local chat-export-server daemon can reclaim the port:
docker --context colima compose down
Optional split stack (nginx serves dashboard static, proxies /dashboard/api, /mcp, /ws, /ext, /enroll, /health to the server): build from the maintainer tree chat-export-dashboard/Dockerfile and projects/Chat Export/docker-compose.yml (see dashboard repo).
Kubernetes
Manifests under deploy/k8s/ (non-root UID 10001, PVC on /data, /health probes, Ingress with WebSocket upgrade for /ws, /ext, /mcp). Apply with kubectl apply -k deploy/k8s; for local Chrome bridge use kubectl port-forward to 127.0.0.1. Full steps: deploy/k8s/README.md and wiki Native and Kubernetes deployment.
config.json (under CHAT_EXPORT_HOME)
Created on first start. Example (secrets redacted):
{
"host": "127.0.0.1",
"port": 8765,
"exportDir": "~/.chat-export/exports",
"rpcTimeoutMs": 60000,
"dashboard": {
"enabled": true,
"username": "admin",
"password": "changeme"
},
"registeredBrowsers": [],
"settings": {
"platformsEnabled": ["chatgpt", "grok", "grok-x", "copilot", "claude"],
"allowDestructive": false,
"exportSchema": "chat-export/1"
}
}
settings.exportSchema defaults to chat-export/1 (also sharegpt/1). MCP chats_export / export jobs accept optional schema; omitted → this setting, then the browser default. See wiki Export formats.
Change dashboard.password before exposing the host beyond loopback. Server listens on 127.0.0.1:8765 by default (/health, /mcp, /ws, /dashboard/).
Tokens
| Prefix | Used by |
|---|---|
cek_ / cem_ |
MCP and CLI (Authorization: Bearer … on /mcp) |
ceb_ |
Chrome extension WebSocket (/ws); enroll via CLI or dashboard |
Only hashes of MCP keys are stored in keys.json (mode 600). Plaintext is shown once at chat-export-server key new.
Detached daemon (maintainer workspace)
In the Chat Export maintainer tree, tmp-scripts/ensure-daemon.mjs can keep chat-export-server running on :8765, write ~/.chat-export/server.pid, and optionally sync Bearer cem_… into .cursor/mcp.json (--sync-mcp-json). Equivalent manual start: chat-export-server start.
Cursor MCP (~/.cursor/mcp.json or project .cursor/mcp.json)
HTTP (server already running):
{
"mcpServers": {
"chat-export": {
"url": "http://127.0.0.1:8765/mcp",
"headers": {
"Authorization": "Bearer cem_YOUR_KEY_HERE"
}
}
}
}
Profiles: expose the full tool surface (chats_*, jobs_*, chat_cache_*, projects_*) for IDE agents. A small read-focused subset (list/get/export, browsers, platforms) is documented on the wiki MCP tools page — match your client’s token budget. Open WebUI via mcpo can proxy the same HTTP endpoint if your setup uses an OpenAPI bridge on another port.
After MCP is configured, run browsers_bind so tools target your connected Chrome profile.
Extension bridge settings: chat-export-extension README.
Background jobs
Long work (chat_ask, export, bulk delete) uses per-browser lanes:
jobs_enqueue,jobs_status,jobs_list,jobs_cancel
Cursor MCP config
HTTP (server already running):
{
"mcpServers": {
"chat-export": {
"url": "http://127.0.0.1:8765/mcp",
"headers": {
"Authorization": "Bearer cek_YOUR_KEY_HERE"
}
}
}
}
stdio:
{
"mcpServers": {
"chat-export": {
"command": "chat-export-server",
"args": ["start", "--stdio"],
"env": {
"CHAT_EXPORT_HOME": "/Users/YOU/.chat-export"
}
}
}
}
MCP tools (overview)
| Tool | Purpose |
|---|---|
browsers_list / browsers_bind / browsers_status |
Connected Chrome profiles |
platforms_list |
Enablement matrix |
chats_list / chats_get / chats_export |
Read and write exports |
chats_create / chats_delete |
UI drive (delete needs confirm: true) |
chat_ask |
Send prompt; wait or job queue |
jobs_* |
Async pipeline |
chat_cache_* |
Temp SQLite cache for long threads |
Full list evolves with releases; see wiki MCP Tools.
Optional: local LLM (e.g. Bonsai-27B)
Any external MCP client (Cursor, Claude Desktop, Open WebUI, or your own agent) can call Streamable HTTP at http://127.0.0.1:8765/mcp. A local OpenAI-compatible runtime such as Bonsai-27B (oMLX or similar on :8000/v1) is an optional orchestrator — Chat Export does not ship or vendor agent code. Example pattern: local model plans steps, this server drives chat_ask / jobs_* in your logged-in Chrome tabs. Guide: wiki Local LLM + Bonsai-27B (RU).
Layout
packages/protocol/ wire contract v1
src/core/ config, keys, audit, db, jobs, cache
src/hub/ WebSocket BrowserHub
src/mcp/ MCP HTTP + stdio
src/cli/ CLI entry
src/dashboard-api.ts /dashboard/api + dashboard/public
dashboard/ git submodule → chat-export-dashboard
git submodule update --init after clone.
Security
- Loopback only by default (
127.0.0.1). Change host only if you understand exposure. - Keys (
cek_/cem_) grant full local API — never commit or publish. - Browser tokens (
ceb_) are separate from MCP keys. chats_deleteand similar needallowDestructiveon extension and server plusconfirm: true.- Append-only audit for sensitive RPC. See SECURITY.md.
- Personal data portability is the goal; you must comply with each provider ToS. Not legal advice.
Related repositories
| Repo | Role |
|---|---|
| chat-export-extension | Content scripts + WS client |
| chat-export-server (this) | MCP hub, jobs, cache |
| chat-export-dashboard | Operator UI submodule |
| Wiki | Install, security, FAQ |
Support the project
- Tip (fiat): DonationAlerts — svwergio_mel
Tips are voluntary; they do not purchase support SLAs or private builds.
FAQ
- No telemetry; no external servers for core operation.
- Only your chats, from your browser session.
- Shared wording: packages/faq.md.
Contributing
See CONTRIBUTING.md (build, deploy/k8s, embedded dashboard sync, test branch gate), extension CONTRIBUTING.md (protocol PLATFORMS), and wiki Contributing.
Dependencies
Runtime: Node 22.13+, @modelcontextprotocol/sdk, ws, zod, workspace @chat-export/protocol (ISC wire contract in packages/protocol/). No Playwright, Puppeteer, Electron, or cloud SDKs in production.
Product graph: chat-export-extension (browser ceb_ WebSocket) ↔ this server ↔ embedded chat-export-dashboard static assets. Dashboard is a git submodule under dashboard/, not an npm dependency of the extension.
Docker: multi-stage node:22-alpine runtime; optional split dashboard image nginx:alpine. package-lock.json is committed for GitHub Dependabot / dependency graph.
Third-party list: THIRD_PARTY_NOTICES.md (npm run licenses). Optional SBOM: npm sbom --omit dev.
Not required: Cursor, Open WebUI, BibLLMsteak, Bonsai-27B, NodeRed paths — optional MCP clients or maintainer docs only.
License
See LICENSE.
Chat Export MCP 질문
Chat Export MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'CHAT_EXPORT_MCP_TOKEN=<YOUR_CHAT_EXPORT_MCP_TOKEN>' chat-export-server -- docker run -i --rm ghcr.io/svergio/chat-export-server:1.0.4를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Chat Export MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Chat Export MCP는 어떤 도구를 제공하나요?
2개 도구를 제공합니다. 예: platforms_list, chat_ask.
이 MCP server가 벤더 API를 사용하나요?
아니요, Chrome extension 브릿지를 통해 이미 로그인되어 있는 웹 UI를 제어하므로 OpenAI 또는 Anthropic API 키가 필요하지 않습니다.
데이터는 어디에 저장되나요?
작업 큐, SQLite 채팅 캐시, 감사 로그를 포함한 모든 데이터는 로컬 머신의 127.0.0.1에 저장됩니다.
어떤 LLM 플랫폼을 지원하나요?
ChatGPT, Grok, X Grok, Claude, GitHub Copilot, Qwen, DeepSeek, Perplexity를 지원합니다.