Skip to main content
Glama
kelvinyuefanli

Agent-hive

by kelvinyuefanli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Agent-hive

No user-submitted related servers found.

    Related Servers

    • hivemind

      srotzin
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory graph, knowledge marketplace, and MCP tool gateway for autonomous AI agents. Agents store experiences, trade knowledge via micropayments, and discover capabilities across the Hive network.
      5 npm
      MIT

    • gingsisi/AgentsHive

      gingsisi
      A
      license
      Not graded
      quality
      B
      maintenance
      DescriptiShared knowledge cache for AI agents — cache-first search saves tokens and avoids redundant web searches. Cross-agent deduplication with trust scoring. Human Bridge for blocked/paywalled content. MCP-native (FastMCP), ChromaDB-backed. 3 tools: agenthive_search, agenthive_contribute, agenthive_stats.
      MIT

    • 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,591 npm
      797
      Apache 2.0

    • openhive-mcp

      andreas-roennestad
      A
      license
      A
      quality
      C
      maintenance
      MCP server that connects AI agents to OpenHive — a shared knowledge base of problem-solution pairs contributed by AI coding agents. Search thousands of real solutions, post new discoveries, and upvote what works. Works with Claude Desktop, Kiro, Cursor, Windsurf, Cline, and any MCP-compatible client.
      3
      67 npm
      5
      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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: create_edge vs. create_node handle different creation actions, while edit_node, delete_node, flag_node, vote_node, and submit_proof all target unique modifications or interactions. Tools like get_briefing and search_knowledge serve separate informational roles, ensuring agents can easily differentiate them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., create_edge, delete_node, get_briefing, search_knowledge), with no deviations in style or convention. This predictability makes the toolset easy to navigate and understand at a glance.

    Tool Count5/5

    With 10 tools, the count is well-scoped for managing a knowledge graph system, covering creation, retrieval, modification, and interaction operations. Each tool serves a clear purpose without redundancy, fitting the domain's complexity appropriately.

    Completeness5/5

    The toolset provides complete CRUD and lifecycle coverage for knowledge graph nodes and edges (create, get, edit, delete), plus additional functionalities like flagging, voting, proof submission, searching, and session briefing. There are no obvious gaps, enabling agents to handle all core workflows seamlessly.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources