agentsclimarketplace

Agent memory mcp

Skill sickn33/agentic-awesome-skills/skills/agent-memory-mcp

A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).From its SKILL.md

Install
npx -y skills add sickn33/agentic-awesome-skills --skill agent-memory-mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.3 KB, as published. Nobody here has run it

Agent Memory Skill

This skill provides a persistent, searchable memory bank that automatically syncs with project documentation. It runs as an MCP server to allow reading/writing/searching of long-term memories.

Prerequisites

  • Node.js (v18+)

Setup

  1. Review the Repository: Ask the user to approve network access to the named repository, then clone the pinned revision into a temporary directory, not an active skills path:

    review_dir="$(mktemp -d)"
    git clone --filter=blob:none https://github.com/webzler/agentMemory.git "$review_dir/agent-memory"
    git -C "$review_dir/agent-memory" checkout --detach 0409b7b7bb6fe443d0d4b6a6b1ee0d4df214f3cd
    git -C "$review_dir/agent-memory" ls-files
    

    Read all bundled files and inspect package.json, lockfiles, lifecycle scripts, network behavior, credential access, and filesystem scope. Show the findings and exact commit, then wait for explicit user approval.

  2. Install the Reviewed Revision:

    Copy the reviewed tree to a user-selected location after approval. Install locked dependencies only after the package scripts have been reviewed:

    cd <approved-agent-memory-directory>
    npm ci
    npm run compile
    
  3. Start the MCP Server: Use the helper script to activate the memory bank for your current project:

    npm run start-server <project_id> <absolute_path_to_target_workspace>
    

    Example for current directory:

    npm run start-server my-project $(pwd)
    

Capabilities (MCP Tools)

memory_search

Search for memories by query, type, or tags.

  • Args: query (string), type? (string), tags? (string[])
  • Usage: "Find all authentication patterns" -> memory_search({ query: "authentication", type: "pattern" })

memory_write

Record new knowledge or decisions.

  • Args: key (string), type (string), content (string), tags? (string[])
  • Usage: "Save this architecture decision" -> memory_write({ key: "auth-v1", type: "decision", content: "..." })

memory_read

Retrieve specific memory content by key.

  • Args: key (string)
  • Usage: "Get the auth design" -> memory_read({ key: "auth-v1" })

memory_stats

View analytics on memory usage.

  • Usage: "Show memory statistics" -> memory_stats({})

Dashboard

This skill includes a standalone dashboard to visualize memory usage.

npm run start-dashboard <absolute_path_to_target_workspace>

Access at: http://localhost:3333

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
  • Re-review upstream before changing the pinned revision; a commit pin improves reproducibility but is not a trust guarantee.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most mcp tooling skills give

Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06

  • Use Zod for input validationin 34 of 780, across 21 files
  • Use stdio for local clientsin 27 of 780, across 10 files
  • Restart Claude Code after configurationin 26 of 780, across 23 files
  • Verify MCP server connection before using toolsin 23 of 780, across 17 files
  • Define input schemas for every toolin 20 of 780, across 11 files
  • Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
  • Pin SDK version in package.jsonin 17 of 780, across 6 files
  • Keep server logic independent of transportin 16 of 780, across 6 files
  • Verify SDK methods against official documentationin 15 of 780, across 5 files
  • Format evaluation results as an XML filein 15 of 780, across 12 files
  • Test servers using the MCP Inspectorin 15 of 780, across 14 files
  • Create ten complex and independent evaluation questionsin 14 of 780, across 11 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.