Vasperamemory MCP Server

by rcolkitt Your server? Claim it

local only

Vasperamemory runs on your own machine — the client starts it, so there is no endpoint to ping. 117 installs a week from npm.

Persistent AI memory for coding assistants. 80+ tools for decisions, patterns, errors.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 226 · avg 36 · -3% w/w

a month agotoday

117

Installs / week

npm · vasperamemory

—

Stars

on GitHub

—

Last commit

0 releases in 90 days

—

License

language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add vasperamemory -- npx -y vasperamemory

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

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

~/.codex/config.toml

[mcp_servers.vasperamemory]
command = "npx"
args = ["-y", "vasperamemory"]

.cursor/mcp.json

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

.vscode/mcp.json

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

This one needs environment variables set before it will start: VASPERA_API_KEY (Your VasperaMemory API key from vasperamemory.com). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Vasperamemory

same job, measured the same way

Memorykit

by rapozoantonio

Cognitive memory for AI coding assistants — persistent memory across sessions

110 installs/wk local only

Memory

by shackleai

Persistent memory for AI coding tools. 11 tools for any MCP-compatible AI tool.

53 installs/wk local only

Project Memory MCP

by kaaustubh

Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.

118 installs/wk local only

Kawa Code

by kawacode

Team-aware memory: intent, decisions, real-time conflicts for AI coding assistants.

172 installs/wk local only

Toon Memory

by luiggival08

Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM

210 installs/wk local only

Memoir

by camgitt

Persistent memory for AI coding tools via MCP. Remembers across sessions and machines.

226 installs/wk local only

Session Forge

by 420247jake

Persistent memory and session intelligence for AI coding assistants. Zero config.

52 installs/wk local only

Knowledge MCP

by fulminate-io

Persistent memory graph for coding agents: hypotheses, evidence, and decisions survive sessions.

local only

Vasperamemory — questions

Answers built from our own checks of this server.

Why is there no uptime for Vasperamemory?

Vasperamemory runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package vasperamemory was installed 117 times last week.

Is Vasperamemory still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Vasperamemory?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls vasperamemory straight from npm; nothing to host, nothing to sign up for.

How many people use Vasperamemory?

The npm package vasperamemory was installed 117 times in the last week. Week over week that is -3%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.