1. Conduid
  2. Data
  3. Memo
MCP server · Data

Memo

CLI notes tool with markdown, tags, SQLite storage, and MCP server for AI integration

Unclaimed last commit 6 months ago data
48Fair

Scored 3 hours ago · breakdown

About Memo

Memo is an MCP server published by harperreed in the Data category: cLI notes tool with markdown, tags, SQLite storage, and MCP server for AI integration. It has been installed 0 times through Conduid.

The repository has 1 stars and 0 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx memo

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Memo

Powered by Claude · Grounded in docs

I know everything about Memo. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.11.2v0.11.2 · 10 Feb 2026Changelog Bug fixes 70a0685f086768638693e1166ab97f8e26f20d2e: fix(deps): use published mdstore module, remove local replace (@harperreed)
v0.10.0v0.10.0 · 1 Feb 2026Changelog Features 6130d4af025000c2cb5d4c804f938fd06f6d08cf: feat: add stale sync support using charm v0.19.0 (@harperreed) Other 094fa33e954f4b9ef08fd50aefc3d74ba1dc5644: chore(deps): update charm to v0.20.0 (@harperreed)…
v0.9.5v0.9.5 · 24 Dec 2025Changelog Other a084e578f2afdec46c732ba6ccf4da318a939f5f: refactor: remove dead code from Do API migration (@harperreed)
v0.9.4v0.9.4 · 23 Dec 2025Changelog Features df3e31ef2c62a77fc4bb53c4ada134f12c5d195e: feat: add sync repair, reset, and wipe commands using charm v0.17.0 (@harperreed)
v0.9.3v0.9.3 · 21 Dec 2025Charm v0.15.4 update

README

memo

A command-line notes tool that stores markdown notes with tags and attachments. Supports SQLite and markdown file backends.

Features

  • Markdown-first: Notes are stored as markdown with full formatting support
  • Tags: Organize notes with multiple tags
  • Attachments: Attach files to notes (stored as blobs in SQLite)
  • Full-text search: FTS5-powered search across titles and content
  • Beautiful output: Rendered markdown in the terminal
  • MCP Server: Built-in Model Context Protocol server for AI assistant integration
  • Portable: Single SQLite database file, XDG-compliant storage

Installation

Homebrew (macOS)

brew install harperreed/tap/memo

From source

go install github.com/harperreed/memo/cmd/memo@latest

Download binary

Download from GitHub Releases.

Usage

Add a note

# Open $EDITOR to write content
memo add "Meeting Notes"

# Inline content
memo add "Quick thought" --content "Remember to call mom"

# From file
memo add "Article Draft" --file draft.md

# With tags
memo add "Project Ideas" --content "..." --tags "work,brainstorm"

List notes

# List recent notes
memo list

# Filter by tag
memo list --tag work

# Search
memo list --search "meeting"

# Limit results
memo list --limit 5

View a note

# Use ID prefix (6+ characters)
memo show abc123

Edit a note

memo edit abc123

Delete a note

memo rm abc123

# Skip confirmation
memo rm abc123 --force

Manage tags

# Add tag to note
memo tag add abc123 important

# Remove tag
memo tag rm abc123 important

# List all tags
memo tag list

Directory-aware notes

# Tag a note with the current directory
memo add "Project TODO" --content "..." --here

# List notes tagged with the current directory
memo list --here

Attachments

# Attach a file
memo attach abc123 document.pdf

# Extract attachment
memo attach get def456 --output ./downloads/

Export/Import

# Export all notes to JSON
memo export --format json --output backup.json

# Export to markdown directory
memo export --format md --output ./notes/

# Import from JSON
memo import backup.json

# Import markdown files
memo import ./notes/

MCP Server

Start the MCP server for AI assistant integration:

memo mcp

Add to your Claude desktop config (~/.config/claude/claude_desktop_config.json):

{
  "mcpServers": {
    "memo": {
      "command": "memo",
      "args": ["mcp"]
    }
  }
}

Available MCP Tools

Tool Description
add_note Create a new note
list_notes List notes with optional filtering
get_note Get a note by ID
update_note Update note title or content
delete_note Delete a note
search_notes Full-text search
add_tag Add tag to note
remove_tag Remove tag from note
add_attachment Add attachment (base64)
list_attachments List note attachments
get_attachment Get attachment content
export_note Export note as JSON or markdown

Storage

memo supports two storage backends:

  • Markdown (default for new users): Notes stored as markdown files in ~/.local/share/memo/
  • SQLite: Notes stored in ~/.local/share/memo/memo.db

Configure the backend in ~/.config/memo/config.json:

{
  "backend": "markdown",
  "data_dir": "~/.local/share/memo"
}

Use memo migrate --to markdown or memo migrate --to sqlite to switch backends.

Building

# Build
make build

# Run tests
make test

# Run tests with race detector
make test-race

# Run linter
make lint

# Run all checks
make check

License

MIT

README mirrored from the source repository 3 hours ago. The original is authoritative.

Questions

About Memo

How do I install Memo?

Run npx memo, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Memo safe to use with an AI agent?

Its trust score is 48 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Memo still maintained?

The last commit was 6 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.