VS Code / local MCP on Windows

Use Explore Better with VS Code

VS Code agents can search and inspect files beyond one workspace without receiving unrestricted access to the rest of the machine.

Explore Better

Connect VS Code in three steps

The desktop app creates the profile first, so credentials and authorized roots never need to appear in a public URL or copied command.

  1. 01Enable AI BridgeOpen Preferences > AI Bridge and turn on the local bridge.
  2. 02Create a profileAuthorize exact folders, choose read-only or planned writes, and copy the generated profile ID.
  3. 03Set up the clientUse the VS Code setup action. Explore Better updates %APPDATA%\Code\User\mcp.json while preserving unrelated configuration.

Explore Better

What the client gains

The client sees a stable, bounded tool model rather than a general-purpose shell.

Live context

Read the active pane, tabs, selection, focus, layout, and context revision when the desktop window is open.

Fast discovery

Page directories, query persistent indexes, inspect metadata, read bounded text, and compute checksums.

Safe execution

Run analysis jobs or preview a file change, apply it through the transactional queue, and monitor or undo the result.

Explore Better

A good first test

Open a folder in Explore Better, select a few files, then ask the client to inspect the current context and identify the largest selected item without modifying anything.

Use Explore Better's get_context tool.
Inspect the visible selection.
Return the largest item and explain which structured fields support the answer.
Do not modify any files.