Skip to main content
Glama
danielamiao

sessions-mcp

by danielamiao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to sessions-mcp

No user-submitted related servers found.

    Related Servers

    • Brain

      sdrshn-nmbr
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP server for collecting, searching, and sharing agent session history from Claude Code, Codex, and Cursor, with repository scoping and token-based authentication.
      Apache 2.0

    • agent-bus

      rishabhjava
      A
      license
      A
      quality
      B
      maintenance
      Enables multiple coding agents (Claude Code, Codex, Cursor) to discover each other's sessions, search transcripts, ask questions, and handoff tasks through a shared MCP server.
      5
      8 npm
      MIT

    • repomemory

      Lay4U
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that captures and recalls coding session memory (failures, decisions, diffs) for AI agents, enabling cross-agent continuity and preventing repeated mistakes.
      108 npm
      MIT

    • codemem

      kunickiaj
      A
      license
      B
      quality
      A
      maintenance
      Persistent memory MCP server that captures coding session context and automatically injects relevant memories into prompts using hybrid search for OpenCode and Claude Code.
      14
      70
      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.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing recent sessions, semantic search, sharing, unsharing, and pulling a shared session. There is no overlap or potential for confusion between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (list_recent_sessions, search_my_sessions, share_session, unshare_session, pull_session). The naming is uniform and predictable.

    Tool Count5/5

    With only 5 tools, the server is well-scoped and each tool serves a clear purpose within the session management domain. This is within the ideal range.

    Completeness5/5

    The tool set covers the full lifecycle of session management: discovering recent sessions, searching them, sharing a session, revoking a share, and pulling a shared session into the current context. There are no obvious gaps for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources