InBrowserMCP logo

InBrowserMCP

by LofiSu

InBrowserMCP allows an AI model to interact with a web browser via a browser extension using the Model Context Protocol (MCP). It consists of a frontend, MCP server, and browser extension to orchestrate communication.

View on GitHub

Last updated: N/A

What is InBrowserMCP?

InBrowserMCP is a system that enables AI models to interact with web browsers. It uses the Model Context Protocol (MCP) to facilitate communication between a frontend interface, a backend server, and a browser extension.

How to use InBrowserMCP?

To use InBrowserMCP, start the MCP server, load the browser extension in Chrome, and start the frontend application. The frontend will initialize an MCP session, allowing you to send commands that control the browser via the extension.

Key features of InBrowserMCP

  • Frontend UI for interaction

  • MCP server for orchestration

  • Browser extension for browser actions

  • WebSocket communication

  • Server-Sent Events (SSE) for updates

Use cases of InBrowserMCP

  • AI-powered web scraping

  • Automated browser testing

  • AI-assisted web browsing

  • AI-driven data extraction

FAQ from InBrowserMCP

What is the Model Context Protocol (MCP)?

MCP is a protocol that allows AI models to interact with external tools and environments, in this case, a web browser.

What is the role of the MCP Server?

The MCP Server orchestrates communication between the frontend, the AI model (implicitly), and the browser extension, translating commands and managing data flow.

How does the Browser Extension interact with the server?

The Browser Extension connects to the MCP server via WebSocket and executes browser actions based on commands received from the server.

Is an AI model explicitly implemented in this project?

No, the AI model interaction is conceptual. The project provides the infrastructure for an AI model to interface with a browser, but the AI model itself needs to be integrated separately.

Where can I find detailed instructions for each component?

Refer to the README files within the frontend, mcp-server, and extension directories for specific instructions on setup and usage.