Skip to main content
Glama

Related Servers

Alternatives to okf-hub

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects any number of AI agents — Claude Code, Codex, or any MCP client — to one git-backed Markdown vault of shared team memory, exposing tools for briefings, search, reading, recent changes, sharing facts, transcripts, and urgent-item acknowledgments. Agent writes are queued and reviewed by a librarian model, then privacy-checked, linted, and committed as attributed git changes, so every agent reads the same current truth.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude, ChatGPT, and other AI apps to share one MCP-accessible hub of Markdown-based memories and skills, with per-app adapters, versioned writes, git history, saving policies, Google OAuth, and a web UI.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude to maintain a team knowledge base stored as markdown in a GitHub repository, with tools for search, edit, linking, and interactive views.
      3 npm
      2
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coordinating Claude Code and Codex across separate Git worktrees with shared issue ownership, file reservations, messages, and explicit handoffs.
      156 PyPI
      3
      MIT

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct hub operation: listing bases, searching a corpus, reading documents, retrieving governance rules, submitting proposals, and rescaming the hub. There is no meaningful overlap between the six tools.

    Naming Consistency4/5

    All tools share the kb_ prefix and use snake_case, and five of six follow a clear verb-first pattern. kb_governance is the only noun-style name, but it still fits the overall naming scheme without causing confusion.

    Tool Count5/5

    Six tools is a well-scoped size for a knowledge-base hub: discovery, reading, searching, governance, contribution, and maintenance each have a dedicated tool. No tool feels redundant or unnecessary.

    Completeness4/5

    The core workflows are covered: exploring bases, reading documents, checking governance rules, and submitting proposals are all supported. The main gap is that proposal resolution is not visible through the MCP tools, and base creation happens outside the hub via git, but these are documented limitations rather than fatal omissions.