There are three core components all used to capture and analyze browser data:
Chrome Extension: A browser extension that captures screenshots, console logs, network activity and DOM elements.
Node Server: An intermediary server that facilitates communication between the Chrome extension and any instance of an MCP server.
MCP Server: A Model Context Protocol server that provides standardized tools for AI clients to interact with the browser.
Model Context Protocol (MCP) is a capability supported by Anthropic AI models that
allow you to create custom tools for any compatible client. MCP clients like Claude
Desktop, Cursor, Cline or Zed can run an MCP server which “teaches” these clients
about a new tool that they can use.These tools can call out to external APIs but in our case, all logs are stored locally on your machine and NEVER sent out to any third-party service or API. BrowserKit MCP runs a local instance of a NodeJS API server which communicates with the BrowserKit Chrome Extension.All consumers of the BrowserKit MCP Server interface with the same NodeJS API and Chrome extension.
Thank you for your interest in contributing to BrowserToolsMCP! We welcome contributions from the community and appreciate your help in making this project better.
Before reporting a new issue, please check the issue tracker to see if it has already been reported.When reporting a bug or suggesting a feature, please include:
A clear description of the issue.
Steps to reproduce (for bugs).
Expected and actual behavior.
Screenshots, logs, or any other details that can help us understand the problem.