MemoryBase
The project operating system for AI agents.
MemoryBase gives your AI coding assistants a shared memory and task system. Agents read your project blueprint, update task statuses, record decisions, and coordinate with each other — all through a standardised MCP interface.
Key Features
- 17 MCP tools — projects, blueprints, tasks, vault — works with Claude Code, Cursor, and any MCP-compatible client
- Real-time Kanban board — drag-and-drop tasks, live updates via Server-Sent Events when agents make changes
- Blueprint editor — structured project definition with in-place editing (tech stack, folder layout, API specs, constraints)
- Vault explorer — searchable, filterable log of decisions, error patterns, and architectural notes
- Zero-config defaults — SQLite out of the box; PostgreSQL for production
- Single Docker image — frontend and backend ship together
Quick Start (pip)
pip install memorybase
memorybase --port 8000
Open http://localhost:8000 — that's it.
Quick Start (Docker)
# 1. Run MemoryBase
docker run -p 8000:8000 \
-v $(pwd)/data:/app/data \
-e MEMORYBASE_API_KEY=my-secret-key \
ghcr.io/sabbiramin113008/memorybase:latest
# 2. Open in browser
open http://localhost:8000
That's it. SQLite data is persisted in ./data.
Quick Start (Local Dev)
# Clone
git clone https://github.com/sabbiramin113008/memorybase.git
cd memorybase
# Start backend (creates venv, installs deps, starts with --reload)
./start-backend.sh
# In a second terminal — start frontend dev server
./start-frontend.sh
- Backend: http://localhost:8000
- Frontend: http://localhost:5273
- API Docs: http://localhost:8000/docs
MCP Configuration
Connect any MCP-compatible AI agent to MemoryBase:
Claude Code / Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"memorybase": {
"type": "sse",
"url": "http://localhost:8000/mcp/sse"
}
}
}
Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"memorybase": {
"url": "http://localhost:8000/mcp/sse"
}
}
}
Your agent can now call tools like list_projects(), get_blueprint(), create_task(), update_task_status(), add_vault_entry(), and more. See MCP Tools Reference.
Screenshots
Kanban board screenshot — coming soon
Tech Stack
| Layer | Technology |
|---|---|
| Backend | Python 3.11, FastAPI, SQLModel, SQLite / PostgreSQL |
| Real-time | Server-Sent Events (sse-starlette) |
| Agent Protocol | MCP (FastMCP) |
| Frontend | React 18, Vite, Tailwind CSS v3, shadcn/ui |
| State | React Query, Zustand |
| Routing | React Router v6 |
| Drag & Drop | @dnd-kit/core |
| Docs | MkDocs Material |
Project Structure
memorybase/
├── backend/ # FastAPI app, SQLModel models, MCP tools, routers
├── frontend/ # React + Vite + Tailwind frontend
├── docs/ # MkDocs documentation source
├── tests/ # pytest smoke tests
├── Dockerfile # Multi-stage build (node → python)
├── docker-compose.yml
├── start-backend.sh # Dev convenience script
└── start-frontend.sh # Dev convenience script
Contributing
See CONTRIBUTING for dev setup, project structure, and how to add new MCP tools.
License
MIT © sabbiramin113008
Metadata
Release files for memorybase 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| memorybase-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for memorybase-0.1.2-py3-none-any.whl |
Release files / memorybase-0.1.2-py3-none-any.whl
| Download URL | memorybase-0.1.2-py3-none-any.whl |
|---|---|
| Size | 188.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed47f17e12fe4b0a6e316d6b20cf3dc4f6b48abc12a59ff70e3dde1f41a91f27
|
|
BLAKE2b-256 checksum How to use checksums |
c86617a5e96f62b90470a9febc21d392fab6dc3787c2e5877510017c8626223f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.7
|
Security for memorybase 0.1.2
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.