Skip to main content
Glama

Related Servers

Alternatives to Kybase

  • A
    license
    Not graded
    quality
    A
    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.
    1
    MIT
  • A
    license
    Not graded
    quality
    A
    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.
    487 npm
    3
    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
    D
    maintenance
    Self-hosted personal knowledge base with semantic search, enabling AI agents to capture, search, and manage thoughts using PostgreSQL with pgvector.
    13 npm
    ISC
  • A
    license
    Not graded
    quality
    A
    maintenance
    Self-hosted knowledge mesh with built-in MCP server enabling AI agents to search and retrieve notes across federated hubs.
    38
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    A self-hosted MCP server that gives AI agents persistent, searchable memory with importance scoring, knowledge graphs, and autonomous memory consolidation.
    1
    -

TDQS

A4.1/5.0

Scored across 18 tools

Disambiguation4/5

Most tools are clearly distinct (get_note vs list_notes vs search_notes; create/update/delete/restore_note; folder operations). The only mild overlap is get_neighbors vs get_graph, but their descriptions explicitly differentiate scope and output shape, so an agent can choose correctly.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_note, list_notes, create_note, update_note, delete_note, restore_note, search_notes, list_folders, create_folder, update_folder, delete_folder, get_graph, get_backlinks, get_neighbors, append_to_note, replace_in_note, indexing_status, list_tags. No mixed conventions or vague verbs.

Tool Count4/5

18 tools is on the higher end but appropriate for a knowledge-management server covering notes, folders, search, graph, and indexing. Each tool earns its place; the count is justified by the domain breadth.

Completeness5/5

The surface covers the full note lifecycle (create, read, update, append, replace, delete, restore), folder management, search (text/semantic/hybrid), graph traversal, backlinks, tags, and indexing status. No obvious dead ends: every write has a corresponding read, and soft-delete has restore.

Maintenance

ActivityActive
ResponsivenessNo issues