keepsake-mcp
Keepsake MCP gives an AI assistant authenticated read/write access to a user's Keepsake CRM and productivity workspace, with search, change tracking, and relationship management.
Contacts: list, get, create, update, delete, search, and view a contact's combined entries/tasks/notes timeline.
Companies: list, get, create, update, delete, and search organizations.
Entries: list, create, update, and delete interactions (calls, emails, meetings, etc.), filtered by type/date/contact.
Tasks: list, create, update, delete, complete/uncomplete, snooze, and retrieve today's or overdue tasks.
Notes: list, create, update, delete, pin, archive/restore QuickNotes and Notes.
Days: list, get, and upsert daily journal/day summaries.
Tags: list, get, create, update, delete, fetch tagged items, and link/unlink tags to contacts, entries, tasks, notes, and companies.
Task headers: create and manage section separators for task pages.
Relationships: link/unlink notes to contacts, entries to contacts, tasks to contacts/notes, and notes to notes.
Utilities: global search, changelog since a timestamp, and agent best-practice instructions.
Safety/ops: read-only hints for reads, destructive hints for deletes, Bearer API key auth, and visible activity-feed logging for writes.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@keepsake-mcp Show me my last interaction with John."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
keepsake-mcp
MCP server for Keepsake (keepsake.place), the app where creators and solo entrepreneurs empty their heads: ideas, tasks and the people who matter, together and linked in one place, all the way to publishing.
Connect your AI assistant (Claude, Cursor, or any MCP-compatible client) to your Keepsake data: contacts, interactions, tasks, notes, daily intentions, companies, and tags.
Why
Your AI assistant forgets between conversations; Keepsake remembers. Ask it to:
"Capture this idea for my next article in #newsletter#"
"Who did I last talk to at Acme Corp?"
"Add a note that I ran into Sarah at the conference"
"What tasks are overdue?"
"Show me everything related to the #house-project tag"
"Create a follow-up task for my meeting with John next week"
Related MCP server: Unofficial Dex CRM MCP Server
Quick start
1. Get your API key
Sign up at keepsake.place, then go to Account > API Keys to generate one.
2. Choose your connection method
Option A: Remote (HTTP) — recommended
No installation required. Works with Claude iOS, Claude web, Claude Desktop Connectors, and any MCP client that supports Streamable HTTP.
Endpoint: https://app.keepsake.place/api/mcp
The official MCP registry entry (server.json) publishes this URL as a streamable-http remote, plus the project title and website. The npm package version stays on the release that was published; the registry entry version is the version field of server.json.
Authentication: Pass your API key as a Bearer token in the Authorization header.
Claude Desktop (Connectors):
Add a remote MCP server in Claude Desktop settings with:
URL:
https://app.keepsake.place/api/mcpAuthentication: Bearer token with your
ksk_API key
Any MCP client (Streamable HTTP):
{
"mcpServers": {
"keepsake": {
"type": "streamable-http",
"url": "https://app.keepsake.place/api/mcp",
"headers": {
"Authorization": "Bearer ksk_YOUR_API_KEY"
}
}
}
}Option B: Local (stdio)
Runs locally via npx. Useful for Claude Code, Cursor, and local development.
Claude Desktop:
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"keepsake": {
"command": "npx",
"args": ["-y", "keepsake-mcp"],
"env": {
"KEEPSAKE_API_KEY": "ksk_YOUR_API_KEY"
}
}
}
}Claude Code:
claude mcp add keepsake -- npx -y keepsake-mcpThen set KEEPSAKE_API_KEY in your environment.
Cursor:
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"keepsake": {
"command": "npx",
"args": ["-y", "keepsake-mcp"],
"env": {
"KEEPSAKE_API_KEY": "ksk_YOUR_API_KEY"
}
}
}
}Server instructions
On connection, the server sends MCP instructions — injected into the client's system
prompt. It is the only channel that reaches an agent before it goes looking for a
capability, so it stays short and points at the rest: call get_agent_instructions for
the full doctrine, and put editorial remarks in a note's margin (create_note_comment)
rather than in the chat, which disappears.
Prompts (1)
Prompt | Arguments | Description |
|
| Act as the editor of a note: read it, judge form and substance, leave anchored remarks in the margin, never rewrite the text |
Available tools (96)
Contacts
Tool | Description |
| List contacts with pagination, sorting, field selection and filters (linked company, has_company, updated_since) |
| Get a contact with recent interactions, tags, and stats |
| Create a new contact ( |
| Update contact fields |
| Permanently delete a contact |
| Accent-insensitive search by name, email, notes, phone and linked company names |
| Unified chronological feed of all items for a contact |
Companies
Tool | Description |
| List all companies |
| Get company with linked contacts and tags |
| Create a new company |
| Update company fields |
| Soft-delete (or permanent delete) a company |
| Accent-insensitive company search |
| Link a contact to a company (optional role) |
| Remove a contact–company link |
| Merge a duplicate company into another (contacts, entries, tags, details, notes) |
Entries (Interactions)
Tool | Description |
| List interactions (calls, emails, meetings, etc.) — filter by type, contact, company, page ( |
| Log a new interaction — supports |
| Update an interaction |
| Delete an interaction |
Tasks
Tool | Description |
| List tasks — filter by status, date, company, page ( |
| Get a task with its tags, contacts, companies and linked notes |
| Create a task — supports |
| Update task fields |
| Delete a task |
| Mark as completed (auto-creates next occurrence for recurring tasks) |
| Mark as pending again |
| Reschedule to a new date |
| Today's tasks: overdue + due today + ASAP |
| Only overdue tasks |
QuickNotes
Tool | Description |
| List notes — filter by pinned/archived, day, company, page ( |
| The stages of the user's publication flow (Idea → In progress → To review → Ready → Published by default — the user can rename, add or remove them) |
| Get one note by ID with its tags, contacts, tasks and linked notes |
| Create a note — supports |
| Update note content, links, days, or its publication-flow stage ( |
| Soft-delete (or permanent) |
| Pin as a post-it (short reference always at hand) |
| Unpin a note (it stays where it is) |
| Archive a note |
| Restore a deleted/archived note |
Note comments (marginalia)
Material kept alongside a note without entering its text — an idea, a reference, an excerpt pasted to rewrite a passage later. Anchored to a passage by quoting it, or to the whole note. Never published, and temporary by design: anything worth keeping becomes a note or a linked task.
Tool | Description |
| List the marginalia attached to a note |
| Attach a marginalia to a passage (pass |
| Edit the content of a marginalia |
| Permanently delete a marginalia |
Days (intention or question of the day)
Tool | Description |
| List days with their intention or question of the day (the one in force, which stays until changed), by date range |
| Get a day, its intention in force ( |
| Set a day's intention or question — one short line, not a journal (upsert); it stays in place on the following days until changed |
Day blocks (Day-view timeline)
Tool | Description |
| List a day's time blocks, in timeline order (creates that day's recurring blocks first) |
| Create a block, auto-placed first-fit (or pinned via anchor_time) |
| Update a block (title, duration, anchor, note, done) |
| Delete a block and prune its timeline ref (on a recurring block: remove it from that day only) |
Recurring blocks (ideal day / ideal week, habits)
Tool | Description |
| List the blocks that come back on chosen weekdays (the user's ideal week and habits) |
| Make a block recurring — from an existing block, or from scratch |
| Change a recurring block from a date onward (title, duration, fixed time, weekdays) — the past is never rewritten |
| Stop a repetition from a date onward; past days keep their blocks |
| Keep a note in a recurring block: every occurrence shows it from a date onward (a running log, a routine checklist) |
| Stop keeping a note in a recurring block from a date onward; earlier days keep it |
Tags
Tool | Description |
| List tags (lightweight — ordering arrays omitted), with optional name search ( |
| Get a tag by ID with all properties, including |
| Create a new tag |
| Update a tag (name, description, color, icon, favorite, |
| Permanently delete a tag and all its links |
| Merge a duplicate tag into another: links moved, |
| Get items linked to a tag — filter by |
| Link any entity to a tag |
| Remove a tag link |
Task Headers (Sections)
Tool | Description |
| List all task headers (section separators) |
| Get a task header by ID |
| Create a task header (section) — insert |
| Update a task header (name, description, collapsed) |
| Permanently delete a task header |
Contact & company links
Tool | Description |
| Link / unlink a company to a note |
| Link a contact to a note |
| Remove a contact link from a note |
| Add / remove a company as participant of an entry |
| Link a contact to an entry |
| Remove a contact link from an entry |
| Link / unlink a company to a task |
| Link a contact to a task |
| Remove a contact link from a task |
| Link a note to a task (non-destructive, the note survives) |
| Remove a note link from a task |
| Link a note to a time block (prepare before, write what happened after) |
| Remove a note link from a time block |
| Link a note to an entry (its write-up) |
| Remove a note link from an entry |
| Link two notes together (symmetric, non-destructive) |
| Remove the manual link between two notes |
| Attach a note to a calendar day (it surfaces in that day's view) |
| Remove a note from a calendar day (the note survives) |
Utilities
Tool | Description |
| Global search across all data types |
| Items modified since a timestamp (for sync) |
| Best practices for AI agents |
Tool annotations
All tools include MCP safety annotations:
Read-only tools (
list_*,get_*,search_*): markedreadOnlyHint: trueCreate tools: marked
destructiveHint: falseUpdate tools: marked
destructiveHint: false, idempotentHint: trueDelete tools: marked
destructiveHint: true, idempotentHint: true
Activity tracking
Every write operation (create, update, delete) performed through the API is recorded in an Activity Feed visible to the user inside Keepsake. Each action shows the entity type, a content preview, and which API key was used.
This means your user can see everything you do. Be transparent and precise. If you make a mistake, let the user know so they can verify in the activity feed.
Call get_agent_instructions at the start of each session for the full best practices guide.
Environment variables
Variable | Required | Description |
| Yes | Your API key (starts with |
| No | Custom API URL (default: |
Rate limits
60 requests per minute per API key. Rate limit headers are included in responses.
API documentation
Full REST API docs: keepsake.place/api
Privacy
Keepsake MCP server only communicates with the Keepsake API (app.keepsake.place). It does not send data to any third-party service. Your data stays between your MCP client and your Keepsake account.
All API calls are authenticated with your personal API key and scoped to your account via Row Level Security. No other user's data is accessible.
See our privacy policy at keepsake.place/privacy.
License
MIT
Available Tools
62 toolsarchive_noteAIdempotentInspect
Transform a QuickNote into a permanent Note (archive it). Notes appear on contact pages, tag pages, and the Notes section.
Inputs: id (required).
complete_taskAIdempotentInspect
Mark a task as completed. If the task is recurring, this automatically creates the next occurrence.
Inputs: id (required).
create_companyBInspect
Create a new company/organization. Only 'name' is required.
Inputs: name (required), email, notes, phone, +2 more.
create_contactAInspect
Create a new contact. first_name is required. last_name is optional (useful for contacts where you only know the first name).
Inputs: first_name (required), email, notes, phone, +3 more.
create_entryAInspect
An ENTRY is a dated interaction log tied to contacts. Records something that happened (call, meeting, email…) on a specific date.
Create a new interaction entry. Content supports #tag# and [[tag]] syntax for automatic tag linking.
Inputs: date (required), type (required), content, tag_ids, +1 more.
create_noteAInspect
Create a new QuickNote in the Inbox. QuickNotes are temporary captures — use archive_note to transform one into a permanent Note.
Content supports #tag# and [[tag]] for automatic tag linking.
Inputs: content (required), is_pinned, contact_ids.
create_tagAInspect
A TAG is a thematic grouping space. Syntax: #name# or [[name]]. Groups notes, entries, tasks, and contacts.
Create a new tag. If a tag with the same name already exists, returns the existing tag.
Inputs: name (required), description.
create_taskAInspect
A TASK is an action item to accomplish. Can have due date, recurrence, priority, linked to contacts and tags.
Create a new task. Title supports #tag# and [[tag]] for automatic tag linking.
Inputs: title (required), date, tag_ids, priority, +5 more.
create_task_headerAInspect
Create a new task header (section separator). Add it to a tag's items_order to position it.
Inputs: name (required), collapsed, description.
delete_companyADestructiveIdempotentInspect
Soft-delete a company. Use permanent=true for hard delete.
Inputs: id (required), permanent.
delete_contactADestructiveIdempotentInspect
Permanently delete a contact and all associated data.
Inputs: id (required).
delete_entryADestructiveIdempotentInspect
Delete an interaction entry.
Inputs: id (required).
delete_noteADestructiveIdempotentInspect
Soft-delete a QuickNote or Note. Use permanent=true for hard delete.
Inputs: id (required), permanent.
delete_tagADestructiveIdempotentInspect
Permanently delete a tag and all its links to contacts, entries, tasks, notes, and companies.
Inputs: id (required).
delete_taskBDestructiveIdempotentInspect
Delete a task.
Inputs: id (required).
delete_task_headerBDestructiveIdempotentInspect
Permanently delete a task header.
Inputs: id (required).
get_agent_instructionsARead-onlyInspect
Get best practices and instructions for being an effective Keepsake AI agent. Call this at the start of each session to refresh your instructions.
Inputs: no named parameters.
get_changelogARead-onlyInspect
Get all items modified since a given timestamp, across all entity types. Perfect for 'heartbeat' checks to see what changed since your last visit. Returns server_time to use as 'since' for the next call.
Inputs: since (required), type, limit.
get_companyARead-onlyInspect
Get a single company by ID, including linked contacts (with roles) and tags.
Inputs: id (required).
get_contactARead-onlyInspect
Get a single contact by ID, including recent entries (interactions), tags, last_interaction_date, and total_entries count.
Inputs: id (required), entries_limit.
get_contact_timelineARead-onlyInspect
Get a unified, chronological feed of ALL items related to a contact — entries, tasks, and notes — sorted by date (most recent first). Much more efficient than fetching entries, tasks, and notes separately.
Inputs: id (required), to, from, type, +2 more.
get_tagARead-onlyInspect
Get a single tag by ID with all its properties (name, description, color, icon, view mode, favorite status).
Inputs: id (required).
get_tag_itemsARead-onlyInspect
Get all items linked to a specific tag: contacts, entries, tasks, notes, and companies with counts.
Inputs: id (required).
get_task_headerARead-onlyInspect
Get a single task header by ID.
Inputs: id (required).
get_tasks_overdueARead-onlyInspect
Get only overdue tasks (pending tasks with a due date before today). Sorted by date ascending (oldest first).
Inputs: no named parameters.
get_tasks_todayARead-onlyInspect
Get all tasks for today: overdue tasks + tasks due today + ASAP tasks. Each task has a 'category' field ('overdue', 'today', or 'asap'). Includes counts per category.
Inputs: no named parameters.
link_entry_contactBIdempotentInspect
Link an existing contact to an entry.
Inputs: entry_id (required), contact_id (required).
link_note_contactAIdempotentInspect
Link an existing contact to a note.
Inputs: note_id (required), contact_id (required).
link_notesAIdempotentInspect
Link two notes together (knowledge base, N-N, non-destructive). The link is symmetric: both notes list each other in their linked-notes section. Use this to connect related ideas — e.g. a note that made you think of another one. Notes can also be linked inline by writing label in a note's content.
Inputs: note_id (required), target_note_id (required).
link_tagAIdempotentInspect
Link an entity (contact, entry, task, note, or company) to a tag.
Inputs: id (required), entity_id (required), entity_type (required).
link_task_contactAIdempotentInspect
Link an existing contact to a task.
Inputs: task_id (required), contact_id (required).
link_task_noteAIdempotentInspect
Link an existing note to a task (non-destructive, N-N). The note stays in the inbox/notes list and the task keeps a live link back to it — use this instead of deleting a note after creating a task from it. The note shows its linked tasks; the task shows the source note.
Inputs: note_id (required), task_id (required).
list_companiesARead-onlyInspect
List all companies/organizations in the user's Keepsake CRM. Supports pagination and sorting.
Inputs: sort, limit, order, offset.
list_contactsARead-onlyInspect
List all contacts in the user's Keepsake CRM. Supports pagination, sorting, and optional last_interaction_date enrichment.
Inputs: sort, limit, order, offset, +1 more.
list_daysARead-onlyInspect
List daily journal summaries. Filter by date range.
Inputs: to, from, limit, offset.
list_entriesARead-onlyInspect
List interaction entries (calls, emails, meetings, events, etc.). Supports filtering by type, contact, and date range.
Inputs: to, from, type, limit, +2 more.
list_notesARead-onlyInspect
List notes. QuickNotes (inbox, not yet archived) and Notes (archived, permanent). Filter by pinned or archived status.
Inputs: limit, offset, pinned, archived.
list_tagsBRead-onlyInspect
List all tags. Tags organize contacts, entries, tasks, notes, and companies.
Inputs: limit, offset.
list_task_headersARead-onlyInspect
List all task headers (section separators used to group tasks on tag pages and day views).
Inputs: limit, offset.
list_tasksBRead-onlyInspect
List tasks. Filter by status (pending/completed), date_type, or specific date.
Inputs: date, limit, offset, status, +1 more.
pin_noteAIdempotentInspect
Pin a QuickNote or Note so it appears at the top of the Inbox.
Inputs: id (required).
restore_noteAIdempotentInspect
Restore a Note back to a QuickNote in the Inbox (unarchive), or restore a deleted note from trash.
Inputs: id (required).
searchARead-onlyInspect
Search across all Keepsake data — contacts, entries, tasks, notes, and companies. Search is accent-insensitive (e.g., 'berenice' finds 'Bérénice').
Inputs: q (required), type, limit.
search_companiesARead-onlyInspect
Search companies by name, email, website, or address. Search is accent-insensitive.
Inputs: q (required).
search_contactsARead-onlyInspect
Search contacts by name, email, company, etc. Search is accent-insensitive.
Inputs: q (required).
snooze_taskBIdempotentInspect
Reschedule a task to a new date.
Inputs: id (required), date (required), date_type.
uncomplete_taskAIdempotentInspect
Mark a completed task as pending again.
Inputs: id (required).
unlink_entry_contactADestructiveIdempotentInspect
Remove the link between a contact and an entry.
Inputs: entry_id (required), contact_id (required).
unlink_note_contactADestructiveIdempotentInspect
Remove the link between a contact and a note.
Inputs: note_id (required), contact_id (required).
unlink_notesADestructiveIdempotentInspect
Remove the manual link between two notes (both notes survive). Links derived from inline label markdown in a note's content are preserved — edit the content to remove those.
Inputs: note_id (required), target_note_id (required).
unlink_tagADestructiveIdempotentInspect
Remove the link between an entity and a tag.
Inputs: id (required), entity_id (required), entity_type (required).
unlink_task_contactADestructiveIdempotentInspect
Remove the link between a contact and a task.
Inputs: task_id (required), contact_id (required).
unlink_task_noteADestructiveIdempotentInspect
Remove the link between a note and a task. Both the task and the note survive.
Inputs: note_id (required), task_id (required).
update_companyAIdempotentInspect
Update an existing company. Only send the fields you want to change.
Inputs: id (required), name, email, notes, +3 more.
update_contactAIdempotentInspect
Update an existing contact. Only send the fields you want to change.
Inputs: id (required), email, notes, phone, +4 more.
update_dayAIdempotentInspect
Create or update a daily journal summary. If a day entry already exists for this date, it will be updated (upsert).
Inputs: date (required), note (required).
update_entryAIdempotentInspect
Update an existing entry. Only send fields you want to change.
Inputs: id (required), date, type, content, +2 more.
update_noteAIdempotentInspect
Update an existing QuickNote or Note.
Inputs: id (required), content, tag_ids, contact_ids.
update_tagAIdempotentInspect
Update an existing tag. Only send the fields you want to change. Supports name, description, color, icon, view mode, and favorite status.
Inputs: id (required), icon, name, color, +3 more.
update_taskAIdempotentInspect
Update an existing task. Only send fields you want to change.
Inputs: id (required), date, title, tag_ids, +4 more.
update_task_headerAIdempotentInspect
Update a task header. Only send the fields you want to change.
Inputs: id (required), name, collapsed, description.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 62 tools
Each tool has a uniquely defined purpose, targeting specific entity types and actions (e.g., link_note_contact vs link_entry_contact). Even with 62 tools, the descriptions clearly differentiate them, making it easy for an agent to select the correct one.
Tool names follow a consistent verb_noun pattern (e.g., create_contact, list_contacts, update_task). The few multi-word nouns (e.g., get_contact_timeline) still adhere to the pattern. No mixing of conventions like camelCase or inconsistent verb prefixes.
With 62 tools, the server is far above the typical well-scoped range of 3-15. While each tool may have a distinct role, the sheer number could overwhelm an agent, and many linking operations could be consolidated into a single parameterized tool.
The tool surface covers full CRUD for all major entities (contacts, companies, entries, tasks, notes, tags, days, task headers), plus relational linking, search, changelog, and agent instructions. There are no obvious gaps in the domain's lifecycle.
Maintenance
Related MCP Connectors
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
MCP server for OnceAsk, the AI-native current-address layer for people and agents.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
MCP server for LeadDelta — manage LinkedIn connections and CRM data via AI assistants.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server enabling AI assistants to store, retrieve, and manage contextual information across conversations with features like persistent memory, advanced search, tagging, and privacy controls.MIT
- AlicenseAqualityDmaintenanceAn MCP server that integrates the Dex personal CRM API with AI assistants to manage contacts, groups, tags, and reminders through 27 specialized tools. It enables users to perform unified searches and execute full CRUD operations on their CRM data via natural language.28MIT
- FlicenseNot gradedqualityDmaintenanceA MCP server that provides persistent memory for AI assistants, storing personal information, relationships, and observations to enable personalized and contextual conversations.4-
- FlicenseNot gradedqualityDmaintenanceMCP server providing a persistent, temporal memory brain for AI assistants, enabling cross-session recall of facts with relationships and temporal context.3-