Skip to main content
Glama
johannesloor

Muscle Memory MCP Server

by johannesloor

Related Servers

Alternatives to Muscle Memory MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to store, recall, and manage persistent memory across sessions through MCP tools, with reviewable handoffs and SQLite-backed local storage.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to programmatically create, manage, and execute independent Python workflow scripts with full CRUD operations, allowing AI to build and modify automation workflows themselves rather than just executing pre-built ones.
      6
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to save, retrieve, semantically search, and document code snippets through MCP tools, including multi-agent workflows for generating style guides and wiki documentation.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to save and retrieve code snippets, perform semantic vector search over stored code, and generate code style guides and wiki documentation. It also orchestrates multi-agent workflows that combine specialized agents to produce comprehensive documentation from saved snippets.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to index and search local skill libraries, persist and resume task checkpoints, and run validated workflow plans with controlled approval and write permissions.
      53 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: mm_list discovers scripts, mm_run executes existing code, mm_save stores reusable code and runs its test, and mm_setup configures personal vs project storage. Although mm_run and mm_save both involve execution, the action boundaries are clearly described and unlikely to be confused.

    Naming Consistency5/5

    All tool names follow the same predictable mm_verb pattern: mm_list, mm_run, mm_save, and mm_setup. There are no naming style deviations.

    Tool Count5/5

    Four tools is well-scoped for a focused script-memory server. Each tool maps to a core operation: discover, execute, save, and configure.

    Completeness4/5

    The surface covers the main lifecycle of listing, running, saving/replacing, and configuring script storage. A delete/remove operation and possibly a direct get/inspect operation are missing, but most workflows remain workable through list, run, and save with replace.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues