Make0 Brain
OfficialRelated Servers
Alternatives to Make0 Brain
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent memory directly during sessions, storing decisions, preferences, error patterns, research, and cross-project guidelines in local SQLite databases. Supports semantic search so relevant project and global context can be recalled by meaning, fully offline and without API keys.-
- AlicenseNot gradedqualityBmaintenanceLocal memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.4Business Source 1.1
- AlicenseNot gradedqualityBmaintenanceEnables AI agents like Codex, Grok Build, and Antigravity to share persistent local memory, preferences, project context, tasks, and handoffs using Markdown and SQLite.1MIT
- FlicenseAqualityBmaintenanceRuns locally on your Mac to give AI agents a shared, private memory of your profile, notes, projects, and saved web pages, with semantic search and version history.31-
- AlicenseAqualityBmaintenanceGives AI agents persistent, local-first memory using SQLite and on-device embeddings, enabling semantic search and recall across sessions with no cloud calls.823 PyPI9MIT
- AlicenseAqualityBmaintenanceLocal, private memory for coding agents: facts tied to files, reusable skills and a task board that persist across sessions. One SQLite file on your machine.16410 npmMIT
TDQS
Scored across 7 tools
Each tool has a distinct, non-overlapping purpose: create, update, delete, read, read-history, search, and list-brains. The descriptions explicitly clarify boundaries, e.g. get_memory vs. get_memory_versions and list_brains vs. search_brain. An agent can select confidently in nearly all cases.
Six of seven tools follow a clean verb_noun pattern (add_memory, update_memory, delete_memory, get_memory, get_memory_versions, search_brain). The noun is inconsistent, though: 'brain' appears in search_brain (which searches memories) and list_brains (which lists brains, not memories), a minor naming trap.
Seven tools is well-scoped for a memory store: full CRUD, version history, search, and brain listing. Every tool earns its place with no redundancy.
Create/read/update/delete plus version history, search, and brain discovery cover the core lifecycle well. The main gap is restore, which is only available via CLI (`npx @make0-ai/brain restore`), and there's no direct 'list all memories' fallback beyond search.