Memory Vault MCP Server

by apurv101 Your server? Claim it

answering

Memory Vault is answering right now. Last checked 1 min ago. 140 installs a week from npm.

Portable AI memory shared across models and harnesses - plain markdown you own.

Installs per day peak 319 · avg 10

a month agotoday

Uptime history 35 hours of history

35 hours agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

780 ms

Response time

average over 24h

140

Installs / week

npm and PyPI

Nothing serious here today

Today is the operative word: we check Memory Vault every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add memory-vault --transport http https://memoryvault.click/mcp

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

{
  "mcpServers": {
    "memory-vault": {
      "url": "https://memoryvault.click/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.memory-vault]
url = "https://memoryvault.click/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "memory-vault": {
      "url": "https://memoryvault.click/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "memory-vault": {
      "url": "https://memoryvault.click/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://memoryvault.click/mcp	streamable-http	needs key	792 ms	1 min ago

Alternatives to Memory Vault

same job, measured the same way

Br8n

by br8n

Owned, portable working memory: a plain-files markdown brain any model can read and cite.

266 installs/wk local only

Callosium

by callosium

One shared memory for every AI you use, in plain Markdown files you own.

72 installs/wk local only

Living Memory

by viibe

An MCP memory server. One memory your agents share — across models, devices and apps.

54 installs/wk answering

Agentage Memory

by agentage

One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.

answering

Atlaso

by atlaso

AI memory layer — one shared, persistent memory across every AI tool you connect.

answering

Engrm

by dr12hes

Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.

91 installs/wk local only

Epiphany

by gatsv-tech

One private, local memory your AI tools share. Cross-model, on-device, never lose a session.

67 installs/wk local only

XMemo

by yonro

Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

142 installs/wk answering

Memory Vault — questions

Answers built from our own checks of this server.

Why is there no tool list for Memory Vault?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Memory Vault working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 780 ms. The bar chart above shows every period we have measured.

How do I connect Memory Vault?

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 is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.

Does Memory Vault need an API key?

Yes. Every time we knock, Memory Vault answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Memory Vault?

It answers our handshake in 780 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Memory Vault?

The npm package memory-vault was installed 140 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.