1. Home
  2. Basic Memory
  3. Basic Memory for VS Code: Setup & Config

Data as of

Basic Memory for VS Code: Setup & Config

VS Code: Basic Memory gives AI clients persistent knowledge stored as Markdown that people can also edit.

What you can do with Basic Memory in VS Code

Persistent AI knowledge in editable Markdown, with local ownership and optional cloud teamwork.

  • Keep architecture decisions available across AI sessions.
  • Use Obsidian and an AI assistant on the same knowledge files.

Before you start: Basic Memory in VS Code

  • Python 3.12+
  • uv / uvx
  • An MCP-compatible client

This is the local client configuration from the README. Notes default to ~/basic-memory. Optional cloud onboarding is separate; no cloud MCP endpoint is specified in the supplied README.

Basic Memory VS Code configuration

  1. Choose VS Code configuration scope

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

  2. Add Basic Memory to VS Code

    Use the basic-memory entry below in servers. Keep Basic Memory's documented stdio connection fields and your other VS Code entries.

  3. Check Basic Memory in VS Code

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

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "basic-memory": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "basic-memory",
        "mcp"
      ],
      "env": {}
    }
  }
}

Basic Memory tools available to VS Code

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

search

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

fetch

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

Retrieve knowledge through the documented ChatGPT-compatible action interface.

schema_infer

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

Infer the structure of a knowledge base.

schema_validate

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

schema_diff

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

Compare knowledge-base structure changes.

edit_note

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

Edit notes, including append and prepend operations.

write_note

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

Basic Memory: full stored tool descriptions

Troubleshooting Basic Memory in VS Code

  • Make uvx basic-memory (from uv, for Python tools) available in the workspace, container, or remote environment hosting Basic Memory. Start through VS Code's MCP controls; inspect output and trust prompts.
  • Basic Memory uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Local users manage their own backups and cross-device sync.
  • Known limitation: Cloud hosting is a paid option.
  • Known limitation: The local install requires Python.
  • General VS Code troubleshooting lives in the /clients/vscode guide.

Basic Memory — details. VS Code guide

Frequently asked questions

For Basic Memory, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's basic-memory example uses stdio.

Basic Memory's VS Code configuration invokes uvx basic-memory (from uv, for Python tools).

Basic Memory's stored list contains 7 tools, including search, fetch, schema_infer. Compare those names with VS Code's connected tool list; the stored list is not a live check.

The README gives ~/basic-memory as the default location.

Yes. Obsidian can open the same Markdown directory and use its wikilinks and frontmatter.

No. The plugin requires an existing Basic Memory MCP connection.