Skip to main content
Glama
dockndevai

ossian-mcp

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ossian-mcp

No user-submitted related servers found.

    Related Servers

    • Nexus RAG MCP Server

      kaushikkumarkr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents with long-term memory and retrieval-augmented generation (RAG) capabilities, allowing them to recall past conversations, search local files, and learn user preferences.
      MIT

    • kbdb

      diko316
      A
      license
      B
      quality
      A
      maintenance
      Enables file-based knowledge management with ranked keyword and semantic hybrid search, allowing AI agents to learn from documents and recall relevant knowledge as a persistent memory tool.
      30
      56 npm
      AGPL 3.0

    • BuildAutomata Memory MCP

      brucepro
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.
      14
      -
    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.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    recall vs ask_documents is clearly delineated (memory vs organisational documents) and reinforced with explicit cross-references in the descriptions. list_documents and list_namespaces are both listing operations but target different resources (documents vs corpus slices with counts), so an agent should rarely confuse them.

    Naming Consistency3/5

    Two tools follow a clean list_* pattern (list_documents, list_namespaces) and ask_documents uses a verb_noun form, but 'recall' is a bare verb with no object, breaking the pattern. The set is still readable, just not uniformly conventional.

    Tool Count4/5

    Four tools is on the lean side but suits a narrow retrieval/memory scope where each tool earns its place. Nothing feels redundant or excessive for the stated purpose.

    Completeness3/5

    The read path is well covered (list documents, list namespaces, ask, recall), but there is no tool to store or update memories, and no way to fetch or inspect a single document. If ingestion is handled externally this is workable, but the memory side looks write-incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources