Skip to main content
Glama

Related Servers

Alternatives to Kybase

  • A
    license
    Not graded
    quality
    B
    maintenance
    A self-hosted Markdown knowledge base and Agent Harness with an MCP server that enables AI agents to read and write notes, providing persistent memory and a shared workspace for multi-agent collaboration.
    2
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Self-hosted, local-first knowledge graph and memory server for AI agents. Enables agents to persist, recall, and organize knowledge through MCP with automatic distillation, deduplication, and cross-linking.
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    A self-hosted knowledge-graph memory server for AI agents, providing persistent memory via 7 MCP tools, automatic instructions, and a web dashboard, enabling AI assistants to remember and retrieve information across sessions.
    362 npm
    6
    AGPL 3.0
  • A
    license
    Not graded
    quality
    F
    maintenance
    A self-hosted persistent memory platform for AI agents and humans offering tools for memory storage, search, beliefs, work management, and code intelligence via MCP.
    7
    GPL 3.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to search, read, ingest, annotate, and manage a self-hosted knowledge base of archived links, Git repositories, documents, and notes over MCP.
    AGPL 3.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    Self-hosted personal knowledge base with semantic search, enabling AI agents to capture, search, and manage thoughts using PostgreSQL with pgvector.
    12 npm
    ISC
  • A
    license
    Not graded
    quality
    B
    maintenance
    Self-hosted knowledge mesh with built-in MCP server enabling AI agents to search and retrieve notes across federated hubs.
    41
    MIT

TDQS

A3.9/5.0

Scored across 18 tools

Disambiguation5/5

Each tool targets a distinct verb+resource, and the descriptions actively route between the close pairs (list_notes vs search_notes, append_to_note vs update_note vs replace_in_note, get_backlinks vs get_neighbors vs get_graph). No two tools appear to do the same thing, and the explicit 'use X instead of Y' guidance removes the residual overlap.

Naming Consistency4/5

Nearly everything is a clean verb_noun pattern (create_note, list_folders, get_backlinks, restore_note), with consistent pluralization for collections. The one outlier is indexing_status, which is a noun phrase with no verb prefix and breaks the pattern.

Tool Count4/5

18 tools is on the heavier side but each maps to a real operation in a notes+folders+graph domain; nothing feels like filler. A slightly tighter surface (e.g. folding indexing_status into a broader status call) would make it ideal.

Completeness4/5

Note lifecycle is fully covered (create/read/list/update/append/replace/soft-delete/restore, search, backlinks, graph), and folders have full CRUD with cascade delete. Minor gaps remain: no tag management beyond list_tags (no rename/merge/delete of tags), no permanent purge, and no dedicated trash-listing tool (deferred to list_notes trashed:true).

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues