watashi-db
Enables optional snapshot sync to Google Drive for multi-device synchronization.
Provides an optional embedding provider that sends record summaries to OpenAI's embedding API for semantic search.
Click on "Install 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., "@watashi-dbrecall our decision on 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.
watashi-db
Personal context database you own. AI tools connect to it — not the other way around.
v0.x is early-stage. APIs and data structures may have breaking changes.
All data is stored locally (~/.watashi-db/default.db). Nothing is sent externally
(unless you explicitly opt in to the OpenAI embedding provider, which sends record summaries to the embedding API).
What is watashi-db?
Every time you start a new AI session, you start from zero — re-explaining your preferences, your tech stack, your past decisions. The AI is smart but knows nothing about you.
watashi-db fixes this. It's a local database that accumulates your preferences, decisions, and experiences, then serves them to any MCP-compatible AI tool at session start.
The AI stays stateless. You gain continuity.
Before / After
Before | After | |
Session start | "I use TypeScript, prefer Japanese comments, and…" (every time) | AI loads your profile automatically via |
Past decisions | "I think we decided on X last week…" (from memory) |
|
Lessons learned | Lost between sessions | Episodes distill into reusable Insights over time |
Multi-tool | Each AI tool has its own silo | One database, any MCP client |
Related MCP server: engram
Who is this for?
Developers who use MCP-compatible AI tools (Claude Code, Codex CLI, Antigravity, Claude Desktop, etc.) daily and want their AI to remember context across sessions — without handing their data to a vendor.
Key Features
Zero-effort recording — AI records your preferences, decisions, and experiences in the background during normal conversation. You don't write anything manually.
Experience distillation — Raw episodes are refined into reusable Insights, Models, and Theories over time (
/groom). Not just a memo database.Fully local — SQLite + FTS5. No cloud, no external calls by default (the optional OpenAI embedding provider is opt-in). Your data stays on your machine.
Vendor-neutral — Any MCP client can connect. Switch AI tools without losing context.
Auditable — Every write is logged (who, what, why). Changes are retracted, never deleted.
Multi-device sync — Optional snapshot sync via Google Drive or any cloud storage.
Quick Start
Step 1: Register the MCP server
# Claude Code
claude mcp add --scope user watashi-db -- npx -y watashi-db@latest
# Codex CLI
codex mcp add watashi-db -- npx -y watashi-db@latestAdd to Antigravity's mcp_config.json (CLI: ~/.gemini/antigravity-cli/mcp_config.json, IDE: ~/.gemini/antigravity/mcp_config.json — open via Manage MCP Servers → View raw config):
{
"mcpServers": {
"watashi-db": {
"command": "npx",
"args": ["-y", "watashi-db@latest"]
}
}
}Add to claude_desktop_config.json:
{
"mcpServers": {
"watashi-db": {
"command": "npx",
"args": ["-y", "watashi-db@latest"]
}
}
}Step 2: Set up hooks and skills (Claude Code)
npx watashi-db setupRestart Claude Code. That's it.
Hooks auto-remind the AI to record decisions and experiences during conversation
@nolog prefix on any prompt skips recording for that message
/recall searches your past decisions, preferences, and experiences
Alternative: Plugin Marketplace (Claude Code)
If you use Claude Code, you can install everything (MCP server, hooks, skills, agents) in one step via the plugin marketplace — with automatic updates:
/plugin marketplace add bareforge/watashi-db
/plugin install watashi-db@watashi-dbThis is equivalent to Steps 1-2 above but uses Anthropic's plugin system.
@latest ensures the latest version is used on every client restart.
For detailed setup (multi-device sync, Codex CLI policies, Cowork plugin, building from source), see the Setup Guide.
How It Works
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Claude Code │ │ Codex CLI │ │ Antigravity │ │ Any MCP │
│ (MCP Client) │ │ (MCP Client)│ │ (MCP Client)│ │ Client │
└──────┬───────┘ └──────┬──────┘ └──────┬──────┘ └──────┬──────┘
└─────────────────┼─────────────────┘
│ MCP (stdio)
┌─────────▼─────────┐
│ watashi-db │
│ (MCP Server) │
│ │
│ SQLite + FTS5 │
│ ~/.watashi-db/ │
└────────────────────┘You work normally. AI records your preferences, decisions, and experiences in the background.
Old records fade. Entries naturally lose search priority over time — no manual cleanup needed.
You run
/groomoccasionally. This distills recurring patterns into lasting Insights, so valuable lessons survive while noise disappears.
That's it. No entity types to learn, no manual tagging. Just use your AI tools and let watashi-db build your context over time.
How is this different?
Approach | Limitation | watashi-db's answer |
CLAUDE.md / .cursorrules | Static instructions, manually maintained | Dynamic experience memory, auto-recorded by AI |
ChatGPT Memory / Claude Projects | Vendor-locked, opaque, no export | You own the SQLite file. Any MCP client can read it |
Obsidian + MCP | General-purpose notes, no structured experience model | Purpose-built for decisions, episodes, and distillation |
Mem0 / Zep | Cloud-dependent memory layers | Fully local, zero external dependencies |
watashi-db is complementary to CLAUDE.md — static rules go in CLAUDE.md, evolving experience goes in watashi-db.
Documentation
Document | Description |
Installation, multi-device sync, Cowork plugin | |
All | |
Philosophy: the statelessness problem in AI collaboration |
Document | Description |
How data is classified (Claim → Episode → Insight → Model) | |
Architectural decisions and review criteria (Japanese) | |
Theoretical foundation: structured reasoning languages (Japanese) | |
Data model; canonical logical names are in the A5:SQL Mk-2 file (not viewable on GitHub; requires A5:SQL Mk-2) |
Development
git clone https://github.com/bareforge/watashi-db.git && cd watashi-db
npm install && npm run build
npm testLicense
Personal / non-commercial / educational / evaluation use: Always free
Commercial use: License required (bareforge.license@outlook.jp)
Change Date: After 2029-03-16, automatically converts to Apache License 2.0
Versions v0.0.12 and earlier were published under MIT License. If you obtained an MIT-licensed version, you may continue using that version under MIT terms.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides persistent personal context (identity, projects, decisions, knowledge) to MCP-compatible AI tools, eliminating the need to re-explain yourself across sessions.Last updated2391MIT
- Alicense-qualityCmaintenanceProvides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.Last updated1MIT
- Alicense-qualityAmaintenanceLocal persistent memory for AI coding tools. Stores project context and conversation recall locally via MCP.Last updated1814MIT
- AlicenseAqualityBmaintenanceA local-first MCP server for shared memory across AI tools, enabling context capture and resume across sessions.Last updated26443Apache 2.0
Related MCP Connectors
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bareforge/watashi-db'
If you have feedback or need assistance with the MCP directory API, please join our Discord server