ThreadSatchel
Supports importing ChatGPT export ZIP archives and capturing local Codex text events into the memory archive, enabling OpenAI conversation and coding-session history to be stored and searched through MCP.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ThreadSatchelfind my earlier notes on the ThreadSatchel database schema"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ThreadSatchel
Keep the thread. Carry the context.
A small, local memory archive that AI assistants can search through MCP. Keep original conversations, notes, and source information in one SQLite database instead of repeatedly explaining the same project in new chats.
Early release. Built and exercised on Windows, with a Linux capture node. It is a personal tool made shareable, not a hosted service or a promise to capture every chat automatically.
What it does
Exposes
search_memoryandget_memorythrough a read-only MCP server.Imports text, Markdown, structured conversation excerpts, and a supported ChatGPT export ZIP shape.
Stores full original text, provenance, source IDs, and revisions; searches with SQLite FTS5.
Captures supported local Codex text events incrementally, without model/API calls.
Can queue capture on several machines and pull it into one archive over existing SSH connections.
Makes repeated imports safe and conservatively reconciles overlapping excerpts.
Related MCP server: LumenCore
Start here
Requires Python 3.12+ with SQLite FTS5. The tested MCP dependency is pinned in requirements.txt.
python -m venv .venv
# Activate .venv using your shell, then:
python -m pip install -r requirements.txt
python setup_memory.py
python import_memory.py examples/example-excerpt.jsonConnect your MCP client to the absolute path of .venv's Python executable, with the absolute path of server_readonly.py as its argument. Ask it to search for sample archive to check the example import. See connection instructions, including Codex configuration.
For optional automatic local capture:
python codex_capture_export.py --config capture-local.json --dry-run
python codex_capture_export.py --config capture-local.json
python install_schedule.py localThe installer is opt-in. Windows uses a limited task while your account is logged in; Linux uses a systemd user timer. See capture and multi-machine setup.
How it fits together
flowchart TD
A["Notes and conversation imports"] --> C["Importer and provenance"]
B["Local Codex capture"] --> C
R["Remote capture queue"] --> S["SSH pull and acknowledgement"]
S --> C
C --> D["SQLite and FTS5"]
D --> M["Read-only MCP tools"]Read before importing your history
Imports and duplicates explains exact IDs, revisions, ambiguous matches, and the ZIP limitation. A real user's complete OpenAI export has not yet been validated; current export tests use synthetic fixtures.
Privacy and security explains retained raw bytes, plaintext storage, capture omissions, and the difference between a read-only endpoint and the optional writable endpoint. Retrieved memories are source material, not instructions to execute.
This does not automatically capture ChatGPT's website or phone app, every Claude conversation, other users' chats, hidden reasoning, or all historic Codex formats. MCP connects an assistant to tools; it does not grant access to its entire chat history.
Development
Run python scripts/check.py for isolated tests. See architecture for the modules and data flow. No embeddings, vector database, paid API key, or model inference are required by this software. Your AI client's normal usage still applies when it retrieves and reads memories.
MIT licensed. Independent project; not affiliated with OpenAI or Anthropic.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory for AI agents. Search, store, and recall across sessions.
Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
Universal memory for AI agents and tools. Save, organize and search context anywhere.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceProvides persistent local memory functionality for AI assistants, enabling them to store, retrieve, and search contextual information across conversations with SQLite-based full-text search. All data stays private on your machine while dramatically improving context retention and personalized assistance.3-
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.3 npmApache 2.0
- AlicenseAqualityBmaintenanceProvides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.81MIT
- AlicenseAqualityBmaintenanceLocal index and hybrid search (SQLite FTS5 + on-device vector KNN) over your AI coding-agent conversation history across 11 tools (Claude Code, Codex, Cursor, and more). Exposes search_threads, search_current_project, recent_threads, get_thread, list_tags, and list_open_todos so any agent can recall its own past work.2240AGPL 3.0