Skip to main content
Glama
jaydubya818

Agentic-KB

by jaydubya818
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Agentic-KB

No user-submitted related servers found.

    Related Servers

    • agent-lore

      osteele
      A
      license
      Not graded
      quality
      B
      maintenance
      A machine-local, agent-writable knowledge base MCP server that lets coding agents autonomously record and retrieve hard-won operational facts, incidents, and corrections as markdown pages in a git repo, with provenance, talk pages, and search.
      3 npm
      MIT

    • index-server

      jagilber-org
      A
      license
      Not graded
      quality
      A
      maintenance
      Governed knowledge base for AI agents via the Model Context Protocol (MCP), enabling agents to search, read, and contribute persisted knowledge with versioning, audit trails, and approval workflows.
      57 npm
      MIT

    • sourcebook

      BackendGameSetMatch
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents a git-backed markdown wiki to read and update, enabling search, read, write, verify, ingest, promote, and lint operations on versioned knowledge documents with schema validation, staleness tracking, and contradiction detection.
      4
      MIT

    • totem-mcp

      emiliano-go
      A
      license
      C
      quality
      A
      maintenance
      Enables engineering agents to maintain persistent knowledge across sessions by storing decisions, invariants, gotchas, and rejected ideas, with staleness detection, conflict detection, full-text search, and structured context assembly.
      31
      3
      MIT

    • clewwiki

      Dodecaidr
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables humans and AI coding agents to collaboratively write to a shared knowledge base with conflict-safe claims, code-anchored staleness detection, and synchronized human/agent documentation via MCP and REST.
      AGPL 3.0
    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

    C2.9/5.0

    Scored across 37 tools

    Disambiguation3/5

    There are parallel general and repo-scoped tools (e.g., close_agent_task vs close_repo_task, publish_bus_item vs publish_repo_discovery/escalation, promote_learning vs promote_repo_learning) that can be confused. Multiple agent state tools (status, verify, repair, trace) also overlap in lifecycle focus, though descriptions help clarify scope.

    Naming Consistency4/5

    Names consistently use snake_case and mostly follow verb_noun or noun_verb patterns. Minor deviations exist, such as agent_* prefix tools (agent_status, agent_verify_state) mixed with verb-first names, and dry_run_close_repo_task vs agent_dry_run_close_task ordering.

    Tool Count2/5

    With 37 tools, the surface is heavy for a knowledge base server. Many parallel repo/agent variants (e.g., close_agent_task, close_repo_task, dry_run_close_repo_task, agent_dry_run_close_task) could likely be consolidated.

    Completeness4/5

    The toolset covers core wiki operations (read, search, list, query, compile), full agent lifecycle (start, active, status, verify, repair, append, abandon, close, trace), bus publishing, repo sync/context/task close, and rewrites. Minor gaps include explicit article delete/update and agent contract management, but most workflows are supported.

    Resources