AI makes mistakes! Undisk makes recovery instant: every write is versioned, every file is reversible.
See it heal →
The Undisk MCP extension handles authentication, workspace selection, and MCP server registration automatically — no manual JSON configuration needed.

VS Code Marketplace

Install from the official Visual Studio Marketplace.

Open VSX Registry

Install from Open VSX for VSCodium, Gitpod, and Theia-based IDEs.

​
What the extension does

  1. Sign in — authenticate with your Undisk account via browser OAuth.
  2. Pick a workspace — select or create a workspace from the command palette.
  3. Ready — the extension registers Undisk as an MCP server using Streamable HTTP. Your AI agent (Copilot, Cline, Continue, etc.) can use all Undisk tools immediately.
If your workspace is empty, try the brain template — it seeds a useful starter structure. Run Undisk: Create Workspace from the command palette and choose a template.

​
Extension commands

CommandDescription
Undisk: Sign InAuthenticate with your Undisk account
Undisk: Sign OutSign out and unregister the MCP server
Undisk: Select WorkspaceSwitch active workspace
Undisk: Create WorkspaceCreate a new workspace (optionally from a template)

​
Manual Configuration

For teams that prefer explicit MCP settings or need to check configuration into version control. Create .vscode/mcp.json in your workspace or open your user mcp.json profile config: 
{
  "inputs": [
    {
      "type": "promptString",
      "id": "undisk-api-key",
      "description": "Undisk API key",
      "password": true
    }
  ],
  "servers": {
    "undisk": {
      "type": "http",
      "url": "https://mcp.undisk.app/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${input:undisk-api-key}"
      }
    }
  }
}

​
Validation Checklist

  • MCP server appears in the Copilot MCP panel (extension) or input prompt appears (manual).
  • Server handshake succeeds on VS Code startup.
  • Basic file operations (list_files, read_file, write_file) complete from MCP-aware agents.

​
Operational Notes

  • The extension stores credentials in VS Code’s built-in SecretStorage — never in plaintext files.
  • For manual config, keep sensitive inputs profile-scoped and avoid committing secrets to .vscode configuration files.