mcpbeat Sign in

Memory Vault MCP Server

answering

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

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

Installs per day peak 21 · avg 8 · +3% w/w
a month agotoday
Uptime history 65 days of history · worst day 99%
65 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
726 ms
Response time
average over 24h
86
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.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add memory-vault --transport http https://memoryvault.click/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "memory-vault": {
      "type": "http",
      "url": "https://memoryvault.click/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://memoryvault.click/mcp streamable-http sign-in 609 ms 3 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.

66 installs/wk local only
Callosium
by callosium

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

41 installs/wk local only
Throughline
by getthroughline

A persistent AI self you own — memory, persona, judgment — portable across all your AI hosts.

answering
Living Memory
by viibe

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

47 installs/wk answering
codemem
by jeang42

Shared memory for coding agents: projects, reusable code, sessions and commits across machines

87 installs/wk local only
Memento
by mementoagi

Hosted MCP memory for coding agents: persistent across sessions, editable markdown, team sharing.

answering
Brain Memory
by brainmemory

Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.

answering
Agentage Memory
by agentage

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

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 726 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 in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Memory Vault?
No API key is involved. Memory Vault answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Memory Vault?
It answers our handshake in 726 ms on average, which is faster than 12% 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 86 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.