Skip to main content
Glama
Sign In
po4erk91

Thread Keeper

by po4erk91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Thread Keeper

No user-submitted related servers found.

    Related Servers

    • threadctx-mcp by threadctx-dev

      threadctx-mcpofficial

      threadctx-dev
      A
      license
      A
      quality
      D
      maintenance
      Shared memory MCP server for AI coding agents, enabling context sharing across sessions with local SQLite or cloud-based semantic search, compatible with Claude Code and Cursor.
      2
      32 npm
      1
      MIT

    • Continuum MCP Server

      pouyahasanamreji
      F
      license
      Not graded
      quality
      D
      maintenance
      Shared memory and orchestration for coding agents, enabling persistent knowledge, multi-agent coordination, and a canonical workflow across MCP-compatible AI clients.
      13 npm
      92
      -

    • memorix

      AVIDS2
      A
      license
      A
      quality
      A
      maintenance
      Cross-agent memory bridge for AI coding assistants. Persistent knowledge graph shared across 10 IDEs (Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, Antigravity, OpenCode, Trae, Gemini CLI) via MCP. 22 tools including team collaboration, auto-cleanup, mini-skills, session management, and workspace sync. 100% local, zero API keys required.
      9
      1,654 npm
      887
      Apache 2.0

    • mcp-agent-brain-hub

      leluong141996-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Governed shared memory for multi-agent systems. Claude Code, Cursor and your own agents read and write one memory, so what one agent learns the others can use, without each one seeing everything. * 6 MCP tools over stdio, no dependencies: brain_recall, brain_remember, brain_correct, brain_forget, brain_profile, brain_feedback * One API key per agent, private / shared / global scopes per relation,
      6
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 148 tools

    Disambiguation2/5

    The surface spans many subsystems and contains several near-overlapping families: peers/presence/live_status, search/dialog_search/search_via_parent, tasks/task_thread/task_logs, and numerous *_status versus *_run trigger tools. Descriptions often clarify individual cases, but an agent can easily misselect among diagnostic, lifecycle, and trigger operations.

    Naming Consistency3/5

    Most names use snake_case, but the conventions are mixed: many are verb_noun (core_get, skill_manage), many are noun-only (tasks, inbox, brief, context), and others are subsystem-prefixed (curator_, dialectic_, shadow_review_). It is readable but not predictably patterned across the set.

    Tool Count1/5

    A 148-tool MCP surface is far beyond a reasonable toolset for an agent to navigate reliably, especially for a memory/coordination server. Many tools are administrative, diagnostic, or role-specific variants that could be consolidated or hidden behind profiles.

    Completeness4/5

    The toolset covers an unusually broad lifecycle: threads, notes, skills, lessons, dialectic claims, signals, tasks, curation, sync, diagnostics, and memory maintenance. There are few obvious dead ends, though the sheer breadth and internal-role tools make the complete surface hard to discover and use coherently.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources