Skip to main content
Glama
keepsake-mcp

keepsake-mcp

by nicolascroce

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

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/mcp

  • Authentication: 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-mcp

Then 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

review_note

note_id

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

List contacts with pagination, sorting, field selection and filters (linked company, has_company, updated_since)

get_contact

Get a contact with recent interactions, tags, and stats

create_contact

Create a new contact (company links it to a company record, created if missing)

update_contact

Update contact fields

delete_contact

Permanently delete a contact

search_contacts

Accent-insensitive search by name, email, notes, phone and linked company names

get_contact_timeline

Unified chronological feed of all items for a contact

Companies

Tool

Description

list_companies

List all companies

get_company

Get company with linked contacts and tags

create_company

Create a new company

update_company

Update company fields

delete_company

Soft-delete (or permanent delete) a company

search_companies

Accent-insensitive company search

link_contact_company

Link a contact to a company (optional role)

unlink_contact_company

Remove a contact–company link

merge_companies

Merge a duplicate company into another (contacts, entries, tags, details, notes)

Entries (Interactions)

Tool

Description

list_entries

List interactions (calls, emails, meetings, etc.) — filter by type, contact, company, page (tag_id), dates

create_entry

Log a new interaction — supports #tag# and [[tag]] syntax

update_entry

Update an interaction

delete_entry

Delete an interaction

Tasks

Tool

Description

list_tasks

List tasks — filter by status, date, company, page (tag_id)

get_task

Get a task with its tags, contacts, companies and linked notes

create_task

Create a task — supports #tag# and [[tag]] syntax

update_task

Update task fields

delete_task

Delete a task

complete_task

Mark as completed (auto-creates next occurrence for recurring tasks)

uncomplete_task

Mark as pending again

snooze_task

Reschedule to a new date

get_tasks_today

Today's tasks: overdue + due today + ASAP

get_tasks_overdue

Only overdue tasks

QuickNotes

Tool

Description

list_notes

List notes — filter by pinned/archived, day, company, page (tag_id), publication-flow stage (status)

list_note_statuses

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_note

Get one note by ID with its tags, contacts, tasks and linked notes

create_note

Create a note — supports #tag# and [[tag]] syntax; archived creates a permanent Note directly (no Inbox), status puts it straight into the publication flow

update_note

Update note content, links, days, or its publication-flow stage (status)

delete_note

Soft-delete (or permanent)

pin_note

Pin as a post-it (short reference always at hand)

unpin_note

Unpin a note (it stays where it is)

archive_note

Archive a note

restore_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_note_comments

List the marginalia attached to a note

create_note_comment

Attach a marginalia to a passage (pass quote) or to the whole note

update_note_comment

Edit the content of a marginalia

delete_note_comment

Permanently delete a marginalia

Days (intention or question of the day)

Tool

Description

list_days

List days with their intention or question of the day (the one in force, which stays until changed), by date range

get_day

Get a day, its intention in force (intention, carried over until changed) and what was written that day (note)

update_day

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_day_blocks

List a day's time blocks, in timeline order (creates that day's recurring blocks first)

create_day_block

Create a block, auto-placed first-fit (or pinned via anchor_time)

update_day_block

Update a block (title, duration, anchor, note, done)

delete_day_block

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_recurring_blocks

List the blocks that come back on chosen weekdays (the user's ideal week and habits)

create_recurring_block

Make a block recurring — from an existing block, or from scratch

update_recurring_block

Change a recurring block from a date onward (title, duration, fixed time, weekdays) — the past is never rewritten

stop_recurring_block

Stop a repetition from a date onward; past days keep their blocks

keep_recurring_block_note

Keep a note in a recurring block: every occurrence shows it from a date onward (a running log, a routine checklist)

stop_keeping_recurring_block_note

Stop keeping a note in a recurring block from a date onward; earlier days keep it

Tags

Tool

Description

list_tags

List tags (lightweight — ordering arrays omitted), with optional name search (q) and archived / favorite filters

get_tag

Get a tag by ID with all properties, including tasks_order (section markers h:<header_id>)

create_tag

Create a new tag

update_tag

Update a tag (name, description, color, icon, favorite, archived to close a project without deleting anything, order of tasks and sections via tasks_order)

delete_tag

Permanently delete a tag and all its links

merge_tag

Merge a duplicate tag into another: links moved, #source# rewritten as the target's name, source deleted

get_tag_items

Get items linked to a tag — filter by types/status, summary mode, task sections included

link_tag

Link any entity to a tag

unlink_tag

Remove a tag link

Task Headers (Sections)

Tool

Description

list_task_headers

List all task headers (section separators)

get_task_header

Get a task header by ID

create_task_header

Create a task header (section) — insert h:<id> in the tag's tasks_order to place it

update_task_header

Update a task header (name, description, collapsed)

delete_task_header

Permanently delete a task header

Tool

Description

link_note_company / unlink_note_company

Link / unlink a company to a note

link_note_contact

Link a contact to a note

unlink_note_contact

Remove a contact link from a note

link_entry_company / unlink_entry_company

Add / remove a company as participant of an entry

link_entry_contact

Link a contact to an entry

unlink_entry_contact

Remove a contact link from an entry

link_task_company / unlink_task_company

Link / unlink a company to a task

link_task_contact

Link a contact to a task

unlink_task_contact

Remove a contact link from a task

link_task_note

Link a note to a task (non-destructive, the note survives)

unlink_task_note

Remove a note link from a task

link_day_block_note

Link a note to a time block (prepare before, write what happened after)

unlink_day_block_note

Remove a note link from a time block

link_entry_note

Link a note to an entry (its write-up)

unlink_entry_note

Remove a note link from an entry

link_notes

Link two notes together (symmetric, non-destructive)

unlink_notes

Remove the manual link between two notes

link_note_date

Attach a note to a calendar day (it surfaces in that day's view)

unlink_note_date

Remove a note from a calendar day (the note survives)

Utilities

Tool

Description

search

Global search across all data types

get_changelog

Items modified since a timestamp (for sync)

get_agent_instructions

Best practices for AI agents

Tool annotations

All tools include MCP safety annotations:

  • Read-only tools (list_*, get_*, search_*): marked readOnlyHint: true

  • Create tools: marked destructiveHint: false

  • Update tools: marked destructiveHint: false, idempotentHint: true

  • Delete 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

KEEPSAKE_API_KEY

Yes

Your API key (starts with ksk_)

KEEPSAKE_API_URL

No

Custom API URL (default: https://app.keepsake.place/api/v1)

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 tools
archive_noteA
Idempotent
Inspect

Transform a QuickNote into a permanent Note (archive it). Notes appear on contact pages, tag pages, and the Notes section.

Inputs: id (required).

complete_taskA
Idempotent
Inspect

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_companyA
DestructiveIdempotent
Inspect

Soft-delete a company. Use permanent=true for hard delete.

Inputs: id (required), permanent.

delete_contactA
DestructiveIdempotent
Inspect

Permanently delete a contact and all associated data.

Inputs: id (required).

delete_entryA
DestructiveIdempotent
Inspect

Delete an interaction entry.

Inputs: id (required).

delete_noteA
DestructiveIdempotent
Inspect

Soft-delete a QuickNote or Note. Use permanent=true for hard delete.

Inputs: id (required), permanent.

delete_tagA
DestructiveIdempotent
Inspect

Permanently delete a tag and all its links to contacts, entries, tasks, notes, and companies.

Inputs: id (required).

delete_taskB
DestructiveIdempotent
Inspect

Delete a task.

Inputs: id (required).

delete_task_headerB
DestructiveIdempotent
Inspect

Permanently delete a task header.

Inputs: id (required).

get_agent_instructionsA
Read-only
Inspect

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_changelogA
Read-only
Inspect

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_companyA
Read-only
Inspect

Get a single company by ID, including linked contacts (with roles) and tags.

Inputs: id (required).

get_contactA
Read-only
Inspect

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_timelineA
Read-only
Inspect

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_dayA
Read-only
Inspect

Get a specific day's journal summary by date.

Inputs: date (required).

get_tagA
Read-only
Inspect

Get a single tag by ID with all its properties (name, description, color, icon, view mode, favorite status).

Inputs: id (required).

get_tag_itemsA
Read-only
Inspect

Get all items linked to a specific tag: contacts, entries, tasks, notes, and companies with counts.

Inputs: id (required).

get_task_headerA
Read-only
Inspect

Get a single task header by ID.

Inputs: id (required).

get_tasks_overdueA
Read-only
Inspect

Get only overdue tasks (pending tasks with a due date before today). Sorted by date ascending (oldest first).

Inputs: no named parameters.

get_tasks_todayA
Read-only
Inspect

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_contactB
Idempotent
Inspect

Link an existing contact to an entry.

Inputs: entry_id (required), contact_id (required).

list_companiesA
Read-only
Inspect

List all companies/organizations in the user's Keepsake CRM. Supports pagination and sorting.

Inputs: sort, limit, order, offset.

list_contactsA
Read-only
Inspect

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_daysA
Read-only
Inspect

List daily journal summaries. Filter by date range.

Inputs: to, from, limit, offset.

list_entriesA
Read-only
Inspect

List interaction entries (calls, emails, meetings, events, etc.). Supports filtering by type, contact, and date range.

Inputs: to, from, type, limit, +2 more.

list_notesA
Read-only
Inspect

List notes. QuickNotes (inbox, not yet archived) and Notes (archived, permanent). Filter by pinned or archived status.

Inputs: limit, offset, pinned, archived.

list_tagsB
Read-only
Inspect

List all tags. Tags organize contacts, entries, tasks, notes, and companies.

Inputs: limit, offset.

list_task_headersA
Read-only
Inspect

List all task headers (section separators used to group tasks on tag pages and day views).

Inputs: limit, offset.

list_tasksB
Read-only
Inspect

List tasks. Filter by status (pending/completed), date_type, or specific date.

Inputs: date, limit, offset, status, +1 more.

pin_noteA
Idempotent
Inspect

Pin a QuickNote or Note so it appears at the top of the Inbox.

Inputs: id (required).

restore_noteA
Idempotent
Inspect

Restore a Note back to a QuickNote in the Inbox (unarchive), or restore a deleted note from trash.

Inputs: id (required).

search_companiesA
Read-only
Inspect

Search companies by name, email, website, or address. Search is accent-insensitive.

Inputs: q (required).

search_contactsA
Read-only
Inspect

Search contacts by name, email, company, etc. Search is accent-insensitive.

Inputs: q (required).

snooze_taskB
Idempotent
Inspect

Reschedule a task to a new date.

Inputs: id (required), date (required), date_type.

uncomplete_taskA
Idempotent
Inspect

Mark a completed task as pending again.

Inputs: id (required).

unlink_entry_contactA
DestructiveIdempotent
Inspect

Remove the link between a contact and an entry.

Inputs: entry_id (required), contact_id (required).

update_companyA
Idempotent
Inspect

Update an existing company. Only send the fields you want to change.

Inputs: id (required), name, email, notes, +3 more.

update_contactA
Idempotent
Inspect

Update an existing contact. Only send the fields you want to change.

Inputs: id (required), email, notes, phone, +4 more.

update_dayA
Idempotent
Inspect

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_entryA
Idempotent
Inspect

Update an existing entry. Only send fields you want to change.

Inputs: id (required), date, type, content, +2 more.

update_noteA
Idempotent
Inspect

Update an existing QuickNote or Note.

Inputs: id (required), content, tag_ids, contact_ids.

update_tagA
Idempotent
Inspect

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_taskA
Idempotent
Inspect

Update an existing task. Only send fields you want to change.

Inputs: id (required), date, title, tag_ids, +4 more.

update_task_headerA
Idempotent
Inspect

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

    A3.8/5.0

    Scored across 62 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An 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
    • A
      license
      A
      quality
      D
      maintenance
      An 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.
      28
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A MCP server that provides persistent memory for AI assistants, storing personal information, relationships, and observations to enable personalized and contextual conversations.
      4
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing a persistent, temporal memory brain for AI assistants, enabling cross-session recall of facts with relationships and temporal context.
      3
      -