StudioMeyer Memory MCP Server

by studiomeyer Your server? Claim it

answering

StudioMeyer Memory is answering right now. Last checked 9 min ago.

Bi-temporal AI memory. 56 tools, knowledge graph, semantic search. EU-hosted, free tier.

Uptime history 47 days of history · worst day 90%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

268 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check StudioMeyer Memory 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 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add memory --transport http https://memory.studiomeyer.io/mcp

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

{
  "mcpServers": {
    "memory": {
      "url": "https://memory.studiomeyer.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.memory]
url = "https://memory.studiomeyer.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "memory": {
      "url": "https://memory.studiomeyer.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "memory": {
      "url": "https://memory.studiomeyer.io/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

URL	Transport	State	Latency	Checked
https://memory.studiomeyer.io/mcp	streamable-http	sign-in	319 ms	9 min ago

Alternatives to StudioMeyer Memory

same job, measured the same way

Memograph

by indhar01

Graph-based memory system for LLMs with knowledge graphs and semantic search.

119 installs/wk local only

Superlocalmemory

by varun369

Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.

1 596 installs/wk local only

Mnemograph

by tm42

Event-sourced knowledge graph memory for AI coding agents with semantic search

148 installs/wk local only

Agent Knowledge

by keshrath

Cross-session memory for AI agents - knowledge graph, scoring, semantic search

119 installs/wk local only

MemoraEU

by pquattro

Zero-knowledge persistent memory for Claude — encrypted, semantic search, EU hosted.

136 installs/wk local only

Shelbymcp

by studio-moser

Knowledge-graph memory server for AI tools via MCP

43 installs/wk local only

Memory

by humaux

Persistent long-term memory for AI agents: semantic search, knowledge graph, and task canvas.

answering

Memento

by scrypster

Persistent memory for AI tools. Local-first knowledge graph with hybrid search.

local only

StudioMeyer Memory — questions

Answers built from our own checks of this server.

Why is there no tool list for StudioMeyer 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 StudioMeyer 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 268 ms. The bar chart above shows every period we have measured.

How do I connect StudioMeyer 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 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 StudioMeyer Memory?

No API key is involved. StudioMeyer Memory 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 StudioMeyer Memory?

It answers our handshake in 268 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.