Skip to main content
Glama
dnotitia

akb

by dnotitia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to akb

No user-submitted related servers found.

    Related Servers

    • Brainstem

      DarkCodePE
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first knowledge backend for AI agents that connects MCP hosts to an Obsidian-compatible vault with indexed retrieval, token-budgeted memory recall, and secure ingestion.
      1
      MIT

    • auxly-memory-cli

      Tzamun-Arabia-IT-Co
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
      2
      MIT

    • index-server

      jagilber-org
      A
      license
      Not graded
      quality
      B
      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.
      25 npm
      MIT

    • exomem

      Artexis10
      A
      license
      Not graded
      quality
      B
      maintenance
      Durable memory with sources, proof, history, and review for MCP-capable agents. It turns a Markdown/Obsidian vault into a local knowledge substrate, enabling agents to store, search, and retrieve governed knowledge.
      3,213 PyPI
      10
      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

    A3.6/5.0

    Scored across 50 tools

    Disambiguation3/5

    The resource-specific variants (put/put_file/put_image, get/get_file, delete/delete_file/delete_collection/delete_vault, update/update_file/edit) have overlapping verbs and could be misselected without close reading, but the descriptions carefully distinguish semantic search from grep, document content from file bytes, and vault-scoped activity from per-document history. Overall, an agent can disambiguate with effort, but the boundaries are not immediately obvious from names alone.

    Naming Consistency5/5

    All 50 tools use a consistent akb_ + snake_case verb_noun pattern (list_vaults, create_table, delete_file) with only a few bare verbs (put, get, update, delete, sql, grep) that still fit the naming system. There is no mixing of conventions or unpredictable style.

    Tool Count2/5

    At 50 tools this is a very large surface even for a comprehensive knowledge-base server; the count dimension explicitly treats 25+ as too many. The breadth of domains (vaults, docs, tables, files, graph, publications, access) explains some of the size, but the surface could be consolidated (e.g. file/image variants, publication helpers).

    Completeness4/5

    The server covers the full lifecycle for vaults, documents, tables, files, collections, access control, publications, and import/export, plus search, graph, history, and help. Minor gaps exist—no vault metadata/rename tool, no collection rename, and table row management is only via raw SQL—but they are workable.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources