VS Code + MemorySync

Overview

Connect the MemorySync MCP server to VS Code and Copilot’s agent mode gains a memory that persists across sessions, workspaces, Dev Containers and Codespaces: search past decisions, store durable facts, and start every task already briefed. Install is one click (the vscode:mcp/install deeplink), one command (`code --add-mcp` or the MemorySync installer), or one config block — documented exactly for every scope VS Code reads, with the API-key input-variable pattern (VS Code prompts once, masks the value, never writes it to disk) or OAuth via dynamic client registration. The only memory vendor with a real VS Code guide: Mem0’s page 404s and Supermemory’s generic snippet uses the wrong top-level key for VS Code. Read tools carry readOnlyHint, so recall runs without confirmation dialogs.

Setup status and requirements

Supported version

MemorySync MCP (hosted)

Last setup review

2026-08-24

Permissions

A MemorySync API key with read and write scopes, or OAuth sign-in on first connection.

Limits

MCP tools run in agent mode only (VS Code platform rule). The github.com coding agent supports header auth only — no OAuth — and requires the COPILOT_MCP_ secret prefix.

Capabilities

• One-click vscode:mcp/install deeplink — with or without the API-key prompt
• code --add-mcp one-liner and installer support (user profile + workspace)
• Exact mcp.json shapes: servers key, ${input:} secrets, OAuth via DCR
• Dev Containers and Codespaces block (customizations.vscode.mcp)
• Copilot coding agent on github.com documented: COPILOT_MCP_ secrets, tools array, no-OAuth limits
• readOnlyHint on read tools — recall without confirmation friction
• Live-verified on a real VS Code install

Quick Start

# One command:
code --add-mcp '{"name":"memorysync","type":"http","url":"https://mcp.memorysync.io/mcp"}'

# Or both servers via the installer:
npx memorysync-mcp-install --client vscode-user

Use Cases

Explore More