Skip to main content
Glama
flyinglimao

Memos MCP Server

by flyinglimao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Memos MCP Server

No user-submitted related servers found.

    Related Servers

    • Memos MCP Server

      ShaoRou459
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Memos instances for personal note-taking and knowledge management. Supports creating, searching, updating, and organizing memos with tags, dates, and visibility settings through natural language.
      MIT

    • mcp-server-memos

      ChenyqThu
      F
      license
      A
      quality
      D
      maintenance
      Enables to interact with Memos note-taking service, allowing search, creation, retrieval, and updating of notes through natural language.
      4
      5 npm
      4
      -

    • memos-mcp-server

      bubua12
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to read and write Memos notes through a Personal Access Token, with task-oriented search, precise editing, todo and tag management, attachment handling, exports, prompts, and resources. It supports both local stdio and multi-user Streamable HTTP transports, with safety switches such as read-only mode and restricted file access.
      20
      9 npm
      MIT

    • Memos MCP

      yixiaozi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to manage a self-hosted Memos instance, providing tools for memos, attachments, comments, reactions, shares, and user metadata, with optional OAuth for remote access.
      10 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

    B3.3/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: instance management, memo CRUD, tags, shortcuts, and attachments are clearly separated. Even the list_* tools are unambiguous because the resource type is explicit in each name.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern, such as list_memos, create_memo, update_shortcut, and upload_attachment. The only slight deviation is get_memo instead of list_memo, but this is still consistent with standard CRUD naming.

    Tool Count4/5

    With 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for a server covering instances, memos, tags, shortcuts, and attachments. Each tool covers a needed operation, so the count feels justified rather than bloated.

    Completeness4/5

    Core memo lifecycle, instance management, shortcut CRUD, and attachment operations are well covered. Minor gaps exist, such as no attachment download/retrieval endpoint and no single get_shortcut operation, but agents can mostly work around these using list operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources