1. Conduid
  2. Developer Tools
  3. memory
MCP server · Developer Tools

memory

Personal External Brain MCP Server - A stateless MCP server for syncing templates, standards, and knowledge via GitHub

Unclaimed devtools
39Low

Scored 5 months ago · breakdown

About memory

memory is an MCP server published by git+clayton-duarte in the Developer Tools category: personal External Brain MCP Server - A stateless MCP server for syncing templates, standards, and knowledge via GitHub.

Install

Install
npx @lesgo/memory-mcp
Claude Code
claude mcp add memory-mcp-gitclayt -- npx -y @lesgo/memory-mcp
npx
npx -y @lesgo/memory-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about memory

Powered by Claude · Grounded in docs

I know everything about memory. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

4 checks have not been run yet.

README

memory-mcp

Personal External Brain MCP Server - A stateless MCP server for syncing templates, standards, and knowledge via GitHub.

Features

  • Zero-latency reads: In-memory cache for instant access to templates and standards
  • Non-blocking writes: Async GitHub sync with local queue for resilience
  • Auto-categorization: Files organized by category (templates, standards, knowledge, etc.)
  • Full-text search: Search across file paths and content

Installation

VS Code / Copilot

Add to your ~/.vscode/mcp.json or VS Code settings:

{
  "servers": {
    "memory-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "memory-mcp"],
      "env": {
        "MEMORY_MCP_REPO": "your-username/memory-mcp-storage",
        "MEMORY_MCP_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "memory-mcp": {
      "command": "npx",
      "args": ["-y", "memory-mcp"],
      "env": {
        "MEMORY_MCP_REPO": "your-username/memory-mcp-storage",
        "MEMORY_MCP_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

Configuration

Variable Required Description
MEMORY_MCP_REPO Yes GitHub repository in owner/repo format
MEMORY_MCP_TOKEN Yes GitHub Personal Access Token with repo scope

Tools

list_knowledge

List all available memory files organized by category.

read_memory

Read the content of a specific memory file.

{ "path": "templates/user-story.md" }

save_memory

Create or update a memory file. Category folders are auto-created.

{ "category": "templates", "name": "user-story.md", "content": "..." }

delete_memory

Delete a memory file.

{ "path": "templates/old-template.md" }

search_memory

Search across all memory files by keyword.

{ "query": "graphql error" }

Storage Repository Structure

Create a private GitHub repository (e.g., memory-mcp-storage) with this structure:

/
├── index.json             # Auto-generated manifest
├── templates/             # Markdown templates
│   ├── user-story.md
│   └── pull-request.md
├── standards/             # Technical rules (YAML/JSON)
│   ├── typescript.yaml
│   └── graphql.yaml
└── knowledge/             # Long-form context
    └── architecture.md

How It Works

  1. Startup: Fetches all files from GitHub, populates in-memory cache
  2. Reads: Cache-first (instant), falls back to GitHub API on miss
  3. Writes: Updates cache immediately, returns to agent, syncs GitHub async
  4. Failures: Failed writes queue to ~/.memory-mcp-queue.json and retry on next operation

Development

# Install dependencies
npm install

# Build
npm run build

# Watch mode
npm run dev

License

MIT

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About memory

How do I install memory?

Run npx @lesgo/memory-mcp, then add the server to your MCP client's configuration.

Is memory safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 1 of the 2 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is memory still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.