AI & MemoryMCP RegistrynpmD · 30

MemoryLayer MCP server

Name: MemoryLayer
Author: memorylayer.in

in.memorylayer · Updated 1mo ago

Local-first persistent memory for AI agents, with reasoning and formal verification.

At a glance

MemoryLayer is an MCP server in the AI & Memory category. It runs locally over stdio via `npx -y @raajvamsy/memorylayer`, and needs MEMORY_API_KEY. It scores D (30/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install MemoryLayer in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install MemoryLayer in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add memorylayer -e 'MEMORY_API_KEY=<MEMORY_API_KEY>' -- npx -y @raajvamsy/memorylayer

Fill in your credentials
Replace <MEMORY_API_KEY> with your real value. Keep secrets out of any config file you commit.
3
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install MemoryLayer in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "memorylayer": {
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ],
      "env": {
        "MEMORY_API_KEY": "<MEMORY_API_KEY>"
      }
    }
  }
}

Fill in your credentials
Replace <MEMORY_API_KEY> with your real value. Keep secrets out of any config file you commit.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install MemoryLayer in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "memorylayer": {
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ],
      "env": {
        "MEMORY_API_KEY": "<MEMORY_API_KEY>"
      }
    }
  }
}

Fill in your credentials
Replace <MEMORY_API_KEY> with your real value. Keep secrets out of any config file you commit.
Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install MemoryLayer in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.memorylayer]
command = "npx"
args = ["-y", "@raajvamsy/memorylayer"]
env = { MEMORY_API_KEY = "<MEMORY_API_KEY>" }

Fill in your credentials
Replace <MEMORY_API_KEY> with your real value. Keep secrets out of any config file you commit.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install MemoryLayer in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "memorylayer": {
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ],
      "env": {
        "MEMORY_API_KEY": "<MEMORY_API_KEY>"
      }
    }
  }
}

Fill in your credentials
Replace <MEMORY_API_KEY> with your real value. Keep secrets out of any config file you commit.
Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install MemoryLayer in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "memorylayer": {
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ],
      "env": {
        "MEMORY_API_KEY": "<MEMORY_API_KEY>"
      }
    }
  }
}

Fill in your credentials
Replace <MEMORY_API_KEY> with your real value. Keep secrets out of any config file you commit.

How to install MemoryLayer in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "memorylayer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@raajvamsy/memorylayer"
      ],
      "env": {
        "MEMORY_API_KEY": "<MEMORY_API_KEY>"
      }
    }
  }
}

Fill in your credentials
Replace <MEMORY_API_KEY> with your real value. Keep secrets out of any config file you commit.
Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What does MemoryLayer need from you?

API key — Optional MemoryLayer API key for higher rate limits. Memory content never leaves your machine; the key is used only for license validation. Get one free at https://memorylayer.in

MEMORY_API_KEYoptionalsecretEnvironment variable
Optional MemoryLayer API key for higher rate limits. Memory content never leaves your machine; the key is used only for license validation. Get one free at https://memorylayer.in

Pass secrets through your shell environment rather than committing them into a config file.

What tools does MemoryLayer expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 29 of 29 source files.

This server can run other programs on your machine, read and write files and execute code it builds at runtime.

Some of this package is bundled— its dependencies are compiled into the published files. The capabilities below are really in what runs on your machine, but they may come from a bundled library rather than the author's own source.

How it was published

Runs preinstall, postinstall on install — this executes when you install the package, before you deliberately run anything.
No provenance attestation — there is nothing linking this published artifact to a specific source commit.
1 npm maintainer — a single point of compromise · last published by raajvamsy.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

D · 30

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%not measurable
No commit history available.
Adoption20%not measurable
No usage data available.
Transparency20%0%
0/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✗ discoverable tool list.
Provenance15%0%
No source repository to trace the code back to.
Packaging15%100%
Publishes a pinned version (1.7.1).

Alternatives to MemoryLayer

Maintain MemoryLayer? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![MemoryLayer on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/in-memorylayer-memorylayer)](https://mcp-skills-hub.vercel.app/mcps/in-memorylayer-memorylayer)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.