Skip to main content
Glama
kirill-sviridov

handoff-mcp

by kirill-sviridov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to handoff-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Shared Memory Hub

      shirisha456
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple MCP-compatible AI clients to share persistent, versioned project knowledge across sessions with conflict-safe updates, provenance, hybrid retrieval, stale-memory handling, and context-budgeted recall.
      MIT

    • codebase-memory

      yuga-hashimoto
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent memory for AI coding agents through the Model Context Protocol, enabling them to store and retrieve project knowledge across sessions.
      27 npm
      MIT

    • @vemdev/mcp-server

      vem-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI agents durable project memory via the Model Context Protocol, allowing them to read tasks, record decisions, search context, and sync snapshots to the cloud.
      4 npm
      MIT

    • Chronos MCP

      Kodaxadev
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides Claude with a persistent local memory and structured knowledge graph to track project states, tasks, and historical decisions across different chat sessions. It enables users to recall information using keyword relevance, time-travel queries, and dependency analysis for complex project management.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checkpoint ends sessions, consolidates compresses old sessions, get_brief loads the brief, log_event records progress, note_entity stores durable knowledge, search_memory searches across projects, and sync synchronizes with git. No overlap in functionality.

    Naming Consistency5/5

    All tool names use a consistent snake_case pattern (e.g., get_brief, log_event, note_entity), which is predictable and easy to understand. No mixing of styles.

    Tool Count5/5

    7 tools is well-scoped for the server's purpose of managing handoff briefs and memory. Each tool covers a necessary operation without being excessive or insufficient.

    Completeness5/5

    The tool set covers the full lifecycle: starting a session (get_brief), recording progress (log_event, note_entity), searching memory (search_memory), ending sessions (checkpoint), compressing old sessions (consolidate), and syncing (sync). No obvious gaps.

    Maintenance

    ActivityStale
    ResponsivenessWithin a week

    Resources