Getting Started

Getting Started

Back to Home

This page covers all installation paths, configuration for Claude Desktop, Docker usage, and debugging with the MCP Inspector.

---

Prerequisites

• Node.js 20 LTS or later
• npm (included with Node.js)
• Claude Desktop (for MCP integration) or any MCP-compatible client

---

Installation

Option 1: npm (recommended)

npm install neurodivergent-memory

For local development:

git clone https://github.com/jmeyer1980/neurodivergent-memory
cd neurodivergent-memory
npm install
npm run build

For development with auto-rebuild:

npm run watch

Option 2: Docker Hub

docker run --rm -i twgbellok/neurodivergent-memory:latest

Option 3: GitHub Container Registry

docker pull ghcr.io/jmeyer1980/neurodivergent-memory:0.1.3
docker run --rm -i ghcr.io/jmeyer1980/neurodivergent-memory:0.1.3

---

Claude Desktop Configuration

Add the server to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%/Claude/claude_desktop_config.json

Using a local build

{
  "mcpServers": {
    "neurodivergent-memory": {
      "command": "/path/to/neurodivergent-memory/build/index.js"
    }
  }
}

Using npx (no install needed)

{
  "mcpServers": {
    "neurodivergent-memory": {
      "command": "npx",
      "args": ["-y", "neurodivergent-memory"]
    }
  }
}

Using Docker

{
  "mcpServers": {
    "neurodivergent-memory": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "twgbellok/neurodivergent-memory:latest"]
    }
  }
}

---

Memory Persistence

Memories are automatically saved to:

~/.neurodivergent-memory/memories.json

This file is created on first use and restored on every server startup. No configuration required.

---

Debugging with MCP Inspector

Since MCP servers communicate over stdio, standard debugging approaches don't apply. Use the MCP Inspector for interactive debugging:

npm run inspector

The Inspector will print a URL you can open in your browser to:

• Send tool calls interactively
• Inspect responses in real time
• Test search queries, graph traversals, and memory operations
• Verify your Claude Desktop config is working

---

Verifying Your Installation

Once connected through Claude Desktop or the Inspector, try these operations to verify everything is working:

1. store_memory — Create a test memory in logical_analysis
2. search_memories — Search for the content you just stored
3. memory_stats — Confirm the memory count is 1
4. retrieve_memory — Fetch the memory by ID

All operations should complete in under 100ms.

---

Release Security

• GitHub Actions runs on Node.js 20 LTS for CI and release automation
• npm publishes use OIDC provenance with npm publish --provenance --access public
• Docker images are built with Buildx, published to Docker Hub, and emitted with SBOM and provenance metadata
• GitHub Actions generates artifact attestations for the npm tarball and the pushed container image digest
• Tagged releases upload the npm tarball, checksums, and attestation bundles as release assets

---

See also: Architecture · Release-Notes · Experiment-Report