MemorySync MCP Server

by memorysync Your server? Claim it

answering

MemorySync is answering right now. Last checked 6 min ago.

Persistent memory for AI agents. Search and store durable facts, preferences and decisions.

Uptime history 64 days of history · worst day 0%

64 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

415 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check MemorySync 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 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

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

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

{
  "mcpServers": {
    "memory": {
      "url": "https://mcp.memorysync.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://mcp.memorysync.io/mcp	streamable-http	sign-in	398 ms	6 min ago

Alternatives to MemorySync

same job, measured the same way

Goldhold

by jerrysrodz

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

37 installs/wk answering

Memory

by velixarai

Persistent memory for AI assistants. Store, search, and recall across sessions.

72 installs/wk local only

Cairn

by jasondostal

Persistent memory for AI agents and humans. Store, search, and discover patterns.

local only

Memstack

by isiomac

MCP server for persistent, searchable memory for AI agents.

475 installs/wk local only

AI Cortex Storage

by aic0rt3x-memory

Persistent cloud memory for AI agents. Store and search key-value memories across sessions.

15 tools answering

MCP Memory

by infoinlet-marketplace

Persistent searchable memory for AI agents — save/get/search across sessions, tags.

39 installs/wk local only

Mem0

by mem0ai

Persistent memory for AI agents: add, search, update, and delete long-term memories.

answering

Central Intelligence

by alekseimarchenko

Persistent memory for AI agents. Store, recall, and share knowledge across sessions.

41 installs/wk local only

MemorySync — questions

Answers built from our own checks of this server.

Why is there no tool list for MemorySync?

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 MemorySync working right now?

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

How do I connect MemorySync?

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 MemorySync?

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

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