Memory MCP Server

by lodekeep

answering

Memory is answering right now. Last checked 10 min ago.

Portable memory for AI agents: capture once, recall across Claude, Cursor, and any MCP client.

Uptime history 32 hours of history

32 hours agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

478 ms

Response time

average over 24h

API key or OAuth

Access

streamable-http

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add memory --transport http https://lodekeep.com/mcp

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

{
  "mcpServers": {
    "memory": {
      "url": "https://lodekeep.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.memory]
url = "https://lodekeep.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "memory": {
      "url": "https://lodekeep.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "memory": {
      "url": "https://lodekeep.com/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://lodekeep.com/mcp	streamable-http	needs key	507 ms	10 min ago

Alternatives to Memory

same job, measured the same way

Mifactory Agent Memory

by mifactory-bot

Persistent memory for AI agents across Claude, ChatGPT and any MCP client.

2 tools answering

Butlerbrain

by butlerbrain

Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.

answering

Aiko

by masa-san-jp

A portable persona for MCP clients — the same agent in Claude Code, Codex, Cursor and VS Code

428 installs/wk local only

Taproot

by taproothq

Persistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients.

answering

Memory

by cortex-mem

Shared, persistent memory for AI agents — works with Claude, Kiro, Cursor, or any MCP client.

91 installs/wk local only

Tabula

by nikhilbhima

Cross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client.

answering

Sovseal Memory

by bobybarack

Local-first, zero-knowledge AI memory across Claude, Cursor, and every MCP client. 0 RTT reads.

16 installs/wk local only

Goldhold

by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

36 installs/wk answering

Memory — questions

Answers built from our own checks of this server.

Why is there no tool list for Memory?

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 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 478 ms. The bar chart above shows every period we have measured.

How do I connect Memory?

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 need an API key?

Yes. Every time we knock, Memory 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?

It answers our handshake in 478 ms on average, which is faster than 25% 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.