Developer · Remote MCP server
MemorySync Documentation
Search and read the current MemorySync documentation while writing integration code.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.memorysync/docs- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-14
- Updated
- 2026-08-14
- Publisher
- io.memorysync · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain memorysync.io · how
- Website
- docs.memorysync.io/mcp/overview
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://docs.memorysync.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- memorysync-docs 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
search_docs,read_doc,list_doc_sections - Checked on
- 2026-10-05
How to connect MemorySync Documentation
MemorySync Documentation is a remote MCP server: there is nothing to install. Its endpoint is https://docs.memorysync.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from io.memorysync
| Server | Runs |
|---|---|
| MemorySyncPersistent memory for AI agents. Search and store durable facts, preferences and decisions. | Remote · HTTPLive check: sign-in required |
More developer servers
| Server | Runs |
|---|---|
| MemoryGuardLocal-first governed MCP memory backend for coding agents. | Local · stdio |
| MemorykitCognitive memory for AI coding assistants - persistent memory across sessions. | Local · stdio |
| MemoryoracleMemoryOracle - 10 agent memory tools: vector store, recall, summarization, redaction. | Remote · HTTPLive check: ✗ no handshake |
| MemoryRouterPersistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients. | Remote · HTTPLive check: ✓ handshake |
| Memshelf MCPWorking memory for AI agents: digest-indexed episodes on a git shelf, recalled a section at a time. | Local · stdio |
| MemtomemMarkdown-first long-term memory for AI agents. Hybrid BM25 + vector search, runs locally. | Local · stdio |
| MemwyreUniversal persistent memory and knowledge retrieval layer for AI agents and LLMs. | Remote · HTTPLive check: ✗ no handshake |
| mendapiDetect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally. | Local · stdio |