Enterprise DNA
M MCP Servers Developer low

nicolascroce/keepsake-mcp

by Various

MCP server for Keepsake personal CRM — connect your AI agent to your contacts, tasks, notes, and more

N

MCP

nicolascroce/keepsake-mcp

Added 1 June 2026

Overview

An MCP server that bridges an AI agent with Keepsake, a personal CRM. It exposes contacts, tasks, and notes as resources and tools that the agent can read and write through the Model Context Protocol. Built in TypeScript, it runs as a standalone process that connects to Keepsake's data store.

Best for

Best for
Developers building AI workflows around personal relationship management

Use cases

  • Automatically log meeting notes and follow-ups to a contact
  • Query tasks for a specific person or project
  • Update contact details or add notes via a chat interface

Notes

An MCP server that bridges an AI agent with Keepsake, a personal CRM. It exposes contacts, tasks, and notes as resources and tools that the agent can read and write through the Model Context Protocol. Built in TypeScript, it runs as a standalone process that connects to Keepsake’s data store.

0 stars on GitHub. Last updated 2026-04-16. Licensed MIT.

Use cases

  • Automatically log meeting notes and follow-ups to a contact
  • Query tasks for a specific person or project
  • Update contact details or add notes via a chat interface

Pros

  • Direct integration between AI agents and personal CRM data
  • Leverages the standardized MCP protocol for interoperability
  • Open source and easy to inspect or extend

Cons

  • Zero stars on GitHub suggests very early stage or limited adoption
  • Requires a running Keepsake instance and MCP-compatible client
  • Dependency on third-party Keepsake service may affect reliability

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Direct integration between AI agents and personal CRM data
  • Leverages the standardized MCP protocol for interoperability
  • Open source and easy to inspect or extend

Cons

  • Zero stars on GitHub suggests very early stage or limited adoption
  • Requires a running Keepsake instance and MCP-compatible client
  • Dependency on third-party Keepsake service may affect reliability