home / mcp / browser mcp server

Browser MCP Server

Provides browser-interaction endpoints to fetch markdown, apply styles, and search history from the active browser page.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "diamond-it-615-browser-mcp": {
      "command": "npx",
      "args": [
        "@djyde/mcp-browser@latest"
      ]
    }
  }
}

You can run a browser-interaction MCP server that lets you work with the browser from your MCP client. This server exposes tools to retrieve page content, apply styles, and search history, enabling practical browser automation and inspection from your MCP setup.

How to use

To use this MCP server, you connect your MCP client to a stdio-based server that runs via a local runtime. The server you run provides the following capabilities: capture and summarize the current page as Markdown, apply CSS changes to the active page, and search your browser history. You can compose commands in your MCP client to invoke these tools and process the results in your workflow.

How to install

Prerequisites you need before installation: a supported Node.js environment and npm (or a compatible package manager). Ensure Node.js is installed on your system.

Install a package manager if you don’t have one. The typical workflow uses pnpm for building and dependency management.

Create a configuration file for the MCP runtime that defines this server as a stdio (local) MCP server with the npm script you will use to invoke the server tooling. Use the following configuration snippet as a starting point.

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@djyde/mcp-browser@latest"
      ]
    }
  }
}

Additional notes

This MCP server defines a single stdio endpoint named and ready to be used by your MCP client. If you plan to run multiple servers, you can add additional stdio entries following the same pattern. There are no explicit environment variables shown for this server, so include env variables only if you plan to extend the configuration in your environment.

Tools

The server provides three main tools you can call from your MCP client.

Capabilities you can call

- get_current_page_markdown β€” Retrieve the current browser page content as Markdown so you can summarize or store it in your notes.

- append_style β€” Append a CSS style to the current browser page to adjust appearance or enable themes for the browsing session.

- history_search β€” Search your browser history to locate prior visits or related pages.

Security and troubleshooting

When using stdio-based MCP servers, guard your environment to prevent unauthorized access to your browser session. Use your normal security practices for local IPC endpoints, and restrict access to the MCP runner as you would for any sensitive local service.

Note on build and run

Build and deployment steps are driven by your MCP runtime environment. The browser MCP server is configured to run via the npm-based command shown in the installation steps. Ensure your environment can spawn the specified npx @djyde/mcp-browser@latest invocation through your MCP runner when loading the mcpServers configuration.

Available tools

get_current_page_markdown

Fetch the current browser page content and return it as Markdown so you can summarize, annotate, or store it.

append_style

Add a CSS style to the active browser page to modify appearance, themes, or layout for the current session.

history_search

Search the browser history for matching entries and return results to your MCP client.