keepsake-mcp is the MCP server for Keepsake (keepsake.place). Keepsake is described as an app for creators and independent entrepreneurs that helps them "clear their mind": gathering and connecting ideas, tasks, and important people in one place, all the way through to publishing.
Purpose Through this MCP server, users can connect an AI assistant (Claude, Cursor, or any MCP-compatible client) to their own Keepsake data, covering contacts, interactions, tasks, notes, daily intentions, companies, and tags. The official description states that AI assistants forget between different conversations, while Keepsake remembers.
Main capabilities Examples of actions the AI assistant can perform include: capturing an idea to the #newsletter# tag, querying who was recently contacted at Acme Corp, adding a note about meeting Sarah at a conference, viewing which tasks are overdue, showing everything related to the #house-project tag, and creating a follow-up task for next week's meeting with John. The server provides a total of 88 tools, covering entries (interactions), note comments (margin notes), days (daily intentions or questions), day blocks (journal view timeline), recurring blocks (ideal day/ideal week, habits), task headers (sections), contact and company associations, and more. Note comments are used to keep material alongside a note without entering the body text, can be anchored to a specific paragraph or the entire note, and by design are temporary and never published; content worth keeping should be turned into a note or an associated task.
How to use First register at keepsake.place, then go to Account > API Keys to generate an API Key. There are two ways to connect:
- Remote method, no installation required, suitable for Claude iOS, Claude Web, Claude Desktop Connectors, and any MCP client that supports Streamable HTTP. The endpoint is https://app.keepsake.place/api/mcp，认证方式为在 Pass the API Key as a Bearer token in the Authorization request header. When adding a remote MCP server in Claude Desktop settings, enter that URL and use the API Key starting with ksk_ as the Bearer token.
- Local method, run via npx, suitable for Claude Code, Cursor, and local development. For Claude Desktop, add the configuration in ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows, then set KEEPSAKE_API_KEY in the environment. For Cursor, add the configuration in .cursor/mcp.json in the project.
Server instructions When connecting, the server sends MCP instructions, which are injected into the client's system prompt. The official description states that this is the only channel the agent can reach before looking for capabilities, so keep it brief and point to the rest: call get_agent_instructions for the full guidelines, and put editorial remarks in the note's margin notes (create_note_comment) rather than in chat, where they will disappear. The official recommendation is to call get_agent_instructions at the start of each session to get the full best-practices guide.
Safety annotations and activity logging All tools include MCP safety annotations: read-only tools (list_, get_, search_*) are marked readOnlyHint: true; create tools are marked destructiveHint: false; update tools are marked destructiveHint: false, idempotentHint: true; delete tools are marked destructiveHint: true, idempotentHint: true. Every write operation performed through the API (create, update, delete) is recorded in the user-visible Activity Feed within Keepsake, showing the entity type, content preview, and usagewhich API Key. The official notice states that users can see all operations, so transparency and precision should be maintained; if an error occurs, the user should be informed so they can verify it in the activity stream.
Limitations and data notes The rate limit is 60 requests per minute per API Key, and responses include rate limit headers. The explanations related to environment variables are not fully expanded in the official text; it only mentions that KEEPSAKE_API_KEY needs to be set. The complete REST API documentation is located at keepsake.place/api. The official statement says that the Keepsake MCP server communicates only with the Keepsake API (app.keepsake.place), does not send data to any third-party services, and that data remains between the user's MCP client and Keepsake account; all API calls are authenticated using a personal API Key and are scoped to the user's account through Row Level Security, making it impossible to access other users' data. The privacy policy is at keepsake.place/privacy.