Skip to main content
Glama
nicolascroce

keepsake-mcp

by nicolascroce

Related Servers

Alternatives to keepsake-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local-first contact management MCP server with SQLite storage and Google Contacts sync, enabling AI agents to upsert, search, log interactions, and surface follow-ups for relationships.
      8 npm
      MIT
    • F
      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
      -
    • 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
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing a persistent, temporal memory brain for AI assistants, enabling cross-session recall of facts with relationships and temporal context.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A personal AI assistant server that provides MCP tools for notes, files, reminders, memory, shell, browser, and 30+ SaaS integrations, enabling AI clients to access and manage your data across sessions.
      3,954
      MIT

    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

    ActivityActive
    ResponsivenessUnresponsive