Browser Devtools Mcp

io.github.serkan-ozalPublished by GitHub account serkan-ozalv0.9.1Updated Oct 24, 2026

Playwright browser & Node.js MCP. ARIA refs, screenshots, ref-based interactions.

The publisher's own server: Driflyte Mcp Server

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Lets an assistant drive a Playwright-controlled browser and inspect Node.js debugging data through MCP tools.

What you can do
A Playwright-based browser and Node.js MCP server. It exposes ARIA references, screenshots and reference-based interactions so an assistant can navigate pages, click and type on elements, and capture visual state. Tool domains can be limited by configuration, and it also supports attaching to an existing Chrome DevTools Protocol endpoint or launching its own browser.
When to use it
Useful when an assistant needs to operate a real browser for testing, page inspection or scripted interaction, or when debugging a Node.js process alongside browser activity. It fits developer and QA workflows rather than general web search.
Requirements
Runs as a remote streamable HTTP endpoint or locally via the npm package browser-devtools-mcp over stdio, so Node.js is needed locally. A Chromium/Chrome browser is required, either bundled or system-installed. Optional configuration includes a CDP endpoint URL, browser executable path, allowed domains, and AWS Bedrock or Figma credentials.
Before you install
It can control a browser and interact with pages, so it may submit forms, click, or change remote state. Persistent context preserves cookies and localStorage, and CDP attachment can reach an existing browser session. The secret FIGMA_ACCESS_TOKEN and AWS Bedrock settings are optional but grant access to external services; restrict BROWSER_ALLOWED_DOMAINS to limit which hosts can be reached.

Installation

In SourceWeft

  1. Open Browser Devtools Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.9.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Driflyte integrations

Driflyte Mcp Server

com.driflyteOfficial publisher

Driflyte lets an assistant list indexed topics and search topic-tagged knowledge crawled from the web and GitHub for grounded answers.

Streamable HTTPWeb executable
Web Search & ScrapingNot indexed yetOct 24, 2026