Skip to main content
Glama
yubinbin32-ops

mdflow MCP Server

by yubinbin32-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mdflow MCP Server

No user-submitted related servers found.

    Related Servers

    • ai-cortex

      ai-creed
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides durable project context for coding agents, including project maps, session history, and explicit memories, all stored locally.
      20 npm
      7
      MIT

    • @vemdev/mcp-server

      vem-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI agents durable project memory via the Model Context Protocol, allowing them to read tasks, record decisions, search context, and sync snapshots to the cloud.
      10 npm
      MIT

    • engrams

      stevebrownlee
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.
      11
      Apache 2.0

    • scoped_memory

      lixuanfan567-png
      A
      license
      B
      quality
      B
      maintenance
      Provides local-first project memory and compact engineering context for Codex and DeepSeek Harness, enabling agents to persist and retrieve project-scoped decisions, task checkpoints, and deterministic EIR/1 engineering facts across sessions.
      8
      MIT

    • Jatobá Brain

      Ey-luccas
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent, multi-project memory for AI agents via MCP, enabling them to store and retrieve tasks, decisions, errors, checkpoints, and documentation while keeping context isolated by project.
      2
      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

    B3.2/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with detailed descriptions preventing major confusion. Minor overlaps exist between graph_mutate and graph_patch, and between entity_open and decision_open, but the descriptions clarify their scopes. Overall, an agent can reliably select the right tool for most operations.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., decision_open, source_binding_accept, checkpoint_list). Even multi-word names like checkpoint_refresh_candidates maintain the pattern, providing predictable and readable tool names throughout.

    Tool Count2/5

    With 32 tools, the server exceeds the 25-tool threshold for 'too many'. While the domain (architecture decision management, graph manipulation, checkpoints, plans) is complex and may justify a larger surface, the sheer number can overwhelm agents and increase selection overhead. The count feels heavy for the apparent scope.

    Completeness4/5

    The tool surface is extensive, covering project registration, decision management, graph creation/validation, source binding, checkpoints, plans, timelines, and synchronization. It appears to provide full lifecycle coverage for architecture decisions and associated artifacts. Minor gaps exist, such as explicit entity deletion (only revert via change_set_revert), but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources