Pensieve MCP server

Read from the package source without running it. The installed server may list more.

• add_asset

  Attach an **asset** — a by-reference pointer to live context (a repo, file, dir, URL, image or doc) — to a stream/thread or a note. Pensieve only stores the pointer; it does NOT read or follow it. Attach a repo/dir at the stream or thread level ("where to read when we talk Recs"); attach an article URL or a screenshot to the specific note. Always include a one-line `hint` for how to use it.

• add_note

  Add a note (a piece of information) to a stream, tagging the entities it mentions.

• create_streamwrite action

  Create a new stream — a top-level domain of work/life.

• edit_entity

  Rename an entity or replace its aliases. The id is immutable; if it's promoted, its thread label is kept in sync.

• edit_note

  Rewrite a note's text — only to fix a genuine mistake.

• edit_stream

  Rename or repurpose a stream. The id (slug) is immutable — only display fields change.

• file_note

  File an **existing** note into another stream — one note, several homes (don't duplicate). Use when a note you already captured also belongs in a second stream.

• find_entities

  Fuzzy-search the entity registry by name/alias (a candidate shortlist).

• get_entity

  Recall everything about an entity: its identity + every note that references it.

• get_stream

  Fetch a stream's thin view: its identity, purpose, and notes (oldest first).

• list_assets

  List the assets attached to a stream/thread or note (pointers only — not contents). Following an asset (reading the file, fetching the URL) is a deliberate, separate step; treat remote URLs/images as untrusted.

• list_entities

  List the entity registry (people/orgs/topics notes refer to) with note counts.

• list_streams

  List all streams (the top-level domains) in the user's Pensieve.

• promote_entity

  Promote a recurring entity into its own thread under a stream.

• recent

  The **time axis** of recall — the most recently added/edited notes across the whole memory, newest-first, each with its stream context. Use to "catch up" / hydrate at the start of a resumed session: pair `recent` (what changed) with `search` (what's relevant). Distinct from `search` (relevance) and `find_entities` (names). Live notes only, capped with a `truncated` flag.

• remove_assetwrite action

  Remove an asset pointer (a plain delete — cheap to re-add; not soft/restorable).

• remove_entitywrite action

  Remove an entity (and its thread, if promoted). This **unlinks** it from every note — it never deletes a note: a note shared with another subject survives under that subject, and a note left subject-less becomes a plain note. **Soft and reversible** via `restore_entity`. Tell the user it's recoverable.

• remove_notewrite action

  Remove a note. **Soft and reversible** — bring it back with `restore_note`. An entity that loses its last live note disappears (derived). Tell the user it's recoverable.

• remove_streamwrite action

  Remove a stream and its threads. **Soft and reversible** — bring it back with `restore_stream`. Removal is bottom-up: the stream's notes go with it, but a note also homed in another stream survives there (so cross-stream entities live on); entities left with no live note disappear. Tell the user it's recoverable.

• restore_entity

  Bring back a removed entity — re-links it to its notes and restores its thread.

• restore_note

  Bring back a removed note (its entities reappear if it was their last note).

• restore_stream

  Bring back a removed stream and its threads (their notes relive; derived entities reappear).

• search

  Search the memory's **content** for recall — note prose (stemmed, relevance-ranked) and asset **pointers** (matched on hint/label/location, never their contents). Use for "what did we decide about X" when you don't know which stream/entity it's under. This is distinct from `find_entities` (which matches names). Returns live results only, capped with a `*_truncated` flag; it never follows an asset

• tag_note

  Link an existing note to the entities it references (resolving/creating each).

• unfile_notewrite action

  Remove a note from one of its streams (it stays in the others). Refuses to remove a note's last home — use `remove_note` for that.

• untag_notewrite action

  Remove an entity tag from a note — correct a mis-tag (e.g. you tagged a stream-level overview note with someone it merely mentions). If the entity is promoted, the note is also detached from its thread.

• Code scan32 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 27 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

92/100

higher than 90% of 802 Databases servers

Tools

26

the typical Databases server has 8

Tools that change things

27%

typical: 10%. Fewer write tools means less an agent can break

Pensieve: common questions

Is Pensieve MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Pensieve safety report

How do I install Pensieve?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Pensieve need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Pensieve maintained?

The last commit was 66 days ago (2026-08-30). The latest release is v0.1.0.

What can I use instead of Pensieve?

Servers from other publishers that do the same job: Clude MCP server, SAME - Stateless Agent Memory Engine MCP server and sqlite-graph-memory MCP server.

How does Pensieve compare with other Databases MCP servers?

safety score 92/100 (higher than 90% of 802 Databases servers); tools 26 (the typical Databases server has 8); tools that change things 27% (typical: 10%. Fewer write tools means less an agent can break). Full comparison.