home / mcp / vs code simple browser mcp server

VS Code Simple Browser MCP Server

MCP Server for interaction with VSCode Simple Browser window

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "savignano-vscode-simple-browser-mcp": {
      "command": "node",
      "args": [
        "/path/to/vscode-simple-browser-mcp/build/index.js"
      ],
      "env": {
        "ENV": "PLACEHOLDER"
      }
    }
  }
}

You can connect to a VS Code Simple Browser MCP Server to control the browser from an LLM, read console logs in real time, run JavaScript in the page context, and track browser state. This enables seamless integration between your assistant and the browser inside VS Code, empowering automated browsing tasks and rich interactions.

How to use

You interact with the VS Code Simple Browser MCP Server through an MCP client. The server exposes a set of actions you can invoke to control the in-editor browser, such as opening URLs, navigating pages, executing JavaScript, and retrieving console output. Start the server locally, connect your MCP client to the provided stdio endpoint, and begin issuing commands to perform tasks like loading a page, running code in the browser context, and monitoring browser activity in real time.

How to install

Prerequisites: ensure you have Node.js installed on your machine.

Clone the MCP server repository, install dependencies, and build the project.

git clone https://github.com/YOUR_USERNAME/vscode-simple-browser-mcp.git
cd vscode-simple-browser-mcp
npm install
npm run build

Configuration and usage notes

Configure your MCP client to connect to the local stdio endpoint provided by the server. The following example shows how to declare the MCP server in your client configuration.

{
  "mcpServers": {
    "vscode_sb": {
      "command": "node",
      "args": ["/path/to/vscode-simple-browser-mcp/build/index.js"]
    }
  }
}

Notes on security and maintenance

Keep access to the MCP endpoint restricted to trusted clients. When deploying in shared or CI environments, consider limiting the available actions and validating input to prevent unintended page navigation or code execution.

Troubleshooting

If the server fails to start, verify that Node.js is installed and that you are running the start command from the correct project path. Ensure you have built the project after cloning.

Examples of useful actions

Open a URL, navigate to a page, execute JavaScript in the browser context, and fetch console logs for debugging. You can also query the current browser state to understand loading status, errors, or navigation history.

Available tools

open_url

Open websites in VS Code Simple Browser from the MCP client.

navigate

Navigate between pages loaded in the browser context.

execute_javascript

Run JavaScript in the browser context and observe results.

get_console_logs

Retrieve console messages with optional filtering.

get_browser_state

Get the current status of the browser, including loading state and history.