MemoryStar
Provides persistent, searchable project knowledge for GitHub Copilot coding agents, enabling memory save, search, and synchronization across sessions.
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., "@MemoryStarsave design decision about using FastAPI"
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.
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
Related MCP server: local-memory-mcp
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.mdOption 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.txtCopy examples/dev-cursor.mcp.json → .cursor/mcp.json (or VS Code equivalent — see examples/README.md).
python server.pyMCP tools (overview)
Category | Tools |
Core |
|
Graph |
|
Files |
|
Hooks |
|
Orchestration |
|
Git |
|
Watcher |
|
Progress |
|
Changelog |
|
Maintenance |
|
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 dashboardConfiguration
Key environment variables (set in .cursor/mcp.json or .vscode/mcp.json):
Variable | Description | Default |
| Database directory |
|
| Workspace root to watch | — |
| Sync on MCP startup |
|
| Background file watcher |
|
| Dashboard port |
|
| Per-feature toggles | all |
See README configuration section below for full list.
Feature toggles
Flag | Tools |
| save, load, update, search |
| file scan, symbols, change hooks |
|
|
| 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 scriptsBuilding the Windows installer
cd dist
.\build.ps1Produces 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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory for AI agents. Semantic search, memory graph, W3C DID identity.
An MCP memory server. One memory your agents share — across models, devices and apps.
Persistent, portable memory for AI assistants — your private memory graph, from any MCP client.
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server providing persistent memory for AI coding assistants by storing and searching architectural decisions, patterns, and solutions. It also includes tools for git automation and mapping codebase expertise based on project history.MIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that provides semantic memory storage and retrieval for coding and AI agents, enabling durable context across chat sessions.49 npm4-
- AlicenseNot gradedqualityDmaintenanceA local-first MCP memory server that gives AI coding agents persistent memory with hybrid semantic and keyword retrieval, working fully offline.18 npm199MIT
- AlicenseAqualityDmaintenanceMCP server that provides a shared semantic memory layer for AI coding agents, enabling teams to store, search, and sync context, decisions, and knowledge across projects with project-based isolation and multi-backend support.141MIT