MemoryStar
A local semantic memory MCP server for AI coding agents that provides persistent, searchable project knowledge including architecture notes, file symbols, git history, progress tracking, and a knowledge graph, all stored locally.
README
MemoryStar
Local semantic memory MCP server for AI coding agents — Cursor, VS Code / GitHub Copilot, and OpenCode.
MemoryStar gives your agent persistent, searchable project knowledge: architecture notes, file symbols, git history, progress tracking, and a knowledge graph — all stored locally (SQLite + ChromaDB).
Repository: github.com/ussdeveloper/memory-star
License: MIT
Author: Przemyslaw Lusina
Features
- 33 MCP tools — save, search (FTS5 + vectors), link, archive, sync, and more
- Per-file tracking — SHA256 change detection, symbol extraction, descriptions
- Knowledge graph — relationships between memories (
depends_on,implements, …) - Auto-sync — background watcher + Cursor hooks after every edit
- Web dashboard — graph view, browse, semantic search (
http://127.0.0.1:7988) - Windows installer — one-click setup into any project folder
- Privacy-first — all data stays on your machine
Quick start
Option A — Install into your project (Windows)
- Download or build
dist/MemoryStar-Setup.exe(see dist/README.md) - Requires Python 3.10–3.13 on PATH
- Run the installer → pick project folder → pick IDE
- Open project in IDE → Reload Window
- Dashboard: http://127.0.0.1:7988
Installed layout:
your-project/
.memorystar/ # server, venv, database
data/ # SQLite + ChromaDB
server.py
.venv/
.cursor/mcp.json # or .vscode/mcp.json
AGENTS.md
Option B — Run from source (this repo)
git clone https://github.com/ussdeveloper/memory-star.git
cd memory-star
python -m venv .venv
.venv/Scripts/activate # Windows
pip install -r requirements.txt
Copy examples/dev-cursor.mcp.json → .cursor/mcp.json (or VS Code equivalent — see examples/README.md).
python server.py
MCP tools (overview)
| Category | Tools |
|---|---|
| Core | memory_save, memory_load, memory_update, memory_search, memory_archive |
| Graph | memory_link, memory_get_links |
| Files | memory_update_file_structure, memory_get_file_info, memory_list_files |
| Hooks | memory_check_for_changes, memory_process_changes |
| Orchestration | memory_sync_project, memory_suggest_scan |
| Git | memory_git_history |
| Watcher | memory_start_watcher, memory_stop_watcher |
| Progress | memory_track_progress, memory_progress_update, memory_get_progress |
| Changelog | memory_changelog_add, memory_changelog_get, memory_changelog_trends |
| Maintenance | memory_clear, memory_restore, memory_list_backups, memory_stats, memory_trends |
Full tool reference is in the server docstring and AGENTS.md.
Agent workflow (recommended)
Session start → memory_suggest_scan(project_path=".")
After edits → memory_check_for_changes → memory_process_changes (if changed)
Save knowledge → memory_save(key=..., scope="architecture|api|decisions|...")
Before task → memory_search(query=..., mode="combined")
Architecture
Agent (MCP client)
│
├── stdio ── MemoryStar MCP Server (server.py)
│ ├── SQLite + FTS5
│ ├── ChromaDB (vectors)
│ ├── file_structure + memory_links
│
├── HTTP :9120 ── Webhook (watcher, context monitor)
│
└── HTTP :7988 ── UI dashboard
Configuration
Key environment variables (set in .cursor/mcp.json or .vscode/mcp.json):
| Variable | Description | Default |
|---|---|---|
MEMORYSTAR_DATA_DIR |
Database directory | ./data (dev) or .memorystar/data (install) |
MEMORYSTAR_PROJECT_PATH |
Workspace root to watch | — |
MEMORYSTAR_AUTO_SYNC |
Sync on MCP startup | 1 |
MEMORYSTAR_AUTO_WATCH |
Background file watcher | 1 |
MEMORYSTAR_UI_PORT |
Dashboard port | 7988 |
MEMORYSTAR_ENABLE_* |
Per-feature toggles | all 1 |
See README configuration section below for full list.
Feature toggles
| Flag | Tools |
|---|---|
MEMORYSTAR_ENABLE_CORE |
save, load, update, search |
MEMORYSTAR_ENABLE_FILE_STRUCTURE |
file scan, symbols, change hooks |
MEMORYSTAR_ENABLE_SYNC |
memory_sync_project |
MEMORYSTAR_ENABLE_WATCHER |
start/stop watcher |
All flags documented in AGENTS.md.
UI dashboard
Open http://127.0.0.1:7988 when the MCP server is running.
- Browse — memories, files, scopes, project tree
- Graph — force-directed knowledge graph
- Search — semantic + full-text
- Guide — built-in agent instructions
Project structure
memory-star/
server.py MCP server + webhook + UI
database.py SQLite + ChromaDB layer
config.py Environment configuration
ui.html Dashboard (single file)
requirements.txt
AGENTS.md Agent instructions (copy to projects)
examples/ MCP config templates
dist/ Windows installer + build scripts
.cursor/hooks/ Cursor hook scripts
Building the Windows installer
cd dist
.\build.ps1
Produces MemoryStar-Setup.exe and MemoryStar-Windows.zip.
Scopes
Use meaningful scope values when saving memories:
architecture · api · dependencies · patterns · decisions · bugs · notes · file-structure · git-history
Contributing
See CONTRIBUTING.md. Changelog: CHANGELOG.md.
License
MIT © 2026 Przemyslaw Lusina — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。