MCP server

Keepsake runs a Model Context Protocol server, so an assistant such as Claude can search your library and read the pages you kept while it helps you. Every tool only reads, so an assistant connected through it can never save, edit, or delete anything.

Connect an assistant

Add Keepsake to your assistant as a remote MCP server at this address:

https://mcp.keepsake.run/mcp

The first time the assistant connects, it opens Keepsake in your browser:

1. Sign in if you are not already.
2. Keepsake names the assistant asking and the site its key will be sent to, so check both are what you expect.
3. Choose Approve to connect it, or Cancel to refuse.

Only approve an assistant you started connecting yourself, and only in the browser where you started it, since an approval given anywhere else is refused.

What it can do

Tool	What it does	Changes anything
search	Searches titles, notes, tags, and archived page text, and returns each match with a snippet.	no
list_bookmarks	Lists bookmarks newest first, optionally narrowed to one tag or to read-later, failed archives, or dead links.	no
get_bookmark	Gets one bookmark's link, title, notes, tags, and archive status.	no
read_archive	Reads the archived text of a bookmark's page as Markdown.	no
list_tags	Lists every tag with how many bookmarks carry it.	no

An assistant usually starts with search or list_bookmarks and then calls read_archive on what it found. A refusal Keepsake can explain, such as a bookmark with no archive yet, comes back to the assistant as the tool's answer, so it can tell you what to change.

Disconnect an assistant

Approving an assistant gives it a key named MCP: followed by the assistant's name, listed under Settings, then API tokens. Delete that key and the assistant loses access at once, and the next time it tries, it asks you to connect again. Requests through the MCP server count toward the same rate limit as the REST API.