Memos MCP Server

A package for Pensieve (previously known as memos)

Local serverstdioPython

What is the Memos MCP server?

A package for Pensieve (previously known as memos). The memos mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

Pensieve is a privacy-focused passive recording project. It can automatically record screen content, build intelligent indices, and provide a convenient web interface to retrieve historical records.

  • 🚀 Simple installation: just install dependencies via pip to get started
  • 🔒 Complete data control: all data is stored locally, allowing for full local operation and self-managed data processing
  • 🔍 Full-text and vector search support
  • 📊 Interactive entity detail view with chronological context navigation
  • 🌐 Smart metadata capture including browser URL retrieval for web activities
  • 🤖 Integrates with Ollama, using it as the machine learning engine for Pensieve

Its toolset

Everything the assistant can do here goes through one of these:

  • postgres — mysecretpassword: Database username and password
  • localhost — 5432: PostgreSQL server address and port
  • builtin_ocr — builtin_vlm
  • idle_timeout — How long (in seconds) the system should wait without activity before entering idle state
  • idle_process_interval — The time window during which skipped files can be processed
  • Configuration — The idle processing behavior can be customized in ~/.memos/config.yaml:

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at memos on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Memos's toolset — postgres, localhost, builtin_ocr and 3 more — is a fair guide to whether it matches your workflow. It is maintained by arkohut; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the memos mcp server does with a few real requests.

Available tools

ToolWhat it does
postgresmysecretpassword: Database username and password
localhost5432: PostgreSQL server address and port
builtin_ocrbuiltin_vlm
idle_timeoutHow long (in seconds) the system should wait without activity before entering idle state
idle_process_intervalThe time window during which skipped files can be processed
ConfigurationThe idle processing behavior can be customized in ~/.memos/config.yaml:

How to install the Memos MCP server

{
  "mcpServers": {
    "memos-1": {
      "command": "uvx",
      "args": ["memos"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Memos to postgres.
  • Use Memos to localhost.
  • Use Memos to builtin ocr.

Frequently asked questions

It connects Memos to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (postgres, localhost, builtin_ocr, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Memos directly.