Skip to main content
Glama
proticom

Gnosys

by proticom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Gnosys

  • mcp-memori by MemoriLabs

    mcp-memoriofficial

    MemoriLabs
    A
    license
    A
    quality
    F
    maintenance
    With Memori's MCP server, your agent can retrieve relevant memories before answering and store durable facts after responding, keeping context across sessions without any SDK integration. With MCP, it can: Store stable user facts and preferences after answering using the advanced_augmentation tool Recall relevant memories before answering using the recall tool Maintain context across sessions us
    2
    21 npm
    2
    MIT

Related Servers

  • knowledge-base-server

    Layla4720
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to capture, classify, synthesize, and retrieve persistent knowledge through MCP and REST APIs, so multiple agents can share memory and improve across sessions. It provides full-text, semantic, and hybrid search with token-optimized context retrieval from sources like Obsidian, code, transcripts, and terminal sessions.
    14 npm
    MIT
  • kairn by primeline-ai

    kairnofficial

    primeline-ai
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides AI assistants with a persistent knowledge graph and experience memory, featuring context-aware routing, progressive disclosure, decay-based forgetting, and automatic promotion of important knowledge. It offers 22 MCP tools for storing, recalling, connecting, and querying knowledge, experiences, preferences, and ideas.
    53 PyPI
    13
    MIT

  • knowledge-base-server

    hugonowak0237
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to share persistent memory by capturing, classifying, synthesizing, and retrieving knowledge from sources like Obsidian, code, and transcripts via MCP and REST APIs. Provides token-optimized search, three-tier memory, and self-learning capture of sessions and fixes so multiple agents can build on prior context.
    14 npm
    MIT

  • knowledge-base-server

    dorothyinoue80287
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to share persistent memory by ingesting knowledge from sources like Obsidian, code, documents, web clips, and terminal sessions, then providing token-optimized search, context, classification, synthesis, and capture tools through MCP and REST APIs.
    14 npm
    MIT

  • knowledge-base-server

    Ebba57
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to share a persistent, self-improving memory by ingesting, classifying, synthesizing, and retrieving knowledge from sources like Obsidian vaults, code, and transcripts through MCP and REST APIs. Provides token-optimized, tiered retrieval with full-text and semantic search so every agent session builds on accumulated context.
    14 npm
    MIT
Deploy Server
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A4.3/5.0

Scored across 14 tools

Disambiguation4/5

Most tools have clearly distinct purposes, and descriptions explicitly cross-reference alternatives (read vs hybrid_search vs recall; reinforce vs reflect; dashboard vs briefing; update vs add_structured). The memory-retrieval trio (read/recall/hybrid_search) and the feedback pair (reinforce/reflect) overlap somewhat, but the guidance is strong enough that an agent can select confidently.

Naming Consistency4/5

All tools share the gnosys_ prefix and use snake_case verb_noun patterns (read, add_structured, update, hybrid_search, preference_set/get, traverse). Minor deviations like gnosys_init and gnosys_toolset are noun-style rather than verb_noun, but overall very predictable.

Tool Count5/5

14 tools is well within the ideal range, each mapping to a distinct memory-system operation (read/write/search/feedback/admin/preferences). The tiering mechanism gates advanced tools without bloating the default surface.

Completeness4/5

The surface covers the full memory lifecycle: create (add_structured), read, update/archive, search (hybrid_search/recall/traverse), feedback (reinforce/reflect), project setup (init/briefing/dashboard), and preferences. Hard deletion is intentionally human-only via CLI, a deliberate rather than accidental gap.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources