memo-mcp
Personal notes MCP server for Claude Desktop. Save, search, and list notes from inside any Claude conversation. Notes are stored locally in SQLite with full-text search powered by FTS5.
Requires Python 3.11+
Installation
pip install memo-mcp
Claude Desktop setup
Add the following to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"memo": {
"command": "memo-mcp",
"args": ["serve"]
}
}
}
If
memo-mcpis not on your PATH (e.g. installed in a virtualenv), use the full path to the executable, or install with uv and useuvxinstead:{ "mcpServers": { "memo": { "command": "uvx", "args": ["memo-mcp", "serve"] } } }
Restart Claude Desktop after editing the config.
Tools
Once connected, Claude can use three tools:
| Tool | Description |
|---|---|
notes.add |
Save a note (plain text, max 10,000 characters) |
notes.search |
Full-text search across all notes (FTS5 syntax supported) |
notes.list |
List notes newest-first with cursor-based pagination |
Custom database path
By default notes are stored at ~/.memo-mcp/notes.db. Override with the MEMO_MCP_DB_PATH environment variable:
{
"mcpServers": {
"memo": {
"command": "memo-mcp",
"args": ["serve"],
"env": {
"MEMO_MCP_DB_PATH": "/path/to/your/notes.db"
}
}
}
}
Rebuilding the search index
If search results seem incomplete after a crash or manual database edit, rebuild the FTS5 index:
memo-mcp reindex
# Reindexed 42 notes in 0.03s
Pass --db to target a non-default database:
memo-mcp reindex --db /path/to/notes.db
Scheduling nightly reindex
macOS / Linux — add to crontab (crontab -e):
0 3 * * * memo-mcp reindex >> ~/.memo-mcp/reindex.log 2>&1
Windows — run once in an elevated PowerShell to create a daily Task Scheduler job:
schtasks /create /tn "memo-mcp reindex" /tr "memo-mcp reindex" /sc daily /st 03:00 /f
Developer notes
Log level — set MEMO_MCP_LOG_LEVEL=debug to enable verbose structured JSON logging to stderr. Default is info. This is a developer-only knob; normal users do not need to set it.
{
"mcpServers": {
"memo": {
"command": "memo-mcp",
"args": ["serve"],
"env": {
"MEMO_MCP_LOG_LEVEL": "debug"
}
}
}
}
License
MIT
Metadata
Release files for memo-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| memo_mcp-0.1.0.tar.gz | 5.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| memo_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / memo_mcp-0.1.0.tar.gz
| Download URL | memo_mcp-0.1.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e8d92149baf5e3015734140b97a791b4bd0aa741a8f71e613f42ea6e4160412
|
|
BLAKE2b-256 checksum How to use checksums |
76c218548f31e04620a1d6fcd0bc80d624c3120092d18d2e6b90f519426e9d16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logRelease files / memo_mcp-0.1.0-py3-none-any.whl
| Download URL | memo_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d384e256882f60b846d9847a3eeeddf9482ed8c585664668715a5f31aa7c3edf
|
|
BLAKE2b-256 checksum How to use checksums |
a1574c126916b3c7ccc151dfc5d6f2068e0960c2fa2c9ce734abfe75e75a9761
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logSecurity for memo-mcp 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for memo_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logA 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.