Skip to main content
Glama
shijieweb

memos-api-mcp

by shijieweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to memos-api-mcp

No user-submitted related servers found.

    Related Servers

    • memopaper-mcp

      agcraft
      A
      license
      A
      quality
      D
      maintenance
      MCP server for memopaper.dev that gives AI agents direct access to a memo buffer, enabling memo creation, retrieval, editing, and deletion via natural language.
      1
      9 npm
      MIT

    • knowledgeplane

      camplight
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that gives AI agents and teams persistent, shared memory using a knowledge graph with vector embeddings, automatic consolidation of related facts, and hybrid search.
      3
      -

    • memoo-mcp

      hinha
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Memoo knowledge graph RAG, enabling search, Q&A, graph traversal, and episode management via the Memoo REST API.
      4 npm
      Apache 2.0

    • memvid-mcp

      Tapiocapioca
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides a persistent memory layer for AI agents by wrapping the memvid CLI. It enables users to manage memory files, perform hybrid searches, and conduct RAG-based question answering through 40 specialized tools.
      40
      1
      MIT
    • yantrikdb-mcp by yantrikos

      yantrikdb-mcpofficial

      yantrikos
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing cognitive memory tools (remember, recall, think, etc.) for AI agents, enabling forgetting, consolidation, and contradiction detection.
      174
      Apache 2.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 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: memory tools cover add/search/delete/update/profile, while knowledge base tools cover create/add/get/delete/remove. Even in overlapping areas like search_memory and get_user_profile, descriptions clarify complementary use.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (add_, get_, delete_, create_, remove_). Minor inconsistency exists between 'remove_knowledge_base' and 'delete_kb_documents' using different verbs, and between singular 'add_kb_document' and plural 'get_kb_documents'/'delete_kb_documents'.

    Tool Count5/5

    Ten tools is well-scoped for a server that manages both user memory and knowledge bases. Each tool covers an essential operation without redundancy.

    Completeness4/5

    Memory lifecycle is complete (create, retrieve, update, delete, profile). Knowledge base lifecycle covers create/delete, document add/delete/query, but lacks an explicit 'list all knowledge bases' or 'update knowledge base' operation, which is a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources