MemorySync
io.memorysyncPublished by memorysync.ioOfficial publisherv1.0.0Updated Oct 24, 2026
Persistent memory for AI agents. Search and store durable facts, preferences and decisions.
The publisher's own server: MemorySync Documentation
Overview
MemorySync is a remote MCP server that gives an AI assistant persistent memory for storing and searching durable facts, preferences and decisions.
- What you can do
- Store durable facts, preferences and decisions in a persistent memory tied to the assistant across sessions, as described in the registry entry. Search that stored memory to recall earlier facts and choices. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when you want an assistant to remember facts, user preferences or past decisions between conversations instead of restating them each time, and when you are comfortable keeping that memory in a hosted third-party service.
- Requirements
- A remote MCP endpoint at mcp.memorysync.io over streamable HTTP. OAuth authentication is required, so you need an account with the provider and must complete the OAuth sign-in flow. No environment variables, headers or local packages are declared.
Installation
In SourceWeft
- Open MemorySync in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.memorysync%2Fmemory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"memorysync": {
"type": "http",
"url": "https://mcp.memorysync.io/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.