Agentage Memory is answering right now. Last checked 10 min ago.
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Agentage Memory does not always answer
Over the last week it answered 98.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
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 mcp add memory --transport http https://memory.agentage.io/mcphttps://memory.agentage.io/mcp[mcp_servers.memory]
url = "https://memory.agentage.io/mcp"{
"mcpServers": {
"memory": {
"url": "https://memory.agentage.io/mcp"
}
}
}{
"servers": {
"memory": {
"type": "http",
"url": "https://memory.agentage.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.agentage.io/mcp | streamable-http | sign-in | 196 ms | 10 min ago |
Alternatives to Agentage Memory
same job, measured the same wayA shared team wiki your coding agents read and write — across every repo and every MCP client.
Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.
Shared memory for AI agents, with a receipt for every write. Hosted MCP at agentics.you/mcp.
Hosted memory for AI agents over MCP. One memory shared by all your agents.
One shared memory for every AI you use, in plain Markdown files you own.
Your notes in one folder on your own server; AI clients read and edit it under write policies
Personal AI memory layer on your own computer. Read/write durable memory across MCP clients.
Shared memory for AI agents, as a graph in your own Postgres. Writes never call an LLM.
Agentage Memory — questions
Answers built from our own checks of this server.