Developer Tools
memorysync.io
Provides search and read access to MemorySync documentation pages and sections.
ENDPOINT 1
https://docs.memorysync.io/mcp
MCP server metadata
- Name
- memorysync-docs
- Version
- 1.0.0
Search the MemorySync documentation before writing MemorySync integration code. Prefer read_doc over a search snippet when you need exact method names, parameters or limits. If the documentation and your prior knowledge disagree, the documentation is correct.
Known tools 3
search_docsSearch the MemorySync documentation and return matching pages with their headings and a link to the full Markdown text.
Inferred read-onlylist_doc_sectionsList the top-level documentation sections and how many pages each contains, to orient before searching.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.memorysync-docs]
url = "https://docs.memorysync.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"memorysync-docs": {
"type": "http",
"url": "https://docs.memorysync.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: memorysync-docs
Remote MCP URL: https://docs.memorysync.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"memorysync-docs": {
"url": "https://docs.memorysync.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"memorysync-docs": {
"type": "http",
"url": "https://docs.memorysync.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "memorysync-docs",
"transport": "streamable-http",
"url": "https://docs.memorysync.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://mcp.memorysync.io/mcp
Known tools 0
No tool metadata was available in the registry cache.
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.memorysync-io]
url = "https://mcp.memorysync.io/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"memorysync-io": {
"type": "http",
"url": "https://mcp.memorysync.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: memorysync-io
Remote MCP URL: https://mcp.memorysync.io/mcp
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"memorysync-io": {
"url": "https://mcp.memorysync.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"memorysync-io": {
"type": "http",
"url": "https://mcp.memorysync.io/mcp",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "memorysync-io bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "memorysync-io",
"transport": "streamable-http",
"url": "https://mcp.memorysync.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for memorysync.io was fetched 2026-08-24T05:06:58.864Z.
memorysync.io is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.