Skip to main content
Glama
jayasukuv11-beep

agenthelm

by jayasukuv11-beep
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to agenthelm

No user-submitted related servers found.

    Related Servers

    • knos

      drexthealpha
      A
      license
      A
      quality
      A
      maintenance
      One local memory every coding agent on your machine shares — Claude Code, Cursor, Claude Desktop, OpenCode. Answers from past sessions, commits, CLAUDE.md/AGENTS.md and ADRs with the exact source, and withholds work another agent has claimed so two agents don't rewrite the same thing.
      3
      5,881 PyPI
      1
      MIT

    • lockstep

      lockstep-team-agent
      A
      license
      D
      quality
      B
      maintenance
      Decision memory for teams building with AI coding agents. Captures every engineering decision once, ranks it by blast radius, and briefs every MCP-compatible agent before it acts, so agents stop making conflicting changes across repos.
      17
      2 npm
      10
      Apache 2.0

    • hive

      HusseinTaha
      A
      license
      C
      quality
      B
      maintenance
      Enables Claude Code agents and sub-agents to share a persistent, compiled memory of project state, decisions, tasks, and facts across sessions instead of re-reading transcripts. Provides token-efficient bootstrap, search, commit, leased task claiming, and task-specific context compilation so parallel agents can coordinate without clobbering each other.
      5
      6 npm
      MIT

    • PeerBridge MCP

      Hoylon
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects multiple AI agents (Codex, Claude Code, Grok, etc.) into a coordinated, auditable team with shared memory, task ownership, and human oversight, enabling parallel collaboration without conflicts.
      241
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation on the Project Brain: retrieval of context, submission of new knowledge, and querying history. There is no overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (get_context, propose_knowledge, get_history). The repetition of 'get' is acceptable as it indicates retrieval operations.

    Tool Count4/5

    With only 3 tools, the server is scoped for a focused knowledge management function. While minimal, each tool serves a clear purpose and the count is appropriate for the domain.

    Completeness3/5

    The tools cover retrieval, submission, and history, but lack direct update or delete operations for knowledge items. Updates could be handled via new proposals, but that introduces overhead and gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources