Skip to main content
Glama
tydeck1016

FlowMCP

by tydeck1016
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to FlowMCP

No user-submitted related servers found.

    Related Servers

    • DataDam Personal Data MCP

      KennethLeeJE8
      A
      license
      Not graded
      quality
      D
      maintenance
      A persistent memory layer for AI tools that decouples personal data from AI's unstable memory, enabling you to mention information once and have it remembered forever across all conversations.
      3
      MIT
    • Mnemo MCP by expandingideas-ai

      Mnemo MCPofficial

      expandingideas-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent AI memory server with hybrid search and embedded sync. Enables AI agents to store, retrieve, and manage information across sessions with temporal knowledge graph support.
      MIT

    • Sovereign Universal Memory MCP

      nnaveenraju
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a persistent, vendor-neutral memory layer that allows AI tools and agents to share context and knowledge across different platforms while maintaining local data ownership. It enables users to store, recall, and manage structured memories through hybrid semantic search and automated context assembly.
      8 npm
      Apache 2.0

    • MCP Memento

      x-hannibal
      A
      license
      A
      quality
      B
      maintenance
      A persistent long-term memory server for AI assistants that enables storing and recalling solutions, facts, and decisions with intelligent confidence tracking and relationship mapping. It allows developers to build a cross-platform knowledge base that integrates seamlessly with IDEs and CLI agents.
      17
      26 PyPI
      2
      MIT

    • Memento

      scrypster
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent memory for AI tools by building a local knowledge graph from conversations, enabling cross-session recall and context awareness without cloud dependencies.
      9
      MIT
    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

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose: listing spaces, storing/searching/deleting memories, sharing memories, and managing projects. The overlap between flowmcp_store and flowmcp_project is mitigated by explicit guidance to prefer project for structured context. flowmcp_recall and flowmcp_load are clearly separated by memory vs. project.

    Naming Consistency3/5

    All tools share the flowmcp_ prefix, but naming conventions vary: list_spaces follows verb_noun, while store, recall, forget, push, project, and load are bare verbs or nouns. 'project' is a noun used as a tool name, and 'load' is generic, making the pattern somewhat inconsistent.

    Tool Count4/5

    Seven tools is a reasonable count for a memory management server. However, flowmcp_project bundles five distinct actions (snapshot, update_section, list, save_skill, load_skill), effectively expanding the surface area. Still, the overall count is well within the ideal range.

    Completeness4/5

    The memory lifecycle (create, read, delete, share) is covered, with update handled via store-with-recall. Project management covers snapshot/update/list/skills but lacks a delete project/section action. There is also no direct 'list all memories' tool, only search via recall. Minor gaps but core workflows are functional.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources