Memory Bank MCP Server for VS Code: Setup & Config

What you can do with Memory Bank in VS Code

Choose it for straightforward, project-isolated memory files shared with an MCP coding assistant.

• Keep a coding assistant's project notes available between sessions.
• Find and read an existing project's context files.

Before you start: Memory Bank in VS Code

• Node.js and npx
• An MCP-compatible client
• A configured memory-bank storage directory

This follows the README's Claude configuration. Set the storage root to your directory. Docker is an alternative and requires a host-volume mapping. Review any client auto-approval settings separately from the server launch.

Memory Bank VS Code configuration

1. Choose VS Code configuration scope

   For Memory Bank MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Memory Bank MCP Server to VS Code

   Use the memory-bank-mcp entry below in servers. Keep Memory Bank MCP Server's documented stdio connection fields and your other VS Code entries.

3. Check Memory Bank MCP Server in VS Code

   Memory Bank MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "memory-bank-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@allpepper/memory-bank-mcp@latest"
      ],
      "env": {
        "MEMORY_BANK_ROOT": "<directory that will hold project memory banks>"
      }
    }
  }
}

Memory Bank tools available to VS Code

Memory Bank's stored tool list documents 5 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

memory_bank_read

Look for memory_bank_read among VS Code's agent-mode tools after starting Memory Bank through the MCP controls.

memory_bank_write

Look for memory_bank_write among VS Code's agent-mode tools after starting Memory Bank through the MCP controls.

Create a new memory document within a project.

memory_bank_update

Look for memory_bank_update among VS Code's agent-mode tools after starting Memory Bank through the MCP controls.

Revise an existing project memory file.

list_projects

Look for list_projects among VS Code's agent-mode tools after starting Memory Bank through the MCP controls.

Discover projects stored beneath the memory-bank root.

list_project_files

Look for list_project_files among VS Code's agent-mode tools after starting Memory Bank through the MCP controls.

Memory Bank: full stored tool descriptions

Troubleshooting Memory Bank in VS Code

• Make npx @allpepper/memory-bank-mcp@latest (Node.js/npm) available in the workspace, container, or remote environment hosting Memory Bank MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
• For Memory Bank MCP Server, keep MEMORY_BANK_ROOT out of version control; VS Code documents input variables and secret handling.
• Memory Bank MCP Server uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Requires choosing and maintaining a storage directory.
• Known limitation: The documented interface does not include semantic-search tools.
• Known limitation: Sample client settings can auto-approve writes and should be reviewed.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions