Aimemo
About
# aimemo [](https://golang.org/) [](LICENSE)…
Details
- Author
- MyAgentHubs
- GitHub stars
- 1
- Downloads
- 254
- Categories
- Other, AI
Jump to
- Single binary, no Docker, Node.js, cloud, or API keys.
- Memory stored in .aimemo/ next to project code, portable across branches.
- Auto-loads prior context via memory_context tool at session start.
- Full-text search using SQLite FTS5 with BM25 scoring (recency + frequency).
- Concurrent writes supported via SQLite WAL mode.
- Full CLI control: inspect, edit, retract, export Markdown or JSON.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
AimemoCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via one-line curl script or Homebrew, then run aimemo init in the project root. Register the MCP server with claude mcp add-json aimemo-memory '{"command":"aimemo","args":["serve"]}' and restart Claude Code – the server loads automatically on each session.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"aimemo": {
"aimemo": {
"command": "aimemo",
"args": []
}
}
}
}McpServers
{
"aimemo": {
"command": "aimemo",
"args": []
}
}aimemo
Zero-dependency MCP memory server for AI agents — persistent, searchable, local-first, single binary.
$ claude "let's keep working on the payment service"
╭─ memory_context ──────────────────────────────────────────────────╮
│ [project: payment-service] │
│ │
│ Last session (3 days ago): │
│ • Stripe webhook signature verification — DONE │
│ • Idempotency key refactor — IN PROGRESS │
│ • Blocked: race condition in concurrent refund handler │
│ │
│ Related: Redis connection pool, pkg/payments/refund.go │
╰───────────────────────────────────────────────────────────────────╯
Picking up where we left off. The race condition in the refund
handler looks like a missing mutex around the in-flight map.
Let me check pkg/payments/refund.go ...
[... Claude works through the fix ...]
╭─ memory_store (journal) ──────────────────────────────────────────╮
│ Resolved refund race — added sync.Mutex around inFlightRefunds. │
│ Tests passing. Next: load test with k6 at 500 rps. │
╰───────────────────────────────────────────────────────────────────╯
🧠 Why aimemo
- No infra to babysit. Single Go binary. No Docker, no Node.js runtime, no cloud account, no API keys. brew install in 30 seconds.
- Memory stays with the project. Stored in .aimemo/ next to your code — commit it to git or add it to .gitignore. Switch branches; memory follows the directory.
- Claude picks up exactly where it left off. memory_context fires automatically on every session start. Claude sees what it was doing, what was blocked, what decisions were made. You stop repeating yourself.
- Full-text search that ranks correctly. FTS5 + BM25 scoring weighted by recency and access frequency. Relevant memories surface first; old noise fades naturally.
- Concurrent sessions, no corruption. SQLite WAL mode lets multiple Claude windows write simultaneously without locking each other out.
- You stay in control. Every tool Claude has, you have from the terminal. Inspect, edit, retract, export. Your memory is readable Markdown or JSON — never locked in a proprietary format.
⚡ Quick Start
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
