Skip to main content
Glama

Related Servers

Alternatives to AgentRoots

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      MCP server providing persistent engineering memory and spec-driven development workflows for AI coding agents, preserving learnings across sessions.
      41
      1,046 PyPI
      Business Source 1.1
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that keeps raw tool output out of the context window by sandboxing and compressing results (about 98% reduction), persisting file edits, git operations, tasks and decisions in SQLite with BM25 retrieval so the agent resumes after compaction, and enforcing routing across 17 platforms via MCP and hooks. It also encourages the model to write scripts that compute answers and log only results instead of reading large data into context.
      10
      24,527 npm
      2
      Elastic 2.0
    • 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.
      12 npm
      98
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets multiple AI coding agents share state, preserve context across sessions, and coordinate via a knowledge graph, messaging, and branch-preserving checkpoint/resume with conflict handling.
      69 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI agents with persistent memory, cross-agent sharing, and context management, enabling them to remember conversations, track complex tasks, and evolve skills across tools.
      2
      MIT

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct purpose: context retrieval, frontier scanning, querying, record fetching, validation, proposal creation, lifecycle review, evidence linking, and synchronization. There is no overlap or ambiguity between tool functions.

    Naming Consistency5/5

    All tools consistently use the 'research_' prefix with a clear verb_noun pattern (e.g., get_context, link_evidence, validate). The naming is uniform, predictable, and follows a standard convention.

    Tool Count5/5

    Nine tools is well-scoped for a research project management server, covering the core lifecycle without redundancies. The number falls comfortably within the ideal range and each tool serves a necessary function.

    Completeness4/5

    The toolset covers creation (propose), lifecycle management (review), evidence linking, querying, validation, and sync, which addresses the main workflows. However, there is no explicit update or delete tool, so direct modification of record content is not exposed; the review and propose tools may handle this indirectly via versioning.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues