Add the MCP Memory Service MCP server to VS Code
Config last verified Nov 10, 2026
The exact config to run MCP Memory Service in VS Code — paste it in, restart, and the tools load.
Prerequisites
- VS Code installed.
Setup
1. Open .vscode/mcp.json
2. Add this configuration
Add to .vscode/mcp.json
.vscode/mcp.json
json
{
"servers": {
"mcp-memory-service": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"mcp-memory-service[sqlite]",
"memory",
"server"
],
"env": {
"MCP_MEMORY_STORAGE_BACKEND": "<MCP_MEMORY_STORAGE_BACKEND>",
"MCP_MEMORY_SQLITE_PATH": "<MCP_MEMORY_SQLITE_PATH>"
}
}
}
}Heads up
- VS Code uses the `servers` key (not `mcpServers`) and requires `type`.
3. Restart VS Code and confirm the MCP Memory Service tools load.
Gotchas
- VS Code uses the `servers` key (not `mcpServers`) and requires `type`.
VS Code is the exception to every other client: its top-level key is "servers", not "mcpServers", and each entry needs an explicit "type" (for example "http" or "stdio"). Secrets are not inlined; instead you declare an "inputs" array and reference each value as ${input:id}, so VS Code prompts for it once and never writes it to disk. Remote servers connect natively with OAuth.